Keyring Network | Docs
  • INTRODUCTION
    • About Us
    • Our Solution
    • Use Cases
  • USER GUIDE
    • 1. Choose a Policy
    • 2. Onboard
      • Keyring Connect
      • Keyring Pro
    • 3. Create a Credential
    • FAQ
      • What is my onboarding status?
      • How to manage multiple entities?
      • What is Keyring's business model?
      • How to create credentials x-chain?
  • INTEGRATION STEPS
    • 1. Create a Policy
      • Connect Policy Builder
    • 2. Integrate to User Flow
    • 3. Permission smart contracts
  • PROTOCOL GUIDE
    • Sandbox
      • Keyring Connect
      • Keyring Pro
    • Data Flow
      • Data Collected
      • Data Storage
    • Smart Contracts
  • RESOURCES
    • Links
    • Get in Touch
    • Brand Assets
    • Data Policies
  • Onboarding Requirements
    • Keyring Pro
      • FalconX
    • Keyring Connect
Powered by GitBook
On this page
  1. PROTOCOL GUIDE

Sandbox

Previous3. Permission smart contractsNextKeyring Connect

Last updated 3 months ago

From an integration standpoint, Keyring Pro and Keyring Connect are similar, but we differentiate the two to reflect end-to-end flows for policy set-up and end-user navigation. SDKs to come.

Deployed contracts on mainnet and testnet available .

Story: A DeFi protocol wants to create a permissioned liquidity pool on Uniswap v4 for token $ERC20.

Integration:

  1. Use Keyring Connect Test Policy (ID: 7 )

  2. Permission pool access with hook invoking Keyring'scheckCredentialfunction. Leave LP token transfers unpermissioned

  3. Test User Flow

Story: A real-world asset protocol wants to create a permissioned vault for their ERC20 token $RWA on Euler v2.

Integration Guide:

  1. Test Policy: Keyring Pro Test Policy (ID: 6 )

  2. Permission vault access and vault token transfers with hook invoking Keyring'scheckCredentialfunction

  3. Test User Flow

here
see here
Keyring Connect
see here
Keyring Pro