Now, Situation, Board and Market, read from the document

The frozen Now and Situation pages, with their inlined data taken out. Each page reads a contract v3.7 document when it loads and runs the rule "Now at t" in the browser, so the rail rewinds against the document. Now opens the staged Solana document by default: the first document whose history begins at a real first admission on the tape.

What build-7 changes

Contract v3.7 (CHANGES-v3.7.md) widens a supply read's amount from a u64 to an integer of up to 78 digits, so an 18-decimal token's supply can be admitted. The BSC real document (螃蟹) is re-assembled from the same pinned tape and RPC bytes with its supply read admitted: 1,000,000,000,000,000,000,000,000,000 base units at 18 decimals, read at 13:27:21Z on block 124532613 and unchanged at 13:27:36Z. The Solana document is byte for byte build-6's.

Board and Market now print a supply line under the cap slot wherever a supply read is valid at the moment shown: Supply 1,000,000,000 on BSC, with the read clock, the block and the exact count in its title. The cap slot follows the contract's display rule: a figure only when the supply and a USD price are both read at that moment. The BSC pool is quoted in oANTHROPIC and its tape carries no USD price, so the cap slot still says cap not read, and its title now gives the cause, no USD price at this moment, instead of saying the supply was not read. STONK on Solana reads the same way. The contract's wide fixture, Market on fixtures/now-v37.json and Board, shows the figure form: KESTREL, an illustrative BSC row with the same 18-decimal supply and a USD price, prints MC $61.8K at 17:27Z. Now and Situation are unchanged.

What build-6 changes

Now stops printing 0 entered where the document refuses a count. On both real rows cumulativeDistinctEntrants is null with the reason no attributable first buy on this tape; every buy is attributed to its transaction signer, not a transfer-correlated recipient, while every wallets interval carries 0. Contract v3.6 (§7.4, CHANGES-v3.6.md) writes the never-zero rule as the reader applies it: a null cumulative stays null at every moment, with the document's reason, whatever the intervals sum to. Now on the BSC document now reads no USD price at this moment · entered not counted · profiled participants not read by this assembly · 2 seen · holders not read · safety not read, and on the Solana document the same with 61 seen; the entered slot carries the reason as its title. Situation already said not counted. No field and no schema change, so the documents are unchanged. On the fixtures and the staged documents every page renders as in build-5, and Board, Market and Situation render as in build-5 on every document. The shots now cover both real documents:

What build-5 changes

Board and Market now open on the real documents, and two page faults the real rows showed are fixed. Board on the BSC document (and on the Solana document) builds its card from the Now row alone: no Board document, no Situation document and no member context is made up. The card says New to you with the row's own reason, No member context.; the cap slot says cap not read, titled supply not read at 13:27Z, because no USD price is read (contract §7.6a); the price is the row's native quote, 0.000000349 in oANTHROPIC, with the exact literal in its title; there is no entry line, because no Board document carries an entry. Market is pass 9's page reading the document's market reading. Market on the BSC document has no reading, so the band says Market not read yet and each of the eight lines prints its title and one reason: no USD price at this moment on the five that need a USD figure, Market not read yet on the other three. The Now fix: a row whose wallets intervals all count zero no longer draws bars with a zero maximum, so Now on the BSC document logs no errors. The Situation fix: the BSC row prints its price as 0.000000349, in fixed notation to three significant digits, and it fits its cell. The real documents open over http only. On the fixtures every page renders as it did in build-4 (Board as build-1b, Market as pass 9).

What build-4 changes

Situation gains the Money in/out track under Wallets in, as pass 13 Situation drew it, with its compare row, its what-changed item and its Evidence block. The track now reads the Now row's flow series from the document (contract v3.5, item 1): per interval, buy USD up from the zero line, sell USD down, and a net tick that the page works out as buy minus sell. An interval appears only once its availableAt has passed at the page minute. An interval the tape did not read is hatched, with its reason as the hatch title. A row whose chain tape is not read shows one hatch and the document's reason. Every document is the v3.5 one: the contract fixtures as the contract ships them, and the staged documents and the supply fixture moved to v3.5 by contract/migrate_v34_to_v35.py. A migrated row carries no series, so its track shows flow not written by this writer. Now is byte-equal to build-3 and Board is byte-equal to build-1b. Both render the same text on the v3.5 documents.

What build-3 changes

The same build as build-2, on the same staged Solana bytes, with the pass 12 strings and the pass 12 cap rule (pass 12 Now, pass 12 Situation). Market cap leads the scale line: cap, then price, then change since seen. A cap is never estimated: a figure prints only when the rule "market cap at t" returns a supply read valid at t; every other basis prints cap not read, titled supply not read at the moment shown. The three labels print byte-equal to the site: Wallets in, No material changes detected since entry, No mentions in tracked Telegram sources. No layout changes. On the Solana document the list is still empty; what changes is the About and legend text, the sources line, and the Situation cap cell. Now on the supply fixture shows the cap form: SPRING carries one supply read, available from 17:00:00Z, so the cap prints from then on and cap not read before it (&t=16:57Z).

The two pages

The documents

One line per document: its contract version and sha256. Every one the pages read validates under contract v3.7 with no errors; the v3.2 document does not.

DocumentContractsha256
staged/solana-now.jsonv3.7 Now object (bare, no stamp), migrated from build-3's copyda00837b44bf965cd1973ecd3f1b1da47bb211ce6d4e26e45310e196e6311082
fixtures/now.jsonv3.7 (stamp companion-v3.7, moved from build-6's v3.5 copy and nothing else), fixturebab7002650e1fe6652c8c178bc82e85eb9008815f3da1c6dcd6a1af8a1aac97e
fixtures/now-v37.jsonv3.7, the contract fixture with KESTREL's 18-decimal supply read7610134bef278770d934a82fe6dbab5e8b55038d184db1120e0e142b199dd89b
fixtures/now-supply.jsonv3.7 (stamp moved), synthetic fixture88110b03ab517ec10c7fac3fe68840a0d09d2806dcf128c5e00d1171dc9fc919
fixtures/now-marlin.jsonv3.7 (stamp moved), synthetic fixture1fe614ac4b819e2111ddce70ef257b5dae1a0dc02a617a2bb63362c54bf2e81d
fixtures/now-notape.jsonv3.7 (stamp moved), synthetic fixture9e99b231de94cb72e3d8553ec76c25cef7d621d88d817ce22e5fd93a4d16cd63
fixtures/spring.jsonv3.7, fixture97ab32be52b4b9f6271e30850e939850ead8128607c327d7f8b2b6cab8c1ff03
fixtures/agrippa.jsonv3.7, fixturee8ad454b8275493d50c7391a5a4474371da1c571727f2b7116b815132487488b
fixtures/mossy.jsonv3.7, fixture3e4be2a20159115034fb349a7bb2577ae31ed00e3f709d98928f7bcbdf143c01
fixtures/board.jsonv3.7, fixturef1b94c211b3af5326b52850ee8aecf8ad936fa91102392bda969a84278da9f1f
staged/spring-now.jsonv3.7 Now object (bare, no stamp), migrated from build-3's copyad2f600448ead4fe792f656770d2f4aa43e9fdb0fcfef5686bb6d5542f543f50
real/bsc-now.jsonv3.7, real BSC document (螃蟹, one row), re-assembled by build-7 with its supply read admitted; http only2968bdddc92f2d989763980772e458b200b305003114c3a9031bcd88d393fc97
real/solana-now.jsonv3.7, real Solana document (STONK, one row), build-6's bytes; http only6e9cd3e184cfd6a5454741465cd8e6f261bae800f96bb91fcfdd7ea8673450e0
legacy/now-v32.jsonv3.2, refused724869db98156a1fc9c28ad4e59e66421f6faa3ffb6dddb05e96a8a4012217f7

How to switch

The Solana document

Pathdata/staged/solana-now.json, a copy of the tape writer's live file; the pages never read the live file
sha256 at copycd11bc321dd2a8d2d9cafc78b306ac3f5c96991e88242e52abd7b033c0321e8c; migrated to v3.5, da00837b44bf965cd1973ecd3f1b1da47bb211ce6d4e26e45310e196e6311082
asOf
history.since
Rows in the document
Rows visible at live
Refused, by reason

What is illustrative in the fixture

RowGradeIllustrative

Read from the rows' grade and illustrative flags when this page loads. The member's looks in the fixture are illustrative too. Your entry is the I'm in tap on the Situation page, kept in this browser.

What the staged SPRING run shows, and why it is empty

Checks and every difference from the frozen pages: CHECKS.md.