50 + 20 / 100 + 40
Regular and Premium fixtures received their Genesis Gift and daily reward. Their wallets paid the claim transaction fees.
70 and 140 test IAT receivedZ4 // BUILD IN PUBLIC · 25 OCTOBER 2026
The reviewed Z4 upgrade, Genesis allocation and funded claim paths ran with the original Model T admin and the same Devnet mint. The X accounts and subscription evidence in this rehearsal were synthetic; live X verification still needs an end-to-end test.
The next build releases 125M of the 500M community IAT at Genesis. The remaining 375M stays locked for six calendar months, then releases linearly over 36 months, finishing at month 42. Initially unlocked non-core reserves become 225M IAT.
The candidate passed 98 Node tests, 4 Rust tests and 24 compiled-program tests, including rejection of spending beyond the unlocked community balance. These are local checks. The existing Devnet configuration and network receipts below use the earlier community policy; this revision still needs a fresh Devnet activation rehearsal.
Community vesting candidate and validation · Current allocation and release rules
The new build rejects a weekly payout if its reserve sources changed after the payout list was prepared. It also saves the exact signed transaction before sending, so recovery can check the same transaction. Local checks passed 87 Node tests, 3 Rust tests and 20 compiled-program scenarios. The narrow source review found no reportable vulnerability; it covered the weekly funding changes, with the scope recorded in its evidence.
The original Model T approved the upgrade on 9 October. All 591,032 deployed bytes match the reviewed build, with the same mint, policy and admin. All 16 program accounts and 11 token accounts stayed unchanged during the upgrade. Its closed buffer returned exactly 3.00328076 test SOL to the publisher. No weekly reward batch has been funded on the public network.
Finalized upgrade and exact deposit return · Completed network checkpoint · Local funding and claim checks · Review scope and result
The first weekly commitment deadline passed on 8 October. That result remains pending under the fixed-randomness rules; we cannot backdate a commitment or choose an already-known draw. Automatic weekly operation and funded claims remain release checks.
The new daily service reserved capacity from immutable, ordered validation records, then activated and paid 20 test IAT in one transaction. A lost network response and a service restart recovered the same finalized signature: one holder signature, one verifier signature and one broadcast. The existing disposable test holder reached 90 test IAT.
Durable daily claim evidence · Earlier atomic browser claim
The earlier Model T upgrade on 6 October added receipt-refund support. Its 15 program accounts and 11 token accounts stayed unchanged. Its temporary buffer closed and returned 3.00015148 test SOL to the publisher.
Upgrade and exact deposit return · Early cleanup rejection test
On 9 October, the paid daily receipt closed after its real 72-hour evidence window. The recorded holder received the full 0.0015748 test SOL deposit. The publisher paid a separate 0.000005-test-SOL cleanup fee; the holder needed no new signature. Every remaining program account, token balance and reserve record stayed unchanged.
A wrong refund recipient was rejected before submission. After cleanup, simulations rejected both repeat cleanup and a replacement reward for the old earning day. The receipt closed once, leaving 15 program accounts and the same 11 token accounts.
Finalized refund, event and replay checks
Active unclaimed rewards stay open until payment or processed expiry. Permanent X bindings and Genesis receipts stay open. This rehearsal used synthetic X evidence; genuine social eligibility, human wallet review and hosted claim operation remain release checks.
Regular and Premium fixtures received their Genesis Gift and daily reward. Their wallets paid the claim transaction fees.
70 and 140 test IAT receivedNine decimals. All tokens reconcile across allocation vaults, campaign escrows and the two test holders. Mint and freeze authorities are revoked on Devnet.
Original hardware admin retainedAll four claims finalized while new campaigns and manifests were paused. The Model T then resumed Devnet operation.
Replay and recipient checks rejectedThe Model T approved a separate Z4META fixture: 1B test tokens, fungible metadata, then immediate mint and freeze authority revocations in one finalized transaction. An independent decoder verified the supply, metadata and revoked authorities. The existing IAT rehearsal mint was unchanged.
View isolated metadata test · Independent verification
This separate fixture is not the official IAT token. The unsigned Mainnet metadata simulation submitted no transaction and proposes no Mainnet addresses.
Every receipt below is on Devnet and uses test IAT or test SOL. Open a receipt to inspect its transaction, accounts and finalized slot.
| Action | Finalized slot | Receipt |
|---|---|---|
| 1B test mint + authority revocations | 506,654,712 | View transaction |
| Publisher funded with 2.7 test SOL | 507,270,293 | View transaction |
| Reviewed program upgrade | 507,272,649 | View transaction |
| Current launch policy pinned | 507,273,076 | View transaction |
| Five allocations + Devnet Genesis | 507,273,416 | View transaction |
| Genesis Gift: 1M test IAT reserved | 507,273,647 | View transaction |
| Daily X pool: 100,000 test IAT reserved | 507,273,660 | View transaction |
| Pause new campaigns/manifests | 507,275,671 | View transaction |
| Regular Genesis: 50 test IAT | 507,275,821 | View transaction |
| Regular daily: 20 test IAT | 507,275,835 | View transaction |
| Premium Genesis: 100 test IAT | 507,275,860 | View transaction |
| Premium daily: 40 test IAT | 507,275,874 | View transaction |
| Resume Devnet operation | 507,276,888 | View transaction |
| Separate metadata fixture + immediate authority revocations | 507,324,981 | View transaction |
| Browser Genesis claim with reload recovery | 507,642,017 | View transaction |
| Atomic daily browser claim | 507,663,340 | View transaction |
| ProgramData extended for receipt refunds | 507,991,876 | View transaction |
| Model T receipt-refund upgrade | 507,996,636 | View transaction |
| Durable service daily claim with restart recovery | 507,998,814 | View transaction |
| Original wallet funds publisher: 0.1 test SOL | 509,073,387 | View transaction |
| ProgramData extended for source-checked weekly funding | 509,073,739 | View transaction |
| Verified upload buffer assigned to original Model T | 509,076,092 | View transaction |
| Model T source-checked weekly funding upgrade | 509,090,761 | View transaction |
| Daily receipt deposit returned to recorded holder | 509,091,176 | View transaction |
Four additional simulations rejected Genesis replay, daily replay, a wrong recipient and a Premium regrant for an already-paid regular wallet-day. These checks submitted no transactions. They prove the issued grant could not be reissued; they do not establish real X subscription history.
FUp5Tr8zQirPaNtyeEKCgK5sJQseppj8HfVzx7BhWBYrHjZ7pjQ5QBiXQM15VvaoF81UuvQucDVeREzgyY6pEXfT7XZjd7aNNci63LZy9syqgjvjNHvkQ83Uwo7cyynrfzPH5a02895b384d78b9af0d4692b225b6f61a1a1ab7d468536df8dfee711a20e16f618c2d0627dcea045fd0cd4bc368d6bbf9442a1fc2236cb37a9887a3c6a0160bThe deployed bytes match the reviewed build. The fixed 1B test supply cannot be increased through a mint authority; the Model T still controls program upgrades. These addresses identify the rehearsal and are not a Mainnet IAT mint.
A hardware-approved payment of 0.0022 Mainnet SOL plus 0.000005 SOL fee obtained 2.2 Devnet SOL at the same original address. This was test funding only.
Mainnet faucet payment · Devnet delivery
The publisher received 2.7 test SOL for the upgrade and rehearsal. The temporary upload buffer was closed and its 2.93695628-test-SOL rent deposit returned to the publisher.
Local checks and this Devnet claim rehearsal are development evidence. They are not a security audit or a completed Mainnet launch.
| Area | Current state |
|---|---|
| X login and reward evidence | Read-only API checks, synthetic browser claims and durable daily-service recovery passed. A genuine holder’s login/follow/repost and hosted service operation remain to rehearse. |
| Receipt deposit refunds | The mature public-chain refund passed: full deposit to the recorded holder, unchanged custody, and rejection of repeat cleanup and old-day reward replay. Hosted cleanup integration remains to complete. |
| Staking, CCC and factions | Finalized balance replay reconciled the 1B test supply. Local funding, claim, source-race and beacon checks pass. Timely public commitments, subsequent CCC snapshots and actual funded weekly claims remain to rehearse. |
| Mainnet release | Pending security/release review, final Mainnet addresses and transaction plan, and deployment funding. No Mainnet program or token has been deployed. |
The 7 October quote for the 591,032-byte reviewed build is approximately 3.04082 SOL for initial deployment and startup accounts; 3.2 SOL is the planning budget with headroom. A first deployment uses the upload buffer’s balance to fund permanent ProgramData. It does not return an additional full buffer deposit. For an upgrade of an already funded program, the separate temporary buffer can return its deposit, as the earlier Devnet receipt demonstrates.
Approximately 3.02733 SOL stays deposited while startup accounts are used. The estimate also includes a 0.01-SOL metadata protocol fee; transaction and protocol fees are not refundable. Priority fees, RPC, X API, hosting and liquidity provisioning are excluded. Refresh this planning estimate before deployment.
Read the reviewed-build rent and fee assumptions · Verify the actual Devnet deployment balance flowWe will publish the canonical mint and program addresses, 1B supply, allocation vaults, vesting state, mint/freeze revocation signatures, upgrade authority, publisher limits and release results. Mainnet mint and freeze authorities will be revoked immediately and their finalized proofs published.
The latest rehearsal proofs are available on this page. Their GitHub sync remains pending.
Earlier builds remain historical evidence. They do not activate Z4 or define its current reward rules.
Read the historical proof archive