KintoWallet

This page explains all the nuances of our wallet implementation.

PreviousKinto Account Abstraction NextMusubi - Chain Abstraction

Last updated 8 months ago

KintoWallet

This page explains all the nuances of our wallet implementation.

What is it?

The Kinto Wallet is a non-custodial smart contract wallet compatible with the from .

The wallet has been designed to maximize user security and ease of use. Our invisible wallet can be used without any browser extensions and has many layers of security to protect user assets from everyday hacks, dusting, and phishing scams.

The following chart shows the essential role the wallet plays in our architecture.

Features

Here are the key features:

The native wallet is the only whitelisted implementation. That means that to send transactions in the network, they must be sent through the Kinto Wallet.
Furthermore, the wallet must have a KYC signer possessing a valid Kinto ID.
The wallet currently supports up to three signers and different signer policies ranging from one to all signers required to send a transaction. The user can set up hardware wallets as secondary signers.
The wallet can only interact with applications whitelisted by the owner. Token approvals need to be explicitly approved by the owner as well. These two can be bundled in the same batch for a frictionless user experience.
The wallet can only receive ETH funds from whitelisted funder addresses.
The user can set up a specific app signer for an application so the user can interact with that application safely without having to sign every transaction with all the signers.

Smart Contracts

Head to the following smart contracts to dive deeper into the implementation details:

PreviousKinto Account Abstraction NextMusubi - Chain Abstraction

Last updated 8 months ago

What is it?

The Kinto Wallet is a non-custodial smart contract wallet compatible with the from .

The following chart shows the essential role the wallet plays in our architecture.

Features

Here are the key features:

The native wallet is the only whitelisted implementation. That means that to send transactions in the network, they must be sent through the Kinto Wallet.

Furthermore, the wallet must have a KYC signer possessing a valid Kinto ID.

The first signer of the account is always secured by Passkeys and stored in Turnkey, a . All transactions are signed within an enclave, and private keys are never exposed to Turnkey or Kinto.

The wallet currently supports up to three signers and different signer policies ranging from one to all signers required to send a transaction. The user can set up hardware wallets as secondary signers.

There is also an additional per user stored in Turnkey. If the user loses control of his wallet, the user can trigger a week-long recovery process to reset the signers.

The wallet can only interact with applications whitelisted by the owner. Token approvals need to be explicitly approved by the owner as well. These two can be bundled in the same batch for a frictionless user experience.

The wallet can only receive ETH funds from whitelisted funder addresses.

The user can set up a specific app signer for an application so the user can interact with that application safely without having to sign every transaction with all the signers.

Smart Contracts

Head to the following smart contracts to dive deeper into the implementation details:

: The factory to create and manage Kinto Wallets. It also facilitates contract deployments.

: The Kinto smart-contract wallet. The code contains the code that verifies the execution, recovery, and management of the wallet.