ACP-267: Primary Network validator uptime requirement increases from 80% to 90%.Read the proposal
Keyring

Keyring

Keyring provides privacy-preserving identity verification using zero-knowledge technology, enabling compliance for blockchain applications implementing txAllowlist precompiles.

Back

Overview

Keyring is an identity verification platform that uses zero-knowledge (ZK) technology to handle KYC for blockchain applications without exposing personal data. Through Keyring Pro and Keyring Connect, users verify their identity once and reuse credentials across multiple platforms. For projects using txAllowlist precompiles, Keyring lets you enforce compliance while preserving user privacy -- verified users can transact on permissioned networks without sharing more data than necessary.

Features

  • Zero-Knowledge Verification: Utilizes zkTLS technology to verify user identity without exposing personal data, allowing proofs to be submitted on-chain.
  • Privacy-First Approach: Users maintain control of their personal information while still satisfying verification requirements.
  • Instant ZK-KYC: Enables users to extract information from established platforms (like Binance, Revolut, or Coinbase) with proof of authenticity in minutes.
  • Multi-Chain Support: Available on multiple networks including Ethereum, Base, Arbitrum, Optimism, and Avalanche.
  • Customizable Compliance Policies: Define specific rules and verification requirements for your platform's risk profile.
  • On-Chain Credential Issuance: Creates verifiable credentials that can be queried by smart contracts for transaction approval.
  • Quick Developer Integration: Simple implementation that can be completed in under 3 hours.
  • Automates Identity Verification: Replaces manual KYC workflows with automated credential verification.

Getting Started

To integrate Keyring into your Avalanche-based application with txAllowlist precompiles, follow these steps:

  1. Contact Keyring: Reach out to Keyring through their contact page to discuss your specific compliance requirements.
  2. Define Compliance Policy: Work with Keyring to establish the rules and data sources you'll accept for verification.
  3. SDK Integration: Add a button or link to your frontend using Keyring's SDK to initiate the verification process.
  4. Smart Contract Integration: Implement the provided modifiers in your smart contracts to check credential validity before allowing transactions.
  5. Testing: Thoroughly test the integration to ensure proper credential verification and allowlist management.
  6. Launch: Deploy your enhanced application with integrated txAllowlist and Keyring verification.

Integration with txAllowlist

Keyring works well with Avalanche's txAllowlist precompile:

  1. Privacy-Preserving Compliance: Users prove they've passed KYC without revealing personal details, maintaining privacy while enforcing transaction restrictions.
  2. On-Chain Credential Verification: Smart contracts verify credentials before approving transactions, acting as the allowlist enforcement layer.
  3. Dynamic Access Control: Transaction permissions are automatically granted or revoked based on credential status -- no manual allowlist management needed.
  4. Verify-Once UX: Users verify once and interact with multiple applications using the same credentials.
  5. Risk-Based Approach: Verification can be calibrated to the risk level of different transaction types or user profiles.

Documentation

Keyring's developer docs are available at docs.keyring.network/docs.

Use Cases

Keyring fits well with these Avalanche-based applications:

  • Permissioned DeFi Pools: Create lending pools or trading platforms that only allow KYC'd users from non-sanctioned countries.
  • Compliant DEXs: Enable decentralized exchanges to implement regulatory-compliant trading without compromising on decentralization principles.
  • Cross-Chain Ecosystems: Maintain consistent identity verification across multiple chains or subnets.
  • Token Offerings: Ensure participants in token sales meet jurisdictional requirements.
  • Enterprise Applications: Build permissioned applications that require verified identity while maintaining privacy.
  • Travel Rule Compliance: Implement solutions compatible with the FATF Travel Rule for VASPs without excessive data sharing.

Is this guide helpful?

Developer:

Keyring Network

Categories:

KYC / Identity Verification

Available For:

C-Chain

Website:

https://www.keyring.network/

Documentation:

https://docs.keyring.network/docs