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 Developers

Architecture Summary

In summary, when a developer or an integration partner interacts with Liquid, they’re leveraging a robust microservice-like architecture:

  • Front-end Interface (Bot or Web): Collects user inputs.

  • Backend (Node.js + Supabase): Orchestrates workflows, maintains user and asset states.

  • Third-Party Services: KYC (Civic/Sumsub) and Documint for specialized verifications and legal document generation.

  • Blockchain (Solana): Issuance of asset tokens and recording of immutable transaction records.

  • Decentralized Storage (IPFS/Arweave): Storage of off-chain asset data linked securely to on-chain tokens.

This modular design allows each component to be improved or scaled independently. For instance, Liquid can swap or add KYC providers per region, upgrade its storage backend, or even migrate from Solana to LiquidChain in the future — all without overhauling the entire system, thanks to consistent interfaces between components.

PreviousDecentralized Storage (IPFS/Arweave)NextSmart Contracts Documentation

Last updated 14 days ago