Home

• Nothing read yet. Hit Refresh.

Pick one and it fills in the task for you. This comes straight off the chain — every stage set up in roughly the last day, whether or not it's listed anywhere.

Running the check reads the collection's price, opening time and per-wallet limit, then measures every wallet against it. Nothing is signed and nothing is sent at this step.

• No wallets yet. Make some, or paste keys below.

Drag a wallet into a box, or click it to move it along. One wallet paying many spreads money out; many paying one brings it back.

1. Replace the key you were given

   Whoever issued your licence key has seen it. The first time you sign in, Skully hands you a new one and asks you to save it. From that moment nobody but you can open your wallets — not the owner, not the machine this runs on.

   There is no reset. Your wallets are locked with that key and the server has no way to open them. Lose it and the wallets are gone with it. Put it somewhere you'd keep a password.

2. Make wallets, then export them

   Go to Wallets, choose how many, and press Make wallets. Then press Export to file straight away — before you send a single coin to them. The file lands on your own computer, not on the server.

   Use throwaway wallets and put in only what you mean to spend. Anyone who reads a key can empty the wallet it belongs to.

3. Put money in

   Paste your funded wallet's key into Bring your own on the Wallets page, then open Funds. Drag that wallet into Paying and the new ones into Receiving.

   Press Preview first. It builds the exact list and sends nothing. Read it, then press Send it.

Everything left of the line reads the chain and tells you things. Nothing you do there can spend a coin. Only holding the button commits you — and even then it waits.

1. Pick what to buy

   Feed lists everything opening on the chain in the next half day, and everything already running. Click one and it fills in the task for you.

   Or paste the address yourself on the Task page. Paste the address, never the collection name — a wrong address sends the money somewhere you can't get it back.

2. Say how many, and what you'll pay to win

   Buy per wallet is how many you get from one transaction. This is the number people get wrong: set it to what your balance can actually afford, not to a round number. If a collection sells out, there is no second chance.

   The work allowance follows the quantity on its own — you don't need to touch it. Whatever isn't used is refunded.

   Rush fee matters far less here than you'd expect. This chain takes transactions in the order they arrive, not in order of who paid most. Speed wins, money doesn't. Leave it low.

   A big quantity is all or nothing. Ask for 100 and only 60 are left, and the whole thing is refused — you get none, not 60. Spreading the same money over several wallets means a partial win instead of nothing.

3. Run the check

   This reads the collection's real price, opening time and limit, and measures every wallet against it. Nothing is signed and nothing is sent.

   Six lamps have to come up. A wallet that can't cover its share is dropped on its own and never blocks the others. If a lamp stays red, it says underneath exactly what's wrong.

4. Hold to get ready

   Press and hold. Every transaction is signed now and held back, and the line underneath repeats what you're about to buy — read it. If the quantity isn't what you meant, press Stand down and nothing goes out.

   At the opening second it fires by itself, from the machine in Ohio, straight to the chain's front door. You can close the tab, close your laptop, go and do something else.

5. Come back and look

   Sign in again whenever you like. Home shows what the last run did — how many wallets got in, how many you bought, and the transaction for each. That waits for you; it isn't lost by closing the tab.

6. Bring the money back

   Afterwards, open Funds, drag the spent wallets into Paying and your main one into Receiving. It sweeps whatever is left, minus each wallet's own fee. Preview first, as always.

1. What the server can and can't see

   Your wallets are locked in this browser with your licence key and stored sealed. The server holds bytes it has no way to read.

   One exception, said plainly: while you hold the arm button, the engine needs your keys for the seconds it takes to sign. They live in memory for that moment and are never written down. Everything else — reading, checking, waiting, sending — happens without them.

2. If something looks wrong

   Everything the panel says comes from the chain itself, so a strange number is usually a real one. Check the address on a block explorer before you doubt the panel.

   The History box keeps the running commentary, and every failure carries the reason the network gave rather than a shrug.

• Loading…

Everything goes out through all of them at once. Duplicates get turned away by the network, so there's no risk of buying twice.

A private connection is what decides most races. The public one is shared with everyone and gets crowded exactly when it counts. A free key from a node provider takes two minutes and is the single biggest thing you can change.

Wipe everything now. Clears the keys, the task and the readings from memory. Nothing was ever on disk, so this is the whole of it.