Declared #001
What this launch declared before it happened
Signed with the wallet that deploys, before the token exists. Every line below is something a launch transaction or a payout hash either matches or does not.
The signed text
vitals declaration deployer: 0x447c8dc55B88C09830E123f9fB3e7C484714ED93 dev buy: 5% of supply, held by the deployer wallet, 2% team and 3% partnerships, vesting contracts in october, nothing distributed at launch tax-free at launch: the deployer only creator tax: 400 bps tax split: 10% the room, 10% ecosystem, 80% the build, treasury rules as declared the room: BLOCK ZERO is 3 seats today, the deployer and two others, who say they are crew whenever they post. the room is owed 10% of the fee wallet's cumulative gross income, paid daily in ETH for 30 days, split equally between the seats held that day, every payout printed before it leaves and recorded with its hash. seats are added after launch on what people actually did, given by the deployer, never sold and never given for a payment. when a seat is added the split is recomputed from that day's payout forward and printed with it. a seat given up is reused and both occupants stay in the history. 10% of gross income goes to ecosystem integrations, 80% to the build: development, infrastructure, integrations and the dev's pay. holder fee share is off at launch. the token is access, not yield: 250k = watch, 1M = the holder feed, 10M = desk. nothing changes in the first 10 days. the room reviews it with holders on 9 oct. any change is announced 7 days ahead. docs: https://checkvitals.xyz/declared/001 nonce: <issued by the bot, one per draft>
This is the text the deployer wallet signs, with one line added
at the moment of signing: docs sha256:, the hash of this page as it
was then. It cannot be printed here, because the hash of a page cannot be part
of the page. The bot stores the signed bytes and the signature together, so the
claim stays checkable against the launch that follows it.
Treasury rules
treasury: 0x138826536Ca720C4D614550D5DB2b22216d136ad. funded by sweeps from the fee wallet after each room payout, every sweep recorded with its hash. it may hold up to 10% of its ETH in other robinhood chain tokens. positions are discussed in BLOCK ZERO, executed and signed by one wallet, and every trade is posted with its hash on X within the hour. realized gains return to the treasury and count as income, so the room receives its 10% through the same ledger. no separate profit share, no promises. the treasury does not trade $VITALS. one signer. no other wallets. no OTC.
Holder fee sharing
holder fee share is off at launch. the token is access, not yield: 250k = watch, 1M = the holder feed, 10M = desk. nothing changes in the first 10 days. the room reviews it with holders on 9 oct. any change is announced 7 days ahead.
The room
the room: BLOCK ZERO is 3 seats today, the deployer and two others, who say they are crew whenever they post. the room is owed 10% of the fee wallet's cumulative gross income, paid daily in ETH for 30 days, split equally between the seats held that day, every payout printed before it leaves and recorded with its hash. seats are added after launch on what people actually did, given by the deployer, never sold and never given for a payment. when a seat is added the split is recomputed from that day's payout forward and printed with it. a seat given up is reused and both occupants stay in the history. 10% of gross income goes to ecosystem integrations, 80% to the build: development, infrastructure, integrations and the dev's pay.
What can be checked, and where
- The deployer is the sender of the launch transaction.
- The dev buy is the opening buy on the curve, as a share of supply.
- Tax-free at launch is the list of wallets the launch transaction pre-exempts.
- The creator tax is a field in the launch parameters.
- The room's payouts are transaction hashes, published after each run.
- Sweeps into the treasury are transaction hashes, recorded as they happen.
- One signer, no other wallets, no OTC is readable off the treasury address's own transaction list.
What this page is not
It is a claim made in advance, not a finding. Nothing in it was checked against a chain at the time it was made. After the launch, the scanner compares what the chain shows against what was signed here, and where they differ it says so and the original finding still stands.
There is no score, no grade and no verdict anywhere in this project. A check that found nothing is not a check that found the launch to be fine, and the card says how many checks ran and how many could not be determined.