Liquid Finance
  • Project Overview and Mission
    • Why Tokenize Assets?
    • Liquid's Vision
  • For Institutional Investors
    • Market Opportunity and Competitive Edgetor
      • Key Advantages
      • Market-Making and Liquidity
    • Compliance and Legal Framework
      • Jurisdictional Legal Wrappers
      • KYC/AML and Investor Accreditation
      • Regulatory Engagement
      • Audits and Security Compliance
      • Transparency and Reporting:
      • Commitment
    • Liquid Finance Token ($LIFI)
      • Fee Reduction
      • Staking and Yield
        • Network Security / Participation
        • Incentivizing Engagement
      • Marketplace and Liquidity Incentives
        • Boosting Listings
        • Liquidity Minting
        • Trading Fee Rewards
      • Governance
      • LiquidChain Native Token
      • Supply and Emissions
      • Value Proposition for Investors
      • Summary
  • For Developers
    • Technical Architecture Overview
      • Solana Blockchain
      • Node.js Backend
      • Supabase (PostgreSQL) Database
      • AI-Powered Bot
      • KYC/AML Integration (Civic & Sumsub)
      • Documint (Legal Document Generation)
      • Decentralized Storage (IPFS/Arweave)
    • Architecture Summary
    • Smart Contracts Documentation
    • Developer API and Integration
      • Asset Tokenization API
      • User Management and KYC API
      • Marketplace API
      • Bot Triggers and Webhooks
      • Supabase Integration
      • Interacting with Solana Programs
  • For General Users (Asset Owners & Investors)
    • Getting Started with Liquid
    • Fees, Costs and Staking Benefits for Users
    • The Liquid Vault (User Dashboard) – MVP Walkthrough
    • Staking & Rewards
  • Roadmap and Future Plans
    • Q2 2025 – Launch and MVP Expansion
    • Q3–Q4 2025 – Growth and Feature Development
    • 2026 – LiquidChain and Decentralization
    • Late 2026 and Beyond – Scaling to New Horizons
    • Summary of Roadmap Highlights
  • SOCIALS
    • Social Links
Powered by GitBook
On this page
  1. For Institutional Investors
  2. Compliance and Legal Framework

Regulatory Engagement

All participants on Liquid undergo stringent KYC (Know Your Customer) and AML screening​:

Liquid integrates with providers like Civic and Sumsub to verify government IDs, perform liveness checks, and run sanctions/PEP (Politically Exposed Person) lists. The verification process is user-friendly (taking just a couple of minutes via the user’s smartphone or webcam), but robust. Only verified individuals or entities can tokenize assets or trade on the platform.

Each verified user is tagged with a jurisdiction and investor status in Liquid’s database (e.g., US – accredited, or UK – retail, or SG – institutional). These tags are crucial for compliance gating. Liquid will automatically restrict what a user can do based on their profile:

  • A U.S. retail investor might be barred from buying certain tokens (Reg D offerings meant only for accredited investors) – the UI will not allow it.

  • A user from a country under sanctions or where crypto asset trading is banned will be prevented from participating entirely (Liquid is not available in those jurisdictions).

  • If a user’s status changes (say they become accredited or their KYC expires after a year), Liquid prompts re-verification or updates permissions accordingly.

On the blockchain level, Liquid can employ techniques like Civic Pass which issue a non-transferable NFT to KYC-verified wallets. Our smart contracts can check for the presence of a valid “verification NFT” in a wallet before allowing transfers in or out. This means even if someone interfaces directly with the token on-chain, the compliance rules persist (if they are not verified, the token won’t move to them – e.g., the transfer will fail due to our program logic). This two-layer approach (off-chain DB + on-chain token controls) ensures compliance cannot be easily circumvented.

PreviousKYC/AML and Investor AccreditationNextAudits and Security Compliance

Last updated 15 days ago

Page cover image