Start: what Chisel proves
This is the colleague-facing bridge between the older signing conversation, the 2020 crypto-linguistic white paper, and the current Chisel implementation. It now starts with the practical reason Chisel is vanilla JavaScript: elliptic gives the browser enough secp256k1 machinery to sign locally without turning the main app into a Node stack dependency tour.
Core builds, signs, serializes, decodes, and explains meaningful UTXO transactions. The main app remains plain browser JavaScript. elliptic is part of the core signing path. Portal displays and filters transaction artifacts. Data is a static or local snapshot. fileProxy, bunOven, keeperBun, scanners, label tools, and importers are satellites.
Start with why local browser signing matters, then open Portal, load a local or bundled transaction fixture, inspect ordered outputs, read MacDougall address lines, inspect OP_RETURN if present, treat amount codes as optional binders, then verify the raw JSON. Do not start with every historical experiment.
A click-through route for colleagues: Portal reader, Etch fixture, raw transaction, local signature, RPC export, then Tools. It avoids live broadcast and uses the bundled dummy fixture.
- Start: explain local browser signing and static graph reading.
- Portal: confirm bundled/static data is visible.
- Etch: load a dry-run fixture.
- Etch: create unsigned raw hex from VIN/VOUT JSON.
- Etch: sign locally with the dummy WIF.
- Etch: export normal RPC command text.
- Tools: show scanners, labels, legacy decoder, and satellites.
Demo mode idle.
Runs fixture and packaging checks inside the same browser environment used for the demo. This is not a live broadcast test.
Self-test idle.
Etch transaction workbench
Paste one private key in WIF format, optionally add OP_RETURN data, and broadcast a self-send consolidation transaction. Your private key is only used locally in this session and never sent to the remote API.
Manual transaction pipeline
Use this when you want to stop between createrawtransaction, signrawtransaction, and sendrawtransaction. You can copy any box out, paste edited JSON or hex back in, then continue from that step. Sending a signed raw transaction does not require the WIF.
Advanced / derived values
Review transaction pipeline
These are the raw objects Chisel uses internally. Keep this mode as the engineering microscope: account, UTXOs, VIN, VOUT, unsigned hex, signed hex, and broadcast result.
No transactions loaded.
Local data / fileProxy
Address / rabbit-trail lookup
Build address helper
Decoded links and drill-down targets
Decoded lines
Chisel semantic records
Index raw
Selected raw transaction JSON
Tools
The support tools stay separate. The main page should control transactions, not become a drawer full of knives.