This is not a call to a mint contract. The tool puts your data directly into calldata, sends a zero-value transaction to the same wallet and charges network gas. That is the whole transaction.
| Mode | Wallet used | Best for |
|---|---|---|
| Single wallet | The wallet connected in the top bar | A first small test, or repeats from one wallet |
| Multi-wallet batch | Wallets in the Bot Wallet vault | The same payload from several wallets; keys never leave this device |
- Pick the chain and modeChoose the chain up top. Single-wallet mode signs with the wallet you connect; batch mode uses wallets imported or generated in Bot Wallets. Put a password or passkey on the vault before you fund those wallets. Sending on the wrong chain puts the data somewhere the target protocol may never read it.
- Enter the payload the protocol expectsUse "Fill template" for plain text, the BSC-20 mint example or a JSON example, then replace its tick and fields with the real protocol values. You can also switch to Hex and paste complete calldata. Text is encoded as exact UTF-8: JSON is not compacted, keys are not reordered and no prefix is added. The payload limit is 64 KB. Hex must contain a whole number of bytes after you remove its spacing.
- Check the final calldataThe preview shows the byte count, final calldata, content hash, sending wallet, destination and estimated gas. Check the chain, wallet, tick, op, amount and the complete payload. Leave Gas Price and Gas Limit blank unless you know the transaction needs a manual setting; otherwise the tool estimates them.
- Single wallet: review, then signChoose "Review and Inscribe", then check the chain, wallet, byte count and full payload in the confirmation dialog. Choose "Sign and Send" and approve it in your wallet. If you run it more than once, the tool uses the next nonce for each transaction and waits for the receipts together.
- Batch: check the run settings, then startA batch starts with one run per wallet and wallets run in order. Each wallet can run 1 to 50 times, with a 0 to 3,600 second delay, and up to five wallets run at once. Keep the tab open while a batch is running. "Stop" takes effect after the current transaction; anything already broadcast can still confirm on-chain.
- Use the transaction hash as the receiptWhen Local Execution History says Confirmed, open the hash in a block explorer and read the receipt. The history belongs to this browser, so a new device or cleared storage has no copy. Whether the result is recognized as a valid inscription still depends on the protocol indexer.
Never do this · A confirmed transaction is not a valid inscription
A receipt only proves that the calldata is on-chain. The protocol indexer decides whether it accepts the ticker, counts this as a first inscription, and sets supply or balances. Start small, check the protocol rules and confirm the result in its indexer before scaling up.
Careful · Onchain data cannot be edited, and rerunning does not undo it
There is no edit or delete button after a transaction lands. A wrong chain, wrong wallet or missing character stays on-chain. Every repeat pays gas again; unless the protocol explicitly allows it, sending the same mint payload will not fix the previous inscription.
Tip · Leave the advanced settings alone at first
Automatic gas estimation is the right default for a first run. Only set Gas Price or Gas Limit when you know the transaction needs it. Likewise, get one wallet through before running a large batch with repeats and delays.