Repository navigation
Zift batch 5: unpublished value_pools_daily (node pool balances, NSM) - #228
Merged
Merged
Conversation
Daily node-reported value-pool balances (transparent, Sprout, Sapling, Orchard, Ironwood, lockbox), the NSM balance and chain supply at the highest observed canonical block of each completed UTC date, from the indexer's insert-only getblockchaininfo observations (from 2026-09-28). Store and mainnet migrations with rollbacks, a separate reader grant applied only after the worker that lists the view, admission readiness, catalogue entry (published:false), guidance, example, eval case, tests and runbook. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an unpublished research dataset,
value_pools_daily. Each completed UTC date gets one row: the node's owngetblockchaininfovalue pools at the highest observed canonical block of that date. Runbook:server/deploy/ask-analytics/value-pools.md(rollback first). Nothing is applied to any host by this PR.Columns:
date, height, hash, observed_blocks, day_blocks, transparent, sprout, sapling, orchard, ironwood, lockbox, nsm, chain_supply(zatoshi stocks).Source: the indexer's insert-only
node_accounting_observations(from 2026-09-28, ~1,150 rows/day). It is replicated with reviewed columns only;subsidy(funding-stream addresses),upgrades,sourceandpoll_interval_msstay private.Findings that shaped it (read-only, mainnet, 2026-11-02)
circulating_supply_zatequals the sum of all pools including the lockbox, and matchessupply_daily.chain_supplyat all 35 day-end blocks. It is published aschain_supply, so it can't be confused withsupply_daily.circulating_supply, which excludes the lockbox.(height, hash)to canonicalblocks, so they never appear.observed_blocksandday_blocksexpose this.daily:daily(indexer-maintained shielded balances) differs slightly from the node's figures. The guidance says which to use and to name the source.Privacy: these are chain-wide totals, one row per date, so they can't link shielded activity.
turnstile_dailyand the other excluded tables stay unpublished.Lessons from batch 4 applied
value-pools-grant-v1.sql), applied only after the worker that lists the view. The test asserts thatvalue-pools-v1.sqlnever touchesask_public_reader.reader_view_driftcheck.Tests
ask-research-value-pools.test.js.ask-logical-sync.test.js.value_pools_end_2026_10stays pending until publish.🤖 Generated with Claude Code