Tokenform

Methodology

How facts, sources and uncertainty are recorded.

Distinct instruments, bounded coverage

Each stock is an underlying asset; its issuer-specific instruments have separate financial mechanics and chain-specific deployments. Balance accounting belongs to each deployment, not globally to an instrument. Coverage is not exhaustive: an absent asset, issuer or chain does not imply unavailability.

Structure and rights summaries describe the issuer’s account, not an independent legal determination or reserve audit. Ondo total-return tracking describes economics, not an established legal security classification.

Sources and observation dates

Facts cite issuer product pages, documentation, registries and chain indexers; an indexer is not an RPC observation. EVM eth_call evidence retains the chain, address, block number, hash, timestamp, blockReference (hash or number), finality (finalized, safe or latest), calldata and result. Solana getMultipleAccounts evidence retains the chain, genesis hash, address, context slot, commitment and parsed mint result (decimals, owner, account type and initialization). A context slot is not a block timestamp. Each source’s checkedAt is consultation time (RPC response completion), not publication or chain time. Rebuilding does not refresh it.

Family-level documentation explains a published mechanism, not an observed dividend event or a test of a particular deployed contract. Dividend summaries retain applicable withholding; deployment balance accounting distinguishes adjusted balances, per-token exposure and scaled UI amounts.

Source-backed facts and unknowns

A green check means support from the cited sources, not whole-contract verification or a safety assessment. Issuer-published addresses and documented decimals retain their citations; RPC evidence supports only the decimals result in its recorded chain context, not legal rights, reserves, lifecycle or current trading availability. Explorer links are provided for navigation.

Unknown means the value is not established; JSON retains null with an explanation rather than substituting zero or false. Omitted fields are not claims about their values. Public schema v5 JSON includes facts, source references and bounded chain coverage; instrument records include their underlying asset and relevant sources. Deployment addresses follow the registered chain format: EVM hexadecimal, Solana base58, TRON base58check, TON raw or user-friendly forms, or native Cosmos bank denominations. Provider identities are separate from legal issuer facts. Balance accounting is a deployment fact; omitted instrument balance is not an unknown global value.

Dated market metrics

Stock prices are Yahoo Finance regular-market USD prices for the exact listed share, not after-hours or token prices. Stock market caps are Yahoo-reported equity capitalizations; share-class methodology is not independently confirmed and an effective cap date may be unavailable. CoinGecko supplies coin-level token prices and reported circulating market caps, not per-chain quotes, FDV or independently audited circulation. Exact chain/address mappings identify the instruments; token-unit equivalence to raw chain balances or underlying shares is not established.

These are stored snapshots, not live or executable quotes. As-of times are the stock market time or CoinGecko provider update time, not necessarily a token trade time. Retrieved times mean response completion; an unknown effective date stays unknown. Refresh failures preserve last-good values and their original dates. Missing values remain unavailable. No price or cap is derived by summing deployments, multiplying supply, or substituting an underlying stock price. Expanding the details exposes precise values and source qualifications.

Retrieval

Read pages over ordinary HTTP without an account, API key or wallet. Use /stocks.md for an overview and /stocks.json for the complete structured catalog. Stock and instrument records have explicit .md and .json URLs, such as /stocks/apple.md and /stocks/instruments/apple-xstock.json.

Request a regular page URL with Accept: text/markdown to select Markdown; when listing both formats, use Accept: text/markdown;q=1, text/html;q=0.5. Explicit .md and .json URLs select their format directly. Use full instrument records for deployment balance accounting, decimals and lifecycle details.