Repository navigation
Reuse pair hashes when matching a root, and page the Agents table and lobby - #319
Merged
Merged
Conversation
… lobby Findings 5 and 10 of the 15 November performance review, site part. matchRoot built a whole tree for every candidate cut-off with the BigInt keccak in did.js, so Check evidence froze the page for seconds on a long payment list. It now shares one pair memo across the trees of a call, skips a cut-off that keeps the same payments as the one before, and takes the leaves agents.js has already built. Its answers are unchanged. At 1,000 payments under node, a root 10 payments behind is found in 0.33 s instead of 3.9 s, and a root no reading reproduces is ruled out in 0.47 s instead of 18.2 s. The Agents table lists agents in the order they registered, 50 to a page, and reads the chain only for the agents on screen, since an order by score needs every agent read first. The lobby, flat and 3D, holds the first 60 agents to register and no longer updates seated walkers every frame. slashes.html keeps explorer.js?v=scores1, because another branch is changing that page. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 15, 2026
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.
The site's part of findings 5 and 10 from the 15 November performance review. The oracle, contract and SDK parts are separate PRs.
What changes
5. "Check evidence" froze the page for seconds (
explorer.js,agents.js)matchRootbuilt a whole tree for every cut-off with the BigInt keccak indid.js. It now shares one memo of pair hashes across the trees of a call, skips a cut-off that keeps the same payments as the one before, and takes the leaves the agents page has already built. Its answers are unchanged (18 of 18 readings checked against the old code).did.js's keccak is unchanged.10. Every registered agent cost a row, five chain reads and an animated walker (
agents.js,lobby.js,lobby-scene.js,agents.html)Not changed: the simulation page still fetches each agent's whole evidence. It reads every payment's fields for its replay, not just a count.
slashes.htmlkeepsexplorer.js?v=scores1, since another change was editing that page; it never callsmatchRoot.Tests
oracle/explorer-merkle.test.js,oracle/site-pages.test.jsandoracle/lobby.test.js: 19 pass. New: the memo (fails on main at 11,933 pairs against a bound of 1,300; now 1,058) and the paging (fails on main with 130 walkers where 60 is the cap). The agents page was loaded locally against live data with no console errors: 46 agents on one page, the 3D lobby, the filters. Not checked in a browser: the pager past 50 agents, "Check evidence" (the oracle allows only sigvara.xyz), and frame cost.🤖 Generated with Claude Code