what this is · how to use · receipts and rent · ticket and cut · addresses
People ask: if we issue a token, what is it for?
One line: the future token may identify the holder set for a separately verified fee distributor. The token itself does not create revenue or make distribution automatic.
| Paper | What you hold |
|---|---|
| NVDA receipt | A Jersey warehouse note. Price path + rent already glued into the multiplier. Not NVIDIA equity. |
| P / Y settlement claims | Independently redeemable receipt claims after the sealed NVDA batch. Public deposits are accepted only while an NVDA batch is in its funding window. |
| Our token | Not issued. A reserved address slot exists in V2 core, but no fee distributor is bound. |
Rent lives on the receipt. Whoever holds the receipt carries that ~0.08%. Our token does not drip NVIDIA’s dividend. “Hold this token = collect NVIDIA yield” is false.
A verified settlement tool may charge a disclosed fee. A separate distributor would then account for and pay eligible token holders. Neither component is deployed yet.
The V2 core now has a bound settlement module and an empty ticket address slot. Filling the ticket slot later will not by itself move fees or enable claims.
Pay holders. Dollar book. No buyback. This remains a design target, not a live promise.
The distributor must define eligible balances or snapshots, accepted assets, accounting, duplicate-claim prevention and solvency before the ticket is issued.
No V2 settlement fee is live. The old V1 pair-token experiment charged a posted fee, but it is retired from the interface and is not the independent V2 settlement.
The reservation core and settlement module are deployed. NVDA batches use the deploy wallet as trusted signer. Public deposits do not start holder distribution. Issue the ticket only after a separately reviewed distributor exists.