CLIQUETECH PROTOCOL

Technical documentation for the creator-token marketplace on Robinhood Chain.

Architecture

cliquetech is a specialized interface operating on top of the Pons v2 bonding curve protocol deployed natively to Robinhood Chain. The system enables creators to launch personal tokens paired against either native ETH or fractionalized Real-World Assets (RWAs).

At its core, cliquetech introduces a custom Gate Factory overlay that enforces continuous self-ownership requirements before any creator fees can be swept from the core protocol fee escrow.

Robinhood Chain Config

The marketplace operates exclusively on the Robinhood Chain mainnet.

Canonical Pons v2 Contracts

cliquetech utilizes the canonical Pons v2 deployment. All creator tokens and bonding curves are directly instantiated through the PonsV2LaunchFactory.

The FeeEscrow and BuybackVault addresses are intentionally not hardcoded: the app and the gate contracts read them live from the factory's public feeEscrow() and buybackVault() getters, so an upstream migration can never leave a stale reference here.

Clique/Gate Trust Model

Unlike vanilla Pons v2 launches where creator fees are sent directly to an EOA, cliquetech wraps every token launch in a Self-Ownership Fee Gate.

The Clique Gate Factory immutably binds a unique CliqueGate contract to the creator prior to the token launch. The Pons factory configures the gate as the creatorFeeRecipient.

All trading fees allocated to the creator accumulate in the global Pons Fee Escrow under the gate's address, forcing the creator to abide by the gate's staking rules to ever withdraw their earnings.

Creator Launch Flow

1. Pair Selection: The creator selects either native ETH or a pre-approved RWA asset as the quote token.
2. Gate Deployment: The creator calls deployGate. The factory derives a deployment salt from the creator and supplied salt, then uses CREATE2 to deploy a gate with immutable Pons factory, creator, and threshold configuration. The gate address is predictable via predictGateAddress before the transaction is signed.
3. Launch Registration: The creator calls canonical Pons launchToken with token metadata, launch-config ID, pair token, expected economics hash, and the predicted gate as creatorFeeRecipient.
4. Binding: After launch, the creator calls bindCreatorToken. The gate verifies the Pons record exists, the deployer is the original creator, the curve is deployed, and the fee recipient is the gate; the registry then maps the token to that bound gate.

ETH & RWA Pairs

A token's pair determines its quote reserve asset. ETH is represented as the zero address (0x0000…0000). cliquetech supports fractionalized Real-World Assets (RWAs) as quote tokens for creators targeting traditional equity economies.

Buy/Sell Mechanics

Trading is fully automated by the Pons bonding curve. Users interact via buy() and sell() methods. The internal pricing function relies on a virtual/phantom quote reserve injected at launch to define the starting price and liquidity depth.

The pair-specific graduationThreshold is denominated in the quote asset's smallest units. When Pons reports the curve ready to graduate, its phase and liquidity migration behavior are governed by canonical Pons v2 — not by cliquetech.

Fee Lifecycle

Curve fees are determined by the canonical Pons launch configuration. The curve exposes pending quote-fee and creator-tax balances; cliquetech does not modify the bonding-curve pricing formula.

• Pending on the curve: Quote fees and creator-tax balances accrue in the canonical curve.
• Sweep: Anyone calls sweepCreatorFees(minBuybackTokensOut) through the gate. The gate invokes the bound curve's sweepFees, moving the fee accounting into canonical Pons escrow.
• Claim: Native ETH uses claimFromFeeEscrow; token-paired launches use claimTokenFromFeeEscrow. Both claims require the seven-day eligibility test at execution time.

Escrow credits belong to the gate address, not directly to the creator wallet. The gate checks eligibility before pulling the full corresponding escrow ledger balance and forwarding it to the creator-selected recipient.

Staking & Self-Ownership

Sweeping curve balances into escrow and claiming escrowed funds are separate actions. A creator may sweep through the bound gate, but cannot claim or withdraw gate-held value until they demonstrate continuous self-ownership for 7 consecutive days.

Wallet & Image Security

Non-Custodial Architecture: cliquetech is entirely non-custodial. Private keys never leave the browser extension (MetaMask, Rabby, etc). All blockchain interactions rely on EIP-1193 standard providers.

Asset Integrity: Clique image uploads are authorized with a fresh wallet signature (EIP-191). The API validates the recovered signer, upload purpose, timestamp, nonce, media type, and size before writing to App Storage; public image responses are immutable. The permanent production origin is used in launch metadata so on-chain URLs never depend on a temporary preview hostname.

API & RPC Behavior

To maintain high availability and circumvent public node rate-limits, frontend reads are multiplexed through a backend proxy at /api/robinhood-rpc.

Blockscout logs (used to detect recent token launches) are proxied through /api/pons/factory-logs. Wallet interactions (writes) bypass the proxy and submit directly to the chain via the user's provider to guarantee transaction integrity.

Contract Reference

Full reference of deployed cliquetech infrastructure.

The factory exposes GATE_INIT_CODE_HASH — the keccak-256 of the CliqueGate creation code. Together with the factory address and the per-creator salt this fully determines every gate address, letting the client verify a predicted gate before any funds move.

Launch & Security Caveats

• Factory Verification: The client verifies the configured gate factory against its published init-code hash. If the chain RPC attempts to present a modified factory, the interface locks out gate transactions.
• No Migration: Once a token is deployed via the Gate Factory, the binding cannot be undone. You cannot transfer fee-claiming rights to a secondary address without migrating the private key of the creator EOA.
• Proxy Trust: Read proxies only provide data availability, not security. Trust assumptions rely entirely on verifiable contract state on Robinhood Chain.

Troubleshooting

Risk Disclosures

Cryptocurrency tokens, bonding curves, and fractionalized real-world assets are experimental technologies subject to extreme price volatility. cliquetech is a permissionless interface interacting with smart contracts on a public blockchain. We do not provide financial advice. The value of any creator token can go to zero. Bonding curves contain inherent slippage and front-running risks. By interacting with these contracts, you acknowledge that you are fully responsible for your own funds, your own wallet security, and your own due diligence.