The browser talks to the application API, which proxies the protocol indexer. The API never substitutes local market records when the indexer returns an empty result.
reads come from finalized chain events
The indexer starts at the deployment block, scans confirmed logs, and resolves the current contract state over RPC. Every response includes the latest indexed block and whether a deployment is configured.
If a deployment or record is absent, the corresponding page renders an empty state. Aggregate cards use zero only when the indexed aggregate is zero.
a desk is an NFT-owned account
Desk721 mints an ERC-721 and creates its canonical ERC-6551 token-bound account. The current NFT owner controls scoped protocol actions for deposits, withdrawals, reservations, claims, sales, and redemption.
Owns the desk identity and advances its ownership epoch on transfer.
Holds the attached assets and exposes bounded execution methods.
Settle OTC offers, whole-book sales, shell trades, and reward rounds.
Offers point to one ownership epoch. A desk transfer or redemption makes older offers stale without requiring an offchain cleanup loop.
every enabled action submits a contract call
A reserved amount settles against a defined payment asset and price. Partial fills use cumulative accounting.
The reservation uses a protected onchain reference and a bounded spread at fill.
Payment and the desk NFT move together after the committed minimum balances are checked.
The interface requests the required wallet network, submits through the connected wallet, waits for a receipt, and refreshes indexer queries. A contract address must be present in the indexer configuration before the action is available.
distribution stays O(1)
A funded round increments one global reward-per-desk accumulator. Each desk stores a checkpoint and settles the difference when it is touched. Executing a round does not loop through every desk.
privacy claims stay narrow
Public offers expose their terms through contract state and events. Allowlisted offers publish a Merkle root and require the filler to supply an inclusion proof. Accepted transactions and their calldata remain public.
The fomo-gated path requires both wallet control and a current registry attestation. A wallet signature alone does not establish membership.
test contracts are usable, mainnet is a separate decision
Wallet writes are available when the indexer reports a deployed address. Mainnet requires its own deployment review, governance authority, operational controls, and security clearance.
This documentation describes software behavior. It is not investment, legal, or tax advice, and no return is promised.