Canonical onchain
Registry + usage
Hub events establish the catalog. Daily Avalanche Parquet logs plus an RPC tail establish complete Transfer history; live calls establish supply, balances, controls, and implementations.
HIGH CONFIDENCEAvalanche C-Chain / Asset register 001
Dinari dShares
on Avalanche.
A live evidence desk for Dinari’s dShare deployment: every contract pair, every unit of observed supply, and the shared machinery that can move or freeze it.
ECONOMIC FOOTPRINT—
—of — native contracts carry supply
- —
- estimated active value
- —
- observed current holders
- —
- wrappers with supply
- —
- failed pair invariants
Market value uses Dinari’s ticker feed as a reference. The contract registry and token state come directly from Avalanche RPC.
1,446 TOKEN CONTRACTS✳
1 SHARED DIAMOND✳
2 UPGRADEABLE BEACONS✳
9 SHARED BRIDGE DECIMALS✳
1,446 TOKEN CONTRACTS✳
1 SHARED DIAMOND✳
01 / Registry pulse
Broad catalog.
Thin footprint.
The deployment surface is enormous; current C-Chain utilization is not. Read breadth and economic use as separate facts.
02 / Live capitalization
The five with a pulse.
03 / Control concentration
Many shares.
One switchboard.
Every native token delegates access, restrictions, registration, and routing to the same hub. Both proxy families can change together through two beacons currently owned by one EOA.
The one-line read
Programmable claims on custodied securities—not trustless bearer shares.
Solvency, legal entitlement, mint discipline, redemption, corporate actions, identity, routing, and upgrades retain offchain or privileged dependencies.
Asset registry / 723 pairs
Every ticker.
Every contract.
Canonical discovery comes from hub creation events. Names and symbols are labels; asset ID and contract address are identity.
| Asset | Status | Native supply | Ref. price | Est. value | Split ratio | Deployed |
|---|
Usage ledger / Full contract census
Follow the
actual use.
Every native and wrapped contract is checked from deployment—not only today’s funded assets. Wallet movement, primary issuance, addresses, and marked value stay separate so activity cannot masquerade as liquidity.
Marked movement / USD
Two kinds of volume.
Wallet transferMint + burn
Address participation
New versus returning.
Asset contribution
What drove the tape.
30-day window
| Asset | Current TVL | Wallet volume | Primary flow | Active addresses | Transactions | Last activity |
|---|
Holder concentration
Current balances.
Metric boundary
Read the labels.
Latest indexed events
The transfer tape.
| Time | Asset | Type | Amount | From | To | Transaction |
|---|
Control plane / Privilege map
723 doors.
One master key.
Centralization is a feature of regulated token servicing—and a correlated failure mode. This map shows what can change all at once.
Risk register
Where trust enters.
Diamond loupe / Live
Selector surface.
—
Known high-privilege principals
Current role masks.
Six principals checked live; the research snapshot also found 100 role-5 EOAs.
Method / Boundaries
Know what
the chain knows.
Onchain precision does not erase offchain dependencies. This page draws the evidence boundary explicitly.
Issuer reference
Prices + process
Dinari’s public ticker feed supplies indicative market references. Product docs describe onboarding, custody, dividends, redemption, and jurisdiction rules.
SOURCE-DEPENDENTOffchain unknown
Reserve + rights
The chain cannot prove shares held at a broker, legal claim priority, named attestation coverage, SIPC treatment, or execution quality.
DILIGENCE REQUIREDSystem map
Five systems, not one token.
1Investor / partnerKYC, wallet, order
→
2Brokerage stackexecution + records
→
3Custodytraditional security
↕
4C-Chain dShareprogrammable claim
↔
5DFN / other chainsseparate coordination
Live quarantine rules
Eight checks per pair.
Any deviation should quarantine the asset for review.
Source register
Follow the evidence.
External claims stay labeled and linked.
Independent analytics. Not an audit, reserve attestation, legal opinion, or investment recommendation.