Configure the settlement exercise for any backend - #109
Merged
Merged
Conversation
Wire the one-suite-two-backends idea from the design note into the runner: --attach uses an already-running chain (never started or stopped by the run), --rpc points at it, --key-file reads three hex keys (never from argv), and --agreement overrides the agreement so a rehearsal can name its own burner addresses. Time-travel scenarios skip on an attached chain (wall-clock deadlines apply); the local chain remains the default and stays the only mode that starts anvil. The design note gains the four-step rehearsal recipe. Execution against a public testnet remains behind its separate authorization gate.
ClaudiuSchuster
force-pushed
the
oss-oo/settlement-backend-config
branch
from
September 18, 2026 12:36
17e9506 to
f9a4258
Compare
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
1 participant
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.
Wires the one suite, two backends design (
docs/settlement-local-chain.md) into the runner:--attach+--rpcuse an already-running chain (never started/stopped by the run),--key-filereads the three role keys (never from argv),--agreementlets a rehearsal name its own burner addresses. Time-travel scenarios skip when attached (wall-clock deadlines); local anvil stays the default. The design note gains the four-step rehearsal recipe. No public network is contacted by this change — executing against a testnet remains behind its separate authorization gate. Verified: 7/7 locally on the default backend;--rpcwithout--attachis refused.