Interactive tools
Validator and confirmation comparator
Two tools. One checks a TAP on Dogecoin payload against the rules on the specification page. The other converts a confirmation count into elapsed time on both chains, because that is the difference people most often carry over unchanged.
- Rules from document v1.0.0
- Network Dogecoin mainnet
- Runs entirely in your browser
Both tools run in this page. Nothing you type is transmitted, stored, logged, or saved to your browser. This page makes no network request other than loading its own stylesheet, scripts, and search index. Reloading the page discards everything you entered.
TAP on Doge payload validator
Paste the exact JSON you intend to inscribe. The validator reports errors that make the payload invalid, cautions that usually mean a mistake, and notes about conditions it cannot check from the payload alone, such as whether a deployment still has supply.
This tool needs JavaScript. With scripts disabled you can still check a payload by hand against the operation rules and the test vectors. The two things worth checking first are that p is exactly tap, and that the operation name is prefixed: token-mint, not mint.
What it checks
- That the body is one JSON object, that
pis exactlytap, and thatopis one of the eleven operation names. - Bare DRC-20 and BRC-20 operation names under
p: "tap", naming the prefixed operation you meant. This is the failure that confirms on chain, costs a full fee, and is then read by nobody. - Required and unrecognised fields per operation, since a misspelled required field silently becomes a missing one.
- Amount format, ticker length against both the pre and post block 5,487,639 rules, and a declared decimal scale within 0 to 18.
- Every address, by base58check checksum and Dogecoin mainnet version byte, calling out Bitcoin addresses explicitly.
- Inscription id shape wherever a field references another inscription, since those fields take ids and not numbers.
- Payload byte length and the number of 520 byte chunks it needs.
What it cannot check
The validator sees one payload and nothing else. It cannot know whether a ticker is deployed, whether supply remains, whether an address holds the balance, whether a trade is still inside its valid window, or whether a signature verifies. Those depend on chain state at the moment the message is applied. A payload the validator accepts is well formed, not guaranteed to succeed.
Confirmation time comparator
A confirmation count is a unit of time, and the unit is different here. Dogecoin targets one minute per block; Bitcoin targets ten. Advice written for one chain buys a tenth or ten times the wait on the other.
This tool needs JavaScript. The arithmetic is simple enough to do without it: on Dogecoin, confirmations are roughly minutes. On Bitcoin, multiply by ten. To wait as long as n Bitcoin confirmations you need about 10n Dogecoin confirmations. The guide has a table of common values.
This tool converts block counts into elapsed time and nothing more. Dogecoin and Bitcoin are separate chains with separate hashrate and separate proof-of-work functions, so matching the minutes does not match the accumulated work. Dogecoin is merge-mined alongside Litecoin, so its security budget does not follow DOGE's price in a simple way. Choose a confirmation policy from the value at risk and from the reorg depths your indexer can survive. See reorg behaviour.