ðŧDevelopment guide
Welcome! This section contains everything a developer needs to start working with Kinto.
Last updated
Welcome! This section contains everything a developer needs to start working with Kinto.
Last updated
Kinto is fully EVM-compatible but Kinto has two idiosyncratic referencers that you need to understand.
The first one is that Kinto has User-Owned KYC, meaning every user needs to be verified before sending any transaction.
The second one is that Kinto has native Account Abstraction, meaning that users are forced to have a smart wallet instead of plain EOAs and users do not have to worry about or pay gas. You can read more about the differences here.
Free KYC, KYT and AML. You get all this compliance tooling out of the box.
Sybil resistance.
Better UI/UX through Account Abstractions.
Higher level of security through Hypernative and Venn.
Insurance Policy to all Kinto users.
Mining rewards for developers based on the usage and TVL of their applications.
For developers, we have created a really simple onboarding process to make sure you can use your existing scripts and plain EOAs to deploy contracts as you would in any other EVM chain. In order to be able to deploy contracts like in any other chain, you need to do the following.
Sign up for a normal Kinto Account on the website.
Set up a deployer EOA account. This account can deploy contracts without restrictions.
Create a Kinto Application and configure your transaction sponsorship rules appropriately.
Once you have created your Kinto application and set up your development environment, you can start building the future of financial applications on Kinto.
You can interact with your application and your smart contracts in two different ways:
Via scripts through Foundry, Hardhat or Truffle. The guide will show you how to send transactions through Kinto Wallets.
Through a decentralized web application. You can see how to integrate our Kinto Wallet SDK here.
On top of the organizational purposes of Kinto Apps and ease of transfer, Kinto Apps are useful tools for developers for two main reasons.
By default Kinto enforces account abstraction which means that all interactions with contracts from users are expected to be UserOps sent through the EntryPoint. However, creating a Kinto App is a way to create an exception to this rule to facilitate contract operations for developers.
Kinto is a gasless experience for the final user thanks to our SponsorPaymaster implementation. In order to achieve this, developers pay the minimal Kinto fees instead of the users. Balances for each contracts and functionality to top up those balances is provided through the Kinto App abstraction.
Application whitelisting, our Kinto Wallet includes functionality to allow (or not) interaction with Kinto APPs. Creating a Kinto APP will provide an easy way to white list the necessary contracts of your application.
Kinto ensures that you get mining rewards from the usage of the applications you create on Kinto. You can read more about the mining program here.
Now that we know a bit more about Kinto Apps, you are ready to create your first one.
