Reading the chain
Every number on the next screen comes from the vault contract, as it stands in the latest block.
Reading the chain
Every number on the next screen comes from the vault contract, as it stands in the latest block.
Proof
Every line below is read from the chain when you open this page, and links back to it. If a figure here ever disagrees with the contract, the contract is right.
Ledger
One row each, written by the vault itself in the transaction that did it.
ETH spent on stock
0
0 purchases
NVDA bought
0.0000
0.0000 in the vault now
SPY bought
0.0000
0.0000 in the vault now
$HYBRID burned for stock
0
0 redemptions
Reading the ledger…
These rows live in the vault contract itself, not in a database of ours: purchases(), claims() and redemptions() return them to anyone who asks.
Meter
A coin whose biggest trader is its own team is telling you something. This is where you check ours.
From our own wallets, last 7 days
–
not counted yet
From our own wallets, since launch
–
not counted yet
Nothing has traded, because the coin does not exist yet. The count starts with the first block the coin trades in.
Listed here at launch: the team wallet, the dev lock, the account that launches and the caller script's wallet.
A trade by any of these counts against us. A wallet of ours that is not on this list would be a lie on this page, so there is none.
Contract
Including the powers that sit with someone else.
These are absences in the code, not promises. Once the vault is deployed, its source goes on the explorer, where anyone can search it for any of them.
Nothing is deployed yet
The launchpad's owner can redirect a coin's future fee after a 3-day wait; stock already in the vault is out of its reach. The stock tokens' issuer can pause them or block an address, which would stop redemptions until it is lifted.