Commit, reveal, broadcast
Send pipeline & status
What actually happens after you sign a DRC-20 send: commit, reveal, index, then the automatic move.
"Send DRC-20 Coins" is really three transactions and an indexing step, orchestrated so it feels like one button press. This page walks through what happens after a user approves a send, and what's actually confirmed working versus still being hardened.
Single-recipient send
Both plain DOGE sends and single-recipient DRC-20 sends are confirmed working end-to-end in production.
- The wallet asks Doge Soft's inscriber for a DRC-20 transfer inscription. The inscriber first checks that the sender's indexed balance covers the amount, and refuses otherwise.
- The inscriber writes the commit and reveal transactions. The reveal puts the transfer inscription on an output owned by the sender's own address. This is the step that inscribes the transfer on Dogecoin L1.
- The wallet waits until that output is visible, checks it carries the expected tick and amount, then builds and signs the move transaction on the device, which sends the inscription to the recipient.
- The move is broadcast, and once it confirms the indexer credits the recipient. If the app closes mid-send, the wallet picks the send back up and finishes it.
Status: confirmed working. Plain DOGE send (dust, fee, change and max-balance edge cases included) and single-recipient DRC-20 send (fully automatic commit → reveal → move) are both live in production.
Who signs what
The inscriber signs only the commit and reveal it creates. The move that hands the coins to the recipient is always signed on the sender's device. Any server that helps get it onto the network only relays an already-signed transaction and never holds the sender's key.
Batch send (many recipients at once)
Splitting one DRC-20 balance across many recipients in a single flow is a separate, three-phase process, currently available inside the wallet app only (not exposed on the injected provider — see Sending DOGE & DRC-20 Coins):
- Split — one commit + reveal inscription is built per recipient, up front.
- Gate — the wallet polls the indexer until every carrier is indexed and its tick, amount and owner all check out.
- Move — a single combined move transaction spends every carrier plus the shared fee UTXOs at once, with the same recovery as single sends.
Status: implemented, not independently verified under load. The batch flow is structurally complete and mirrors the proven single-send pipeline, but it doesn't yet have the same track record in production as single-recipient sends. Treat it as beta — verify results, don't rely on it for anything time-sensitive yet.
Current, ecosystem-wide picture of what's proven versus still cooking: see Ecosystem status.