Kinto

Kinto API is available on Web3 API platform.

Kinto is an L2 focused on providing safe access to on-chain finance. It's built on top of the Ethereum network using the Arbitrum Nitro Stack, and it's non-custodial, transparent, permissionless, and governed by the community.

Kinto has been designed from the ground up to provide a safe environment for users and financial institutions. Kinto has two unique features at the chain level to enhance the security of the chain:

By default, Kinto provides KYC, AML & fraud monitoring at the blockchain level. All participants in the network are KYC'ed, and the network runs AML on all of the participants. Transactions can then only be performed by verified participants achieving Sybil Resistance. PII is only saved in identity providers chosen by governance. Users' information cannot be linked to their on-chain accounts except when they choose to do so with an application that requests it.
Kinto gives every single user a smart contract wallet powered by Account Abstraction. The Kinto wallet aims to be invisible. The user does not need to worry about complicated browser extensions, seed phrases or gas while still receiving the benefits of non-custodial ownership. Kinto wallet offers similar security assurances to a Gnosis safe, the standard in on-chain security.

Kinto has a two-layer governance system fully on-chain. The protocol parameters, sequencer, and treasury will be voted on-chain by 9 Nios (Guardians). Token-holders elect these 9 guardians on a rolling 6-month basis.

Blockchain interaction API

In order for your Web3 application to interact with Kinto — either by reading blockchain data or sending transactions to the network — it must connect to a Kinto node. Developers interact with the blockchain using the methods provided by the API.

The API interaction follows the JSON-RPC which is a stateless, light-weight remote procedure call (RPC) protocol. It defines several data structures and the rules around their processing. It is transport agnostic in that the concepts can be used within the same process, over sockets, over HTTP, or in other message-passing environments. It uses JSON (RFC 4627) as data format.

Methods supported

web3_clientVersion — returns the current client version.
web3_sha3 — returns Keccak-256 (not the standardized SHA3-256) of the given data.
net_version — returns the current network ID.
eth_syncing — returns data on the sync status or false.
eth_gasPrice — returns the current price per gas in wei.
eth_accounts — returns a list of addresses owned by client.
eth_blockNumber — returns the number of most recent block.
eth_getBalance — returns the balance of the account specified by address.
eth_getStorageAt — returns the value from a storage position at an address specified.
eth_getTransactionCount — returns the number of transactions sent from an address.
eth_getBlockTransactionCountByHash — returns the number of transactions in a block specified by block hash.
eth_getBlockTransactionCountByNumber — returns the number of transactions in the block specified by number.
eth_getUncleCountByBlockHash — returns the number of uncles in a block specified by block hash.
eth_getUncleCountByBlockNumber — returns the number of uncles in a block specified by block number.
eth_getCode — returns code at an address specified.
eth_sendRawTransaction — creates a new message call transaction or a contract creation for signed transactions.
eth_call — executes a new message call immediately without creating a transaction on the blockchain.
eth_estimateGas — generates and returns an estimate of how much gas is necessary to allow the transaction to complete.
eth_getBlockByHash — returns information for the block specified by block hash.
eth_getBlockByNumber — returns information for the block specified by block number.
eth_getTransactionByHash — returns information on a transaction specified by transaction hash.
eth_getTransactionByBlockHashAndIndex — returns information on a transaction specified by block hash and transaction index position.
eth_getTransactionByBlockNumberAndIndex — returns information on a transaction by block number and transaction index position.
eth_getTransactionReceipt — returns the receipt of a transaction by transaction hash.
eth_getUncleByBlockHashAndIndex — returns information about an uncle of a block by hash and uncle index position.
eth_getUncleByBlockNumberAndIndex — returns information about an uncle of a block by number and uncle index position.
eth_getLogs — returns logs matching the parameters specified.

Methods supported​

Methods​

web3, net, eth​

Methods supported

Methods

web3, net, eth