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
  2. Technical Architecture Overview

Supabase (PostgreSQL) Database

PreviousNode.js BackendNextAI-Powered Bot

Last updated 14 days ago

Liquid uses Supabase (an open-source Firebase alternative) as its database and authentication layer. All user and asset data – user profiles, KYC status, asset details, token metadata links, etc. – are stored in a Postgres database via Supabase. Supabase also enables real-time notifications; for instance, a Supabase trigger can notify the backend when a user’s KYC is approved, prompting the next step in the workflow. This event-driven design (“bot triggers”) ensures smooth automation from one stage to the next.

Page cover image