Skip to content

docs: clarify Quantum forge script support boundary #9

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
williamclay8 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

docs: clarify Quantum forge script support boundary #9

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ Key Quantum extensions on top of upstream Foundry:
- `--quantum` and the `--quantum.*` flags route CREATE through the shared Quantum adapter with the same explicit sender / key-id / seed / cosigner contract as `cast send`.

- In `forge script`:
- Scripted broadcast routes through the shared Quantum adapter for supported write shapes and fails closed on unsupported Quantum script shapes with a stable rejection message.
- `--quantum` intentionally fails closed in v1: scripted Quantum broadcasts are not yet wired through the native `0x7A` adapter. Split scripted write flows into individual `cast send --quantum` / `forge create --quantum` invocations, or rerun without `--quantum` against an Ethereum-compatible network.

- Additionally:
- A shared `QuantumWriteRequestV1` write contract with fail-closed v1 validation: `nonce_key` must be `0`, multi-call bundles are rejected, and lifecycle-selector misuse is caught before signing.
Expand Down