Akiro LabsAboutGet AccessTips
VIEW ON OPENSEA

Akiro Mint

A mint bot for EVM drops. It syncs to network time, signs your transactions before the drop opens and fires every wallet in the same millisecond across several nodes at once — so you land in the block you aimed for, not the one after.

SOON View plans

Mint bot testing is still in progress. Access to the launcher opens during the beta test period.
Subscription required. The launcher refuses to start without an Akiro Key tied to an active plan — see Terms.

Hits the second you aim for

Your computer's clock is usually a second or two off, and a mint is decided in milliseconds. Akiro Mint syncs to network time, builds and signs your transaction before the drop opens, and then does nothing but wait. At the exact moment it only has to send bytes that are already prepared.

Every wallet fires at once

Put ten wallets in and all ten send in the same millisecond — not one after another. Each wallet gets its own thread, its own signature and its own connection, so a slow or broken wallet never holds up the rest.

Up to three independent tasks

One mint can be worked by three separate tasks at the same time, each with its own wallets, its own proxies and its own RPC endpoints. That keeps a group of wallets from eating the bandwidth of the one wallet you care about most.

A second attempt when it makes sense

If a transaction reverts or never lands, the bot asks the chain why with a single call and tries again with a fresh signature — but only when the reason is temporary. Sold out, wallet limit reached, signature already used: it stops and tells you, instead of burning gas.

Full guide

Written for someone who has never used software like this. Nothing to compile, no developer tools to install — Akiro Mint is a normal desktop app that fetches and decrypts its own components. If you follow this page top to bottom you will be ready for your first drop in about twenty minutes, most of which is waiting for free accounts to be created.

What you need before you start

  • An active plan and an Akiro Key. The launcher will not start without them — see plans.
  • Wallets you are willing to risk. Never the wallet holding your collection. Make fresh ones for minting and keep only mint money on them.
  • Gas on every wallet. A wallet with no gas is simply skipped — the bot checks before the drop and tells you which ones are short.
  • At least one RPC endpoint — free, five minutes to set up. Explained below.
  • Proxies — optional. Most people running a handful of wallets do not need them. Explained below, including when you do.

RPC endpoints: what they are and where to get them

Your computer cannot talk to a blockchain directly. It talks to a node — a server that holds the chain and passes your transaction on. The address of that server is called an RPC endpoint, and it looks like an ordinary web link.

Every chain has free public endpoints, and they work fine on a quiet day. During a hyped drop thousands of people hammer the same public node at the same second, it starts refusing requests, and your transaction waits in line while somebody else's gets in. That is the single most common reason a mint bot "did nothing".

The fix is your own endpoint, which nobody else is using. The free tier of any of these is far more than a mint needs:

  • Alchemy — the one we use ourselves. Sign up, press Create new app, pick your chain, open the app and copy the HTTPS link. That link is your endpoint. Treat it as a password: anyone who has it can spend your quota.
  • QuickNode and Ankr — same idea, same free tiers. Useful as a second source: two endpoints from two different companies will not fail together.

Add several. Akiro Mint sends your transaction to every endpoint you list at the same time, and whichever accepts first wins. Extra endpoints cannot slow you down — they only cover the case where one of them chokes.

Give each task its own endpoint. Five wallets sending through one endpoint at the same millisecond compete with each other for that provider's quota. Create two or three separate apps in Alchemy — it costs nothing — and assign one to each task.

Proxies: what they are, and when you actually need one

A proxy is a middleman server. Traffic goes through it, so the service on the other end sees the proxy's address instead of yours. Assign a different proxy to each wallet and each wallet looks like a different person on a different connection.

Whether you need them depends entirely on what you are minting:

  • A plain public mint, your own RPC — you do not need proxies. A blockchain node does not care how many wallets come from one address. This covers most drops.
  • Drops that go through a marketplace — proxies help. When the bot has to ask OpenSea for a signed transaction (allowlist, GTD and FCFS stages), that is a normal web request to a company that counts requests per address. Ten wallets from one address in one second looks like exactly what it is, and the requests start getting refused.
  • Many wallets on a shared public endpoint — proxies help. Same reason: per-address rate limits.

If you do need them, buy residential proxies from any reputable seller — datacenter ranges are the first thing such services block. You will be given lines in the form http://user:pass@host:port; paste them into the Proxies page and assign them to wallets. The bot spreads them round-robin if you list fewer proxies than wallets.

Step by step

  1. Get your Akiro Key. With an active plan, open Profile on this site and generate it. It is shown once — copy it immediately. Lost it? Generate a new one; the old key dies the moment you do.
  2. Install and sign in. Download the launcher, run it, paste the key once. It pulls its components itself and shows Ready. Leave it running: while it is open it keeps your session alive, and a launcher that sat closed for hours will ask you to sign in again — you do not want to discover that ten minutes before a drop.
  3. Add your wallets. On the Wallets page, paste the private key of each minting wallet. Keys are sealed by your operating system the moment they are saved and never leave your machine. Give each wallet a name you will recognise under pressure.
  4. Add your RPC endpoints on the Broadcast page, as described above.
  5. Point the bot at the drop. If the collection sells through OpenSea, turn on OpenSea Mode and pick the drop — the launcher builds the call itself and handles allowlist signatures. Otherwise fill in the contract address, the calldata and the value by hand. Check the contract address twice: it is the one mistake nothing downstream can catch.
  6. Set the start time. Take it from the drop itself, not from a tweet — organisers move schedules and rarely announce it. The launcher corrects for your computer's clock drift on its own, so enter the real opening time and leave the rest alone.
  7. Set gas. Give yourself room: a max fee several times the current network rate costs you nothing extra if the network stays calm — unused gas is refunded — but a fee set too low means your transaction sits while the collection sells out. Note that a wallet must hold gas limit × max fee in advance, even though it will spend far less.
  8. Check the per-wallet limit. Many drops allow one NFT per wallet. When that is the case, set Burst to 1 — a second transaction from the same wallet is guaranteed to fail and burn gas for nothing. Burst above 1 only makes sense when the drop lets one wallet mint several.
  9. Split into tasks if you have many wallets. A workable layout: task A gets your best one or two wallets on the fastest endpoints, tasks B and C get the rest, each on its own private endpoint. Tasks are fully independent — stopping one does not touch the others.
  10. Arm it, well before the start. Press Arm & Run and confirm the summary. The task goes to Armed — spinning to T0 and waits. Arm at least fifteen minutes ahead: arming runs the checks, reads fees, signs and warms up connections, and if something is wrong you want time to fix it, not two minutes.
  11. Do not touch those wallets afterwards. The transaction is signed in advance and tied to the wallet's current position in its own queue. Send anything else from that wallet and the prepared transaction becomes invalid. The bot re-checks a few seconds before the start and will re-sign if it can, but do not rely on it.

Reading the result

The log tells you exactly what happened, per wallet and per task. The line that matters most is fired at T0 +0 ms — that is the bot hitting the opening moment. After it you will see how many of your endpoints accepted the transaction, and then whether it made it into a block.

A revert is not always a failure of the bot. Sold out means someone was faster. Wallet limit reached means that wallet already has its NFT. Not active means the stage had not opened yet — the bot treats that one as temporary and tries again by itself. Every wallet is judged on its own: one failing has no effect on the others, and a run where two of five wallets succeed is a normal outcome, not a bug.

The mistakes people actually make

  • Not enough gas on a wallet. The most common one by far. Check balances the day before, not the hour of.
  • Using the wallet meanwhile. Buying something on a marketplace with a wallet that is armed for a mint will invalidate its prepared transaction.
  • Trusting an announced time. Schedules move. Re-check the drop shortly before it opens.
  • Burst above 1 on a one-per-wallet drop. Pure gas donation.
  • Arming at the last minute. Leaves no room to react to anything.
  • One endpoint for everything. Works right up until the moment it matters.

Safety

This software signs transactions with your private keys. Keys are sealed by your operating system on your own machine and are never sent to us — but the wallet you load is the wallet at risk, so use ones made for minting and funded with what you intend to spend.

Nobody from Akiro will ever ask for a private key or for your Akiro Key. Not in Discord, not in a support ticket, not in a direct message. Anyone who does is not us.

The launcher is available to active subscribers, and a field-by-field reference for every setting ships inside the app. Stuck on something this page did not cover? Ask in the community — a real person will answer.