OpenViSTAI · Agents · Blockchain · Crypto
Submit a project
Menu
Layer 2 & Scaling

Kinto

Kinto is an Ethereum Layer 2 rollup with core Solidity contracts for smart-contract wallets, account abstraction, and on-chain identity and compliance checks.

Explore the practical guide ↓

Independent OpenViST project profile, based on linked sources.

Kinto — OpenViST project profile in Layer 2 & Scaling.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use the repository when developing or reviewing Solidity integrations with Kinto’s wallet, paymaster, or identity contracts, or when preparing to run its documented local tests.

Who it is for

  • Solidity developers reviewing or integrating Kinto’s core contracts.
  • Teams building applications that need Kinto wallet creation, account abstraction, or on-chain identity checks.

Documented uses

  • Inspect the contracts behind KintoWallet and its factory.
  • Integrate account-abstraction transactions through Kinto’s EntryPoint and SponsorPaymaster.
  • Check whether an address meets KYC, accreditation, or AML-sanctions requirements using Kinto ID.
Before you choose

Requirements & limits

The core-contract repository is public and specifies the MIT license. Its documented development requirements include Foundry and Yarn or NPM.

  • Kinto is described as EVM-compatible, but its transaction model requires a KintoWallet and routes transactions through the EntryPoint.
  • The first signer of a KintoWallet must hold a Kinto ID for transactions, according to the repository README.
  • Direct EOA transactions are restricted to five listed contracts; EOAs can make calls that do not change chain state without KYC.
  • The repository separates settlement, execution, and data availability in its architecture description, identifying Ethereum, Arbitrum, and Celestia via Blobstream respectively.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Set up the Kinto core-contract repository

Install the project dependencies and prepare the environment file for repository work.

Before you start

  • Foundry
  • Yarn or NPM
  • The repository’s .env.sample file and configuration values

Steps

  1. Install dependencies with yarn install.

  2. Copy .env.sample to .env and fill in the required values.

  3. After deploying the proxy, add its address to the environment configuration.

Expected outcome

Dependencies are installed and the environment file is prepared for subsequent repository work.

Guide limitations

  • These instructions cover dependency and environment setup, not application deployment.
  • A custom chain requires additional CREATE2 proxy setup described in the repository.
Documentation 1 ↗
Source-based practical guide

Run the repository’s local tests

Invoke the core-contract test suite using the documented local test command.

Before you start

  • Foundry and the repository dependencies

Steps

  1. From the repository, run forge test.

  2. Alternatively, run yarn test.

Expected outcome

The repository’s local test suite is invoked.

Guide limitations

  • Fork tests require FOUNDRY_PROFILE=fork and the repository’s fork-test configuration.
  • The instructions do not establish that the tests have been run successfully in a particular environment.
Documentation 1 ↗
Evidence and transparency

Sources & review

Official repository ↗
Source record details
Source availability
Active
Sources checked
8 October 2026
Original website title
KintoXYZ/kinto-core · Official homepage title · retained in its source language
How we review sourcesSuggest a correction