Chisel

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.

Read origin bridge Starts with vanilla JS, elliptic, local signing, QR stickers, mundane transaction UX, then maps the white paper kernel to Portal, MacDougall, ASC, and the current refactor boundary. Printable HTML Letter-friendly review copy with a print button and explicit page-break behavior. Refactor phases Low-risk sequence for cleaning up Chisel before touching signing, fees, UTXO selection, or broadcast code. What Chisel proves Short colleague-facing claim: local signing, ordered outputs, explorer/node resources, static graph, and satellite tools. Architecture Core driver, Etch workbench, Review microscope, Portal reader, and satellites. Demo script Portal first, Start second, Etch third, Review fourth, Tools last.

Current boundary

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.

First demo path

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.

Guided demo mode

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.

Browser self-test

Runs fixture and packaging checks inside the same browser environment used for the demo. This is not a live broadcast test.

Self-test idle.

Send crypto

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.

Currency Sender WIF

Saves the derived public address as the username and this WIF as the password when your browser supports direct credential storage.

Derived public address

Show the public address for another phone to scan, or search it as its own Portal ledger stream.

Load a key to watch this address.

QR scanners

Both use the same camera tool. SCAN KEY assembles four private-key fragments. SCAN ARTIFACT accepts one public 16-hex sticker and returns a chain-specific unspendable index output ready for Send.

Fee (RVN) OP_RETURN ASCII

Build an image from ordered Digibyte outputs, or open the general payload satellite for URLs, IPFS CIDs, local file hashes, and artifact plans.

OP_RETURN HEX IPFS field Extra recipients

Optional fixed outputs. Unspendable rows are intentional burn/index outputs, not normal recipients. Change still returns to the sender after recipients and fee are subtracted.

Recipient total (RVN) Recipients + fee (RVN) RPC / API URL

Idle

Ravencoin uses the RPC/API server directly for UTXOs, create, decode, and send.

Advanced send 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.

WIF handling: Chisel uses the WIF only inside the current browser session. Manual draft save/restore intentionally does not store WIF values. Fixture WIFs are public dummy keys and must not be funded.

I understand SEND SIGNED RAW will broadcast a transaction to the selected chain/provider. Leave this unchecked while building, signing, copying, or testing fixtures.

Optional UTXO JSON

VIN JSON

VOUT JSON

Unsigned raw transaction hex

Signed raw transaction hex

RPC command export

Scratch JSON / notes

Advanced / derived values

UTXO count Spend total (RVN) Send-back amount (RVN)

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.

1. Account

2. UTXOs

3. VIN

4. VOUT

5. Build payload

6. Unsigned raw transaction

7. Decoded unsigned transaction

8. Signed raw transaction

9. Decoded signed transaction

10. Send payload

11. Broadcast result

Open a Chisel page

You do not have to log in just to read. The fifth sticker is the public shorthand for a page. Scan that one sticker to resolve its ledger index and open whatever is already attached to it. Scan the four private stickers on the back only when you want Chisel to recognize you as the owner and let you add records.

Scan one page sticker Public path. Scan sticker 5, derive its Litecoin index address, and open the page if it already exists. This is the normal Alaskan K9 Blessing-style entry path and does not load a private key. Open as the owner Control path. Scan the four private fragments from the back of the booklet. Chisel derives the identity, returns here to Portal, and keeps Send as the transaction-writing tool rather than the login screen.

No transaction selected

verify tx in explorer

Base57 image render controls

Color map

Scale

Skip front

Skip back

Direct txid

Your loaded Chisel address

Personal account

LTC

Public address only. Private key material is not stored in Portal.

VERIFY ADDRESS

Transaction stream

◷ Loading ThunderWords…

DGB RVN LTC BTC DOGE Gomez Jethro Other

◷ Loading ThunderWords…

☰ File portal / storage

Storage is a Portal concern, not part of signing. rigler.org/fileproxy can cache ledger data now and can later host signed off-ledger records associated with a Chisel page.

fileProxy URL

Gomez Jethro

Local transaction list is merged into the main stream.

Merged stream list is rendered in the main stream.

Address / rabbit-trail lookup

Currency / explorer profile

Address, contract, or Chisel index marker

verify address

Build address helper

Spendable address

Trail note

Marker

Phrase

Decoded links and drill-down targets

No transaction selected.

Decoded lines

Address / chord lines

MacDougall-readable pass

Chisel semantic records

Index raw

Selected raw transaction JSON

Examples

Runnable artifacts and reference outputs. These are examples of Chisel's portable-tool approach, not extra transaction modes.

M64 artifact workbench Stage controlled JavaScript through canonicalization, token bytes, M64 transport, hydration, and an isolated browser test. Dark Star raster example Run the compact deterministic raster engine that reconstructs the larger Dark Star image from a small program and parameters. M64 hydrator Load an M64 artifact, hydrate it back into its controlled source form, and execute the declared entry point. Polygon artifact carrier Publish and retrieve exact artifact bytes through Polygon transaction calldata with an injected EVM wallet.

Tools

The support tools stay separate. The main page should control transactions, not become a drawer full of knives.

Key capture / custody

Broadcast key capture Tablet/phone scanner for four left-to-right colored key stickers, scanned-key library, multi-chain addresses, red private-key QR, InstaPrint PNG handoff, and return to Chisel. Legacy QR / WIF scanner Older linear scanner: assemble four 16-hex stickers or a full WIF, verify one selected chain, then load it back into Chisel. Key InstaPrint tool Create and download the black-and-white long PNG receipt for a WIF/private key and public address.

General tools

M64 artifact workbench Canonicalize, crush, encode, hydrate, and test compact controlled-JavaScript artifacts, including the Dark Star example. MacDougall resolver Resolve and inspect MacDougall-style encoded references with the standalone browser tool. 2×2 label builder Build printable CertLedger / RVN labels with SHA-256 Base64 and txid QR fields. Display portal Render base58-color image chords from tx JSON, pasted JSON, or Digibyte explorer data. Browser self-test Run fixture, draft, send-lock, Portal boot, and static-data checks before a demo. Demo mode notes Click-through route for showing Chisel without starting with the old Decode page or a live broadcast. Legacy transaction decoder Old single-transaction inspector. Portal is the normal reader; use this when debugging txid-named fixtures or raw output decoding. qrField label tool Generate printable QR-coded field identifiers and physical entry-point labels.