Devnet iteration 2

Status: implementation in progress Cluster: Solana devnet only Decision set: 0012 and 0013

This record starts before the first external write. It will be extended from the checked source revision through the program update, release activation, fresh Market lifecycle, public ledger, and site deployment. A local test or a devnet execution is not mainnet evidence.

1. Pre-write public baseline

Observed at 2026-08-28T03:45:47Z through one bounded finalized getMultipleAccounts read against https://api.devnet.solana.com. Both RPC responses reported context slot 489,182,510. No signer, wallet file, or browser session was read.

Every Program account was executable and owned by BPFLoaderUpgradeab1e11111111111111111111111. Every ProgramData account was non-executable, owned by that same Loader, and carried the retained authority:

4zrxtw5c4oPLpuTQbLYjRCXFUudvFCNNjzR9LqVQvEwP

The ProgramData lamports sum to 31,772,309,520, exactly DEPLOY_1's parked rent arithmetic. The raw ProgramData-body hashes, which include Loader metadata, were also retained in the local pre-write evidence:

1.1 Second pre-write admission read

During the 2026-08-28T05:12Z minute, three bounded, key-free finalized JSON-RPC reads rechecked the devnet genesis, all seven Program accounts, and all seven ProgramData headers. The account observation returned context slot 489,212,834. Every permanent Program/ProgramData address, Loader owner, executable flag, deployment slot, ProgramData space, and upgrade authority still matched the table above and DEPLOY_1. Because Loader V3 writes the current slot into ProgramData on Upgrade, the unchanged seven deployment slots also establish that no role was upgraded between the two observations. This second read did not claim a new payload digest; the byte-digest baseline above remains the pre-write byte authority.

A separate two-call genesis-and-balance read returned finalized context slot 489,213,774 and exactly 32,185,584,146 lamports (32.185584146 SOL) for the retained deployer. No transaction was signed or submitted. This is the arithmetic baseline that must be read again immediately before the first program-extension or Upgrade transaction.

2. Public-site baseline

This section is a timestamped baseline, not a floating description of the currently deployed site. Each statement below is bound to its named wrapper commit, source commit, workflow run, and HTTP observation. Later deployments must add their own coordinates in §8; do not infer current site contents from this checkpoint.

The same pre-write check requested https://clutch.dregg.pro/ over HTTPS. It returned HTTP 200 from GitHub Pages. The response identified the current page as last modified 2026-08-28T02:30:25Z. This establishes reachability only; the post-deployment cold-browser and chain-reconciliation checks remain owed.

The public checkpoint was subsequently rebuilt from wrapper commit e7f49c022e5913dbbc62005c3781e58752c1de34, whose dclutch/ subtree was byte-for-byte source commit 3b2c7bdd. The intentionally manual Pages run 33143867158 passed the frontend export, documentation assembly, internal-link check, artifact upload, and deployment. An outside HTTPS read then returned HTTP 200 with Last-Modified: Fri, 28 Aug 2026 05:09:20 GMT. The app root, Markets, Activity, Portfolio, Smoke, Bounty, and every sampled linked guide, ABI, refusal, evidence, README, and notices page returned 200. The landing page states the current external boundary plainly: seven programs are live on devnet, there is no open/sample market, and there is nothing to buy or place at risk. This remains a reachability and reader-truth checkpoint, not the owed post-Market cold-browser acceptance.

At the time of this checkpoint, the wrapper source later advanced to 9b965990 with the frame and replay-safety checkpoint, but no Pages workflow was dispatched for that source-only sync. The last deployment observed by this record was therefore the exact, verified e7f49c02 artifact. That sentence is date-bound and must not be read as the current deployment after a later manual Pages run.

3. Implementation gates already landed

• ee309c25, amended by 22adb790: decision 0013 adopts the projected founding v2 source-cap and controller-subset funding design.
• ecf1f2c0: publication and activation resume exact partial progress; substrate preflight checks slot, authority, Loader owner, and privilege. The locked successor suite passed 54/54.
• ebeca73c: SourceMaterialV3 makes the source-policy graph acyclic and derives the complete-set cap at the named integer boundary. Source tests passed 67/67; operator Found tests passed 10/10; Lean regenerated byte-identically.
• 600998f7: the checked-release gate enumerates all 13 shipped SBF links and refuses zero-diagnostic evidence unless every link freshly compiled in the current run. Its focused adversarial suite passed 11/11.

No item in this section is a deployment claim. The source revision, checked ELFs, all-link frame diagnostic, 20-seed compute evidence, program writes, release records, market transactions, ledger, and site revision remain to be recorded below after they exist.

4. Checked source and build

Pending.

5. Program update and wallet arithmetic

Pending. The opening wallet checkpoint from DEPLOY_1 was independently re-read at finalized slot 489,213,774 as 32,185,584,146 lamports; it must be read again immediately before the first signed transaction. No balance in this document is a fee, treasury, reserve, bounty, or protocol principal.

6. Release generation and activation

Pending.

7. Fresh Markets and exterior lifecycle

Pending.

8. Public ledger and site

Pending.