Protocol reference

1. Architecture

One canonical Ethereum Sepolia ERC-721 collection records 1,111 possible Deeds. Destination registries hold activated snapshots. A RuntimeFactory creates an immutable Runtime per Deed on first app publication. Each Gateway executes its implementation through delegatecall using its own storage. Apps must use the documented execution context and enforce their own permissions.

The source collection stores owner, revision, USD-denominated toll, information and recipient allocations. Ownership transfers increment the revision and clear custom recipients. The five destination registries store attestor-approved snapshots bound to the collection and destination, including the source block and expiry for activation. They do not mint a second Deed or automatically synchronize transfers.

A factory creates at most one Runtime per Deed on its network when first requested, including through publication. Publication deploys a distinct Gateway with an immutable Runtime, implementation and Deed identifier. Application code executes through delegatecall against that Gateway's storage. The Runtime's registry, oracle, treasury and factory bindings are immutable in this deployment.

2. Economics and trust

The current mint is 0.001 test ETH with no reserved NFTs and one public mint per wallet. Tolls range from USD 0 to USD 2 and settle natively with 90% allocated to owner recipients and 10% to the treasury, subject to rejection rules. The testnet uses a trusted attestor and test price feeds.

An execution names the Gateway and encoded call, configuration revision, maximum toll, appValue, application gas limit and deadline. The Runtime checks registration and current configuration, quotes the toll and requires exact native value for toll plus appValue. It sets executingUser and executingApp during application execution and clears them afterward. Application failure reverts the operation.

After successful application execution, the Runtime calculates the protocol portion with integer rounding and allocates the remaining toll to the owner or configured recipients. Rejected recipient amounts go to the treasury in the same execution. A treasury payment failure reverts all execution effects. Paid, Redirected, TreasuryPaid and Executed events allow the website to distinguish successful allocation from redirection.

The collection declares a separate 10% resale royalty to its immutable treasury. It does not implement a mandatory charge on every free transfer. The toll split is payment routing for actual executions, not a distribution of a builder's profit or a promise of yield to NFT holders.

3. Verification and integration

Use the Contracts page for the active collection, treasury and network addresses. Existing networks do not inherit another network’s app deployments. Source checks must match the current release; historical tests are not evidence for different bytecode. Builder guides describe initialization, selectors, payment bounds and authorization. See the risk and security documents for limitations.

The source is Ethereum Sepolia (11155111). Destinations are Robinhood Testnet (46630), Base Sepolia (84532), Ink Sepolia (763373), Arc Testnet (5042002) and ApeChain Curtis Testnet (33111). Each network has its own factory, Runtime instances, gateways and oracle. The Contracts page and /api/release identify the currently configured addresses.

Native quotes use ceiling division and the network oracle. Non-stable references expire after two hours for nonzero tolls; Arc uses its fixed native test-asset reference. USD or ETH screen preferences change presentation only. They do not select a different payment asset or write a new toll.

The website indexes events into PostgreSQL, handles duplicate events and reorganizations and presents time-stamped revenue snapshots. A cache can outlive the latest index attempt, so delayed data is displayed with its age rather than treated as a fresh quote. Directory profile updates use signed, versioned messages and do not change contract ownership.

4. Documents and action authorization

Docs is a reference reader inside the website. Minting, configuration, profile updates, destination activation and application publication do not require a checkbox or separate terms signature. The website does not collect new terms acknowledgments.

The wallet still authorizes each requested transaction or signed profile or activation message. These controls are independent of the document reader. Earlier saved acknowledgment records and their document bytes are preserved as historical evidence, not used as a gate for current actions.

5. Scope of this reference

This document describes the configured testnet release, not a roadmap or an offer of a future asset. It supplies no valuation model, migration commitment, income forecast or claim of regulatory approval. Source verification, test evidence and standards references are useful checks but must be matched to the specific deployed addresses and bytecode.

Deployment references for this release

Collection

0x8f0b8eacacad43bd8b86b2305a20bb4a7007faba

Treasury

0x224385Bd4dBe4c5cb0ab469fe06ACdA734541A94