AssetGate — BOT Chain Mainnet Architecture & Integration Brief

1. Summary & Value Proposition

Real-World Assets (RWAs)—such as private credit funds, commercial real estate, structured debt, and treasuries—cannot be legally represented by standard ERC-20 tokens. Global regulatory frameworks require strict on-chain guarantees:

• Identity Verification: Only KYC/AML-verified investors may hold or receive the asset.
• Transfer Restrictions: Asset movement must enforce jurisdictional rules, single-investor concentration caps, and max holder thresholds.
• Institutional Governance: Issuers require legal capabilities to freeze malicious wallets, pause trading during halts, execute court-ordered asset recovery, and distribute automated pro-rata dividends.

AssetGate brings institutional-grade RWA infrastructure to BOT Chain. Built on the battle-tested ERC-3643 (T-REX) standard, it establishes a turnkey B2B platform with on-chain compliance gates, resilient PostgreSQL event indexing, zero-gas preflight simulations, and specialized Issuer/Investor portals.

2. Smart Contract Architecture (The Two-Gate Model)

To meet global security token regulations, standard ERC-20 transfers are strictly forbidden. In AssetGate, every asset movement (transfer, transferFrom, mint) must pass through two independent, sequential on-chain verification gates before balances can update:

       Sender (Verified) ────────── transfer(to, amount) ──────────► Recipient
                                       │
                                       ▼
        ┌─────────────────────────────────────────────────────────────┐
        │  GATE 1: Identity Registry (IdentityRegistry.sol)           │
        │  • Is recipient registered in the Identity Registry?        │
        │  • Does recipient hold a valid ONCHAINID contract?          │
        │  • Does ONCHAINID hold a valid KYC Claim (Topic 1)          │
        │    cryptographically signed by a Trusted Claim Issuer?      │
        └──────────────────────────────┬──────────────────────────────┘
                                       │
                               [Passes Gate 1]
                                       │
                                       ▼
        ┌─────────────────────────────────────────────────────────────┐
        │  GATE 2: Modular Compliance (ModularCompliance.sol)         │
        │  • Country Restriction: Is recipient's country allowed?     │
        │  • Balance Cap: Does amount exceed single-wallet limit?     │
        │  • Holder Threshold: Does transfer exceed max holder cap?   │
        └──────────────────────────────┬──────────────────────────────┘
                                       │
                         ┌─────────────┴─────────────┐
                         ▼                           ▼
                 [Both Gates Pass]            [Either Fails]
                         │                           │
                   Tokens Move                 On-Chain Revert
               Event Emitted & Indexed         Zero Balance Change
  

Core Architectural Guarantees:

• Gate 1 (Identity & Attestation): Verifies investor eligibility via decentralized ONCHAINID (ERC-734/735). The token queries IdentityRegistry.isVerified(recipient), confirming that an authorized claim issuer signed their KYC claim off-chain.
• Gate 2 (Modular Compliance Rules): Evaluates dynamic jurisdictional rules via ModularCompliance.canTransfer(). If the transfer breaches country restrictions, holding limits, or maximum investor caps, execution halts immediately.
• Strict Atomicity: If either gate returns false, the transaction reverts on-chain with zero state change. Only when both gates pass are balances debited/credited and indexed by our real-time engine.

3. Core Smart Contracts & Compliance Modules

All smart contracts below have been compiled via Foundry, orchestrated with DeployAll.s.sol, and deployed on BOT Chain Mainnet (Chain ID 677), with core contracts verified on-chain and auxiliary modules pending explorer source verification (see Section 9 for status breakdown):

Active Compliance Modules:

• CountryRestrictModule.sol: Enforces investor jurisdiction eligibility (e.g., permitting ISO 840 US investors while blocking sanctioned nations).
• BalanceCapModule.sol: Prevents token concentration by capping maximum holdings per single investor.
• MaxHolderCountModule.sol: Automatically enforces private placement limits (e.g. maximum 500 holders).

4. ONCHAINID Privacy & Cryptographic Attestation

We designed the identity layer to guarantee institutional compliance without exposing sensitive investor data on a public ledger:

• Decoupled Identity Contracts: Every investor has a dedicated ONCHAINID smart contract (ERC-734 / ERC-735), separating their on-chain legal persona from their transient wallet keys.
• Zero PII On-Chain: Passports, tax IDs, and personal documents never touch BOT Chain. The blockchain records only cryptographic attestations.
• ECDSA Claim Signatures: Our trusted Claim Issuer signs an off-chain attestation hash: keccak256(identityAddress, TOPIC_KYC, "PASSED_KYC"). The smart contract validates only this signature, keeping verification instantaneous and gas-minimal.

5. Resilient Indexing Engine & Database Fault-Tolerance

AssetGate maintains a live, zero-latency Cap Table backed by Fastify, Prisma ORM, and Neon PostgreSQL without overloading BOT Chain's RPC nodes:

• Conservative 100-Block Batches: Configured with BATCH_SIZE = 100 against https://rpc.botchain.ai as recommended by the BOT Chain engineering team, eliminating RPC timeouts.
• Atomic ACID Checkpoints: Checkpoint updates (lastBlock) are committed inside prisma.$transaction alongside event inserts.
• Automated Fault-Tolerance Tests: Verification tests prove that RPC failures or database deadlocks immediately roll back and leave lastBlock strictly unchanged. On restart, the indexer resumes from lastBlock + 1 with zero duplicate records (enforced by txHash_logIndex unique keys).

6. Off-Chain Preflight Simulation Shield

On public blockchains, compliance failures revert on-chain and burn real gas fees. AssetGate eliminates this friction with its Preflight Shield (/api/v1/transfer-preflight):

7. Complete Live Demo Walkthrough

The production DApp is deployed live at https://asset-gate.vercel.app/ on BOT Chain Mainnet (Chain ID 677). The platform operates seamlessly across two standard user personas:

Persona A: Investor Portal (Self-Sovereign Identity & Compliant Trading)

Persona B: Issuer / Fund Manager Portal (Corporate Governance & Control)

8. Role-Based Access Control & Dashboard Agent Manager

To ensure high institutional security while making corporate administration frictionless, AssetGate combines strict smart contract RBAC with an interactive dashboard permission manager:

• On-Chain Security: Administrative controls (mint, freeze, forcedTransfer, pause) strictly require the AGENT_ROLE on both the Token and Identity Registry contracts. Unauthorized calls revert immediately.
• Interactive UI Agent Manager: Contract owners and compliance officers can delegate or revoke the Agent role directly through the governance interface without executing manual command-line scripts:

  // Operator permissions can be granted or revoked directly from the web UI:
  token.addAgent(operatorAddress);
  identityRegistry.addAgent(operatorAddress);

  Simply input the target operator's wallet address, click Grant agent, and that account is immediately authorized on-chain to execute minting, compliance freezes, and emergency halts.
• Instant Transaction Proofs: Confirmation banners on all dashboard controls render live receipt links directly to BOT Chain Explorer, allowing compliance officers and auditors to verify the underlying state change on-chain in real time.

9. BOT Chain Mainnet Deployment Matrix & Verification

The entire AssetGate protocol suite is deployed and live on BOT Chain Mainnet (Chain ID 677). All smart contracts are open for public audit and verification on scan.botchain.ai:

Core Genesis Verification & Live Endpoints