Skip to content

deploy: refuse what a node would not take, and keep keys off the command line #14

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

Merged
mjthatch merged 1 commit into from
Oct 23, 2026
Merged

deploy: refuse what a node would not take, and keep keys off the command line #14

Show file tree
Hide file tree
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 @@ -95,7 +95,7 @@ Each test generates programs for one layer, runs them through `hand` (which exec
elements-cli -stdin sendrawtransaction < spend.hex
```

`deploy spend` prunes the program against this transaction and executes it, so a wrong witness fails before anything is sent. You don't need a node for a Liquid testnet -- the faucet funds the address and the transaction can be broadcast through Blockstream's Esplora API (the `liquidtestnet` network in `deploy`).
`deploy spend` prunes the program against this transaction and executes it, so a wrong witness fails before anything is sent; it also refuses a spend that a node would not take (above the consensus cap on the Bit Machine's cells, a budget that does not cover the cost, above the standard weight). You don't need a node for a Liquid testnet -- the faucet funds the address and the transaction can be broadcast through Blockstream's Esplora API (the `liquidtestnet` network in `deploy`).

## Your circuit

Expand Down
Loading
Loading