--
minted
--:--:--
IDLE
countdown to start
ARM, PUBLIC
SeaDrop mintPublic from one wallet, the burner. This spends.
Reads the public drop from chain and fires mintPublic from the burner.
For contracts that are not SeaDrop. Build the calldata with read-invite.js or howminted.js, then fire it here. Never retype hex.
Raw arming runs through the same executor as every other mode. It is driven from the terminal for now: node fire.js <chain> --to <addr> --hex <calldata> --value <eth> --at <ISO> --max <eth> --broadcast
A gated or FCFS phase, entered through OpenSea rather than built from chain.
| stage | type | price | cap |
|---|
The signature comes from OpenSea, is bound to this wallet, and works once,
which is why there is no attempts field: a second transaction carrying the
same payload reverts by construction.
Public phases are won by wallet count. Gated phases check the address, so extra wallets only collect extra rejections.
no wallets ticked
| use | label | address | balance |
|---|
no target staged
LOAD TARGET reads the collection and stages it here. A single eligible stage is
selected for you; with several, pick one under Signed. Wallets that are
ineligible, underfunded, over cap, or whose payload fails validation are skipped
and named. The rest still fire. Fund with disperse.js before arming.
Collections ranked by mints per minute, from Transfer events out of the zero address, so every standard shows up rather than SeaDrop only.
| collection | per min | wallets | price | left | gone in | state |
|---|
Many wallets on one collection is demand. One wallet with a high count is usually
farming, and the wallets column separates them. Robinhood runs about ten blocks a
second, so a wide window is a very large scan. Start at ten minutes and widen only
if it completes quickly. Click a row to load it into Public.
Add an address to the watchlist. Nothing is armed by adding one: this only decides whose mints you get to see.
Labels are short and alphanumeric. A wallet you rate highly can carry more weight
than the others when copy mint decides whether a collection is worth following,
which is set per wallet in copymint.js.
What the wallets you follow have been minting in the last hour. Read only.
Firing on what a watched wallet mints is a SPENDING path and is not wired to this
page. copymint.js can do it from the terminal and has never fired on chain, so it
is driven deliberately for now:
node copymint.js watch <chain> --max-price <eth> --budget <eth> --fire
It refuses to fire without both a max price and a budget.
Every wallet currently on the watchlist, with its label and weight.
TARGET
Target detail appears here once loaded.
--
left
--
supply
--
price eth
--
your cap
--
gas gwei
LIVE TARGETS
Open and upcoming SeaDrop phases found in the last few days of logs.
| collection | price | left |
|---|
A failed read is UNKNOWN, never zero. The bot will not arm on an unknown.
Nothing on this page signs. Arming, signing and broadcast all happen on the host.
Nothing on this page signs. Arming, signing and broadcast all happen on the host.