EST. 2026 · V1.0.0Robinhood Chain
UseCert monogram

Stock certificates · Minted on Robinhood Chain

Loading vault0%

Addresses

Every contract, and where to read it

All 34 contracts behind UseCert, on Robinhood Chain (chain 4663). Every one publishes its source on the explorer, so each link lands on code rather than bytecode.

These come from the same generated module the app transacts against — not a list kept by hand beside it — so this page cannot drift from the contracts the dashboard is actually talking to.

Verified code evidence · Sourcify

Verification evidence unavailable right now. Every address below links to its Sourcify lookup.

This shows public source/bytecode verification status for these addresses on Robinhood Chain. It does not prove a signed release, an audit, the website build, the keeper's or attester's behaviour, a hedge or fill on the venue, collateral sufficiency, settlement, redemption, custody, dividends or voting rights. Certificates are synthetic exposure, not shares.

Shared · 4

Holds every attestation and its timestamp. ageSec() here is the number the dashboard publishes.

maxNotional18() — the mint ceiling. Returns zero while an attestation is aged out.

A registry, not a deployer. It stopped constructing vaults when doing so pushed it past the EIP-170 size limit.

Real USDG, 6 decimals. Nothing in this deployment mints it; the vaults only hold what holders deposit.

uTSLA · 5

venue market 16 · verified

Holds the collateral, runs the hedge, and is the only contract that can mint or burn the certificate.

The ERC-20 you actually hold.

px() and the three guards — staleness, deviation, basis — whose thresholds the risk table reads from here.

The accrual ledger.

Chainlink price feed, 8 decimals, total-return. Read only through CertOracle, which applies the guards.

uSPY · 5

venue market 26 · verified

Holds the collateral, runs the hedge, and is the only contract that can mint or burn the certificate.

The ERC-20 you actually hold.

px() and the three guards — staleness, deviation, basis — whose thresholds the risk table reads from here.

The accrual ledger.

Chainlink price feed, 8 decimals, total-return. Read only through CertOracle, which applies the guards.

uQQQ · 5

venue market 25 · verified

Holds the collateral, runs the hedge, and is the only contract that can mint or burn the certificate.

The ERC-20 you actually hold.

px() and the three guards — staleness, deviation, basis — whose thresholds the risk table reads from here.

The accrual ledger.

Chainlink price feed, 8 decimals, total-return. Read only through CertOracle, which applies the guards.

uNVDA · 5

venue market 15 · verified

Holds the collateral, runs the hedge, and is the only contract that can mint or burn the certificate.

The ERC-20 you actually hold.

px() and the three guards — staleness, deviation, basis — whose thresholds the risk table reads from here.

The accrual ledger.

Chainlink price feed, 8 decimals, total-return. Read only through CertOracle, which applies the guards.

uAAPL · 5

venue market 10 · verified

Holds the collateral, runs the hedge, and is the only contract that can mint or burn the certificate.

The ERC-20 you actually hold.

px() and the three guards — staleness, deviation, basis — whose thresholds the risk table reads from here.

The accrual ledger.

Chainlink price feed, 8 decimals, total-return. Read only through CertOracle, which applies the guards.

uMSFT · 5

venue market 14 · verified

Holds the collateral, runs the hedge, and is the only contract that can mint or burn the certificate.

The ERC-20 you actually hold.

px() and the three guards — staleness, deviation, basis — whose thresholds the risk table reads from here.

The accrual ledger.

Chainlink price feed, 8 decimals, total-return. Read only through CertOracle, which applies the guards.

What "verified" does and does not mean here

Source for all 27 contracts is published on Sourcify with an exact match on the runtime bytecode. The contracts this deployment created directly also match on creation bytecode; each vault's certificate and buffer ledger are created inside the vault's own constructor, so they have no creation transaction of their own to match.

Every mirror's venue market index was read from the venue's own market list before deploying, by a preflight that refuses a market the venue does not list. The index is immutable, so a wrong one could only be fixed by redeploying.