Repository navigation
Confirm a finalized root's payments in one Multicall3 read - #238
Merged
Merged
Conversation
sigvara_verify_evidence asked the reputation contract about each covered payment in a separate call, up to 100, eight at a time. Arc's public RPC refused the 29th within a second with "rate limit exceeded", and one refusal failed the whole check, so the tool failed on every agent with a long payment history. SigvaraVerifier.verifyEvidenceMany asks once, through Multicall3's aggregate3, and one at a time where Multicall3 has no code. The regression test runs the tool over 60 payments against a node that refuses past 20 calls a second, and fails on the old code. Against the live agent that failed 8 of 8 times, the check now confirms all 70 covered payments in about a second. Bumps the SDK to 1.0.0-alpha.18, not yet published. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
RunTimeAdmin
added a commit
that referenced
this pull request
Nov 8, 2026
Published 8 November 2026 with the one-read evidence check (#238). Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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 bug
sigvara_verify_evidenceasked the reputation contract'sverifyEvidenceabout each covered payment in a separate call, up to 100, eight at a time. Arc's public RPC limits calls a second. Measured on 7 November with every read logged: the 29th to 32nd calls within about a second came backrate limit exceeded(ethers reports it as "missing revert data"), and one refusal failed the whole check. So the tool failed 8 of 8 tries on the simulation's solo agent, on bothrpc.testnet.arc.ioandrpc.testnet.arc.network. It worked only on agents with few payments.The fix
SigvaraVerifier.verifyEvidenceMany(did, items)asks once, through Multicall3'saggregate3at its usual address, which Arc testnet has and the site already uses. Where Multicall3 has no code, it asks one at a time, in turn. Whether it has code is read once per verifier, and a failed read is asked again.Tests
test/evidence-confirm.test.ts. It runs the tool against a local node that refuses past 20eth_calls a second, over 60 payments, and checks all 60 are confirmed with no refusal and oneaggregate3. It also checks each answer is read from the batch (a wrong leaf comes back false), and the fallback without Multicall3. Both tests fail on the old code.test/mcp.test.tsstubsverifyEvidenceManyin place ofverifyEvidence, and the first test now expects one read for all twenty payments.Live check
The built branch against the live solo agent on 8 November, at about 00:12 UTC, three times across both public RPCs: each time it reproduced the finalized root over 70 payments, including the two Base payments, and the contract confirmed all 70, in about a second.
Also
1.0.0-alpha.18, with a changelog entry, not yet published.1.0.0-alpha.18to the three docs that sayalpha.17still fails. The SDK README says the confirmations are one read. The README and whitepaper SDK counts are updated in place.🤖 Generated with Claude Code