How the house is built.

What is operational

• Asset directory — 21 verified records from 5 issuers (registry 2026.11.09-1). Search, category, issuer and network filters, sorting, URL-persisted state, comparison of up to three assets, a device-local watchlist and CSV export of public records.
• Asset detail — identity, holder rights, redemption, eligibility, transfer restrictions and fees as documented by the issuer, with a source link and the claim each source supports. Unknown facts read "Not provided".
• Portfolio reader — read-only balance reads for the registered assets on Robinhood Chain and Ethereum, by connected wallet or pasted address. Correct decimals and balance semantics; unpriced positions are never counted as zero; partial and stale totals are flagged.
• Reference prices — Chainlink feeds read on-chain with validity checks, issuer indicative quotes, and DefiLlama aggregates, each with provider, timestamp and freshness. Never an executable quote.
• Activity — observed ERC-20 transfers of registered assets from public explorer APIs.
• Screen privacy — masks values on your display only.
• Transparency — live network probes, feed inventory, contract list and integration status, also as JSON at /api/status.

What requires external configuration

• Shield and unshield — a reviewed privacy-protocol adapter registered in src/lib/privacy/adapter.ts. Status: Not configured.
• Sealed batch orders, settlement and cancellation — a reviewed execution adapter registered in src/lib/trading/adapter.ts. Status: Not configured.
• Cryptographic eligibility verification — a credential or proof provider registered in src/lib/eligibility/adapter.ts. Status: Not configured.
• Provider RPC endpoints — optional. Key-free public endpoints are used when ROBINHOOD_RPC_URL and ETHEREUM_RPC_URL are unset.

How records are verified

Each asset record is built from primary issuer documentation and confirmed on-chain: the contract's name(), symbol() and decimals() are read and compared with the issuer's registry or API, and every Chainlink feed is read for description(), decimals() and latestRoundData() and matched against the Chainlink directory. The verification method and timestamp are stored on the record and shown on the asset page. The script pnpm verify:registry repeats the on-chain part and fails on any mismatch.

Live previews

The landing page previews are live: the hero panel shows reference prices for real registry assets from the same price API as the app, and the portfolio section reads a real address (your connected wallet or lookup when there is one, otherwise a public example address on Robinhood Chain). Nothing is invented, and a failed read is shown as an error rather than replaced with placeholder figures.

Project token

The $MAGCIFENT identifier appears in the navigation and footer with its contract address once published ("CA soon" until then). It is published through pnpm token:ca <address>, which validates and checksums the address and records the chain and explorer link. No price, market data, rewards or rights are implied.

Storage and privacy

Watchlists, the screen-privacy preference, and the last read-only lookup address live in this browser's localStorage. They are local to the device and profile, not synced and not sent to a server. No analytics are loaded. Wallet addresses are sent only to this site's own API routes to read public balances.

Claims and copy

The launch headline reads "Real-world assets. Privacy in your hands." because the supported instruments give economic exposure rather than direct ownership of the underlying. Copy about shielding, sealed orders and eligibility proofs appears only once those integrations are configured and verified.

Continue with the privacy model or the integration rules.