RWA Settlement / Robinhood Chain
Every claim.
Beside its
reference.
Zynt exposes the relationship between tokenized claims and the references they settle against — including how old each side of that relationship is.
- Layer
- Claim ↔ Reference
- Signature
- Age Δ
- Verdict
- Alignment
Live settlement object
02Claim Explorer
Search a claim. Get its reference.
Claim id, contract address, transaction hash, asset or reference id. Results always render both sides — the reference is never behind a modal.
Try: a claim label · an asset symbol · PX-… reference · a 0x… address or transaction hash
03Live settlement feed
Settlement activity.
Claims and references as they are read from the registry.
| Claim | Reference | Claim age | Ref age | Age Δ | Status | Source |
|---|---|---|---|---|---|---|
04Age Engine
Every side has an age.
The gap between them is the metric.
age = now − last observation. Both sides of a settlement are measured on the same clock; their difference is the AGE DELTA — a single number that says how synchronised a claim is with the thing that backs it.
Live sample · …
Claim age
--:--:--Reference age
--:--:--Age Delta
- FRESH0 – 5 min
Observed within the fresh window. Eligible for ALIGNED.
- AGING5 min – 30 min
Still usable, but drifting. Watch the delta.
- STALE30 min+
Past the stale threshold. Settlement reads STALE REFERENCE.
Thresholds are configuration, not constants — NEXT_PUBLIC_AGE_FRESH_SECONDS / NEXT_PUBLIC_AGE_AGING_SECONDS.
18s
seconds
02m 41s
minutes
1h 18m
hours
2d 04h
days
05Asset registry
Tracked assets.
One row per asset: its primary claim, the reference behind it, both ages, the delta and the settlement verdict.
| Asset | Type | Claims | Reference | Claim age | Reference age | Age Δ | Settlement |
|---|---|---|---|---|---|---|---|
06How Zynt settles
Three reads. One verdict.
Nothing in the interface is a decoration for a process that happens elsewhere. Each step is a real read, and each read can fail visibly.
- 01
A claim is observed
A tokenized claim is read from the Zynt registry: issuer, contract, value, quantity, block and timestamp. The timestamp starts the claim clock.
getClaim · getBlock
- 02
Its reference is resolved
The claim names the reference it settles against. Adapters resolve it — registry, HTTPS attestation, oracle feed or manual pin — and normalise the answer. No answer is reported as REFERENCE UNAVAILABLE.
onchain · api · oracle · manual
- 03
Alignment is evaluated
Values, timestamps, availability and settlement state are compared on one clock. The verdict is ALIGNED only when everything agrees; otherwise PENDING, STALE REFERENCE, VALUE MISMATCH or UNKNOWN.
age Δ · tolerance bps · thresholds
07Settlement strand
Two paths. Bridged where both were seen.
The upper strand is the claim; the lower strand is its reference. A bridge appears only where an observation exists on both sides — gaps are gaps.
Bridges = paired observations · fade = not yet observed
SVG · CSS · no WebGL
08Protocol statistics
Counted, not estimated.
Read from the registry on every refresh.
Claims
References
Assets
Aligned
Robinhood Chain head
chain 4663 · —
Data mode
onchain
registry configured
Developer / Protocol
Point Zynt at a registry.
The interface is wired end-to-end: viem reads, adapter resolution, the Age Engine and alignment all run against whatever registry and reference sources the environment names. Supply the addresses and the demo dataset disappears.
.env.local
registry set · settlement set · reference api set
NEXT_PUBLIC_RPC_URL=NEXT_PUBLIC_CHAIN_ID=NEXT_PUBLIC_EXPLORER_URL=NEXT_PUBLIC_ZYNT_REGISTRY_ADDRESS=NEXT_PUBLIC_ZYNT_SETTLEMENT_ADDRESS=NEXT_PUBLIC_REFERENCE_API_URL=