Your Runestone
| Component | vBytes | Cost (USD) |
|---|
Runes vs Ordinals — same byte count, different cost
If your Runestone payload were instead stored as taproot witness data (like an Ordinals inscription), it would get the SegWit discount. Same fee rate and BTC price.
| Storage method | Payload vBytes | Discount |
|---|
Why Runes get no witness discount
A Runestone is a set of varint-encoded integers (rune ID, amounts, output index, and for etchings: name, symbol, divisibility, premine, mint terms) pushed into an OP_RETURN output. OP_RETURN data lives in the transaction's regular scriptPubKey, not in the witness section — so it doesn't qualify for SegWit's witness discount. Every byte costs the full 4 weight units, i.e. exactly 1 vbyte per byte, versus the ~0.25 vbyte per byte that Ordinals inscriptions pay for witness-stored content.
This calculator adds standard transaction overhead — roughly 68 vbytes per taproot input and 43 vbytes per non-OP_RETURN output — plus the OP_RETURN output itself (payload bytes + ~11 bytes of opcode/pushdata/output framing), all multiplied by your fee rate.
Runes payloads are small, so the fee difference rarely matters in dollars
Because a Runestone is typically 20-100 bytes versus an inscription's kilobytes, the 4x per-byte cost disparity translates into a difference of a few cents to a few dollars at normal fee rates — not the difference between a $5 and $500 transaction. The exception is a fee-rate spike (Runes launched during exactly this kind of congestion in April 2024), where every vbyte, discounted or not, gets expensive fast. Check current network fees before minting.
Related: Ordinals inscription cost · Network fees · NFT profit calculator