Chisel

Broadcast mode builds, signs, decodes, and sends the transaction. Review mode shows the raw transaction pipeline after a build/send attempt.

One-step Ravencoin send-back + broadcast

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.

Opens qrScan.html. The scanner derives its currency list from installed Chisel coin extensions, then assembles four 16-hex QR stickers or accepts a complete WIF.
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.
Idle
Ravencoin uses the RPC/API server directly for UTXOs, create, decode, and send.
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.

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

      

Decode ledger objects

Open the decoder when the txid is the durable object key and the outputs need to be read as OP_RETURN plus MacDougall indexed addresses.

Portal explorer

Cross-chain transaction stream. Local filesystem records are loaded first, then live index lookups can add new transactions as they are discovered. The table is the main object: one row per transaction, newest first, with decoded data hints and verification exits.

Transaction stream

No transactions loaded.

show
Local transactions will load here when fileProxy is running.
Sources and write options

Config is read from chisel.portal.config.json. Saved transactions are pretty jq-style JSON under data/transactions/<coin>/ and EVM split feeds under data/transactions/evm/<chainid>/<contract>/.

Local transaction list is merged into the main stream.
Merged stream list is rendered in the main stream.
Address / rabbit-trail lookup
verify address

Build address helper

Decoded links and drill-down targets
Decoded lines
Address / chord lines

        
MacDougal-readable pass

        
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.