Akiro Mint

1. Install, sign in and fund your minting wallets

Guide for launcher 1.5.22. Button and field names below follow the English interface. This is EVM minting software; choose the network used by the collection.

• Access. Get an active Akiro plan, generate your Akiro Key in your site Profile, download the launcher through the site and sign in. The Akiro Key unlocks the launcher; it is different from an OpenSea API key and from a wallet private key.
• Wallets. Add a dedicated minting wallet on Wallets and give it a recognisable name. Use the same address that earned the allowlist spot. Fund every selected wallet with the mint price plus native gas on the correct chain; a free mint still needs gas.
• Before the drop. Check that the launcher is online and authenticated, that components have loaded, and that no update or login is outstanding. Keep the computer awake and connected until the task finishes. Locking the screen is fine; sleep pauses execution.

2. Find your way around: Basic and Pro

• Mode switch. Basic and Pro are the switch at the top of the launcher. They control which settings are shown, not a different subscription or a faster mint engine. Start in Basic; use Pro when you need the extra controls.
• Pages. Dashboard is the overview. Mint Settings is where tasks A/B/C are configured and run. Wallets manages minting wallets. Drop Intel reads OpenSea collection/stage information. Broadcast manages delivery endpoints. Settings contains global network, RPC and OpenSea API settings.
• Pro pages. Calldata, Gas and Proxies appear in the navigation in Pro. Pro also exposes additional controls inside Settings and Mint Settings. If a field is missing, check the mode first. On a narrow window the navigation icons can disappear while the page names remain.
• Help. Use Explain this beside a field for the in-app reference. Never change an unfamiliar advanced setting just to remove a warning; read the warning and fix its cause.

3. Choose the chain and configure RPC

An RPC endpoint is the node URL the app uses to read the chain and submit transactions. It must support the collection’s network.

• Settings → Network. In Basic select Chain; in Pro verify Chain ID. Set Primary HTTP RPC to a working HTTPS endpoint for that chain. Phase reads, balances and gas quotes verify the RPC chain before using its data. If RPC network mismatch appears, correct the primary RPC or the per-wallet override; changing the chain selector does not repair a custom URL for another network. Adding a Broadcast endpoint does not replace the primary RPC.
• Provider. Use a provider or the official network RPC that actually supports your chain. Free-plan limits vary; an individual API URL does not guarantee isolated capacity. Treat API-bearing RPC URLs as secrets.
• Broadcast. Add the endpoints you want to use on Broadcast, check their chain and enable only appropriate entries. An unfamiliar hostname is labelled network-unverified; a configured endpoint is not proof of connectivity. The engine verifies the actual chain before sending. Multiple delivery routes can improve resilience, but do not guarantee acceptance or inclusion. Separate provider URLs can still share an account-wide quota.
• Per-task override. In Pro, Broadcast endpoints for task A/B/C (comma-separated) overrides that task’s RPC list. Check the Broadcast summary for the selected task. Do not copy Ethereum builder endpoints to a different chain.
• Websocket RPC. Optional WS RPC is for supported mempool observation; it is not required for a basic scheduled mint. Unsupported chain/mempool combinations do not become supported by adding a WS URL.

4. Choose the right mint path

• Public SeaDrop mint. For an OpenSea collection with an unrestricted public SeaDrop stage, use SeaDrop collection (OpenSea public mint) in Mint Target. Leave OpenSea Mode disabled. The app can generate public calldata locally and prepare the transaction before the opening.
• Closed OpenSea stage. For GTD, allowlist or FCFS stages requiring an OpenSea signature, use OpenSea Mode. FCFS means first come, first served among eligible wallets; it may still be allowlisted. A beta role, raffle entry or access to a game is not necessarily a mint spot.
• Other contracts. For a mint that is not supported by the SeaDrop generator or OpenSea Mode, use the contract’s correct transaction target, calldata and native value. There is no universal mint calldata. Ask for help if you cannot verify the transaction you are configuring.

5. OpenSea GTD / FCFS / allowlist: complete setup

OpenSea returns the mint transaction for the currently active stage. The bot cannot manufacture eligibility or reuse another wallet’s signature.

• API key. In Settings → OpenSea, add your own OpenSea API key. It is needed for Drop Intel and the REST path for signed stages. Keep it private and follow the quota shown by OpenSea for your account. An Akiro Key is not a substitute.
• Inspect the collection. In Drop Intel paste the collection slug or full OpenSea collection link, then Check collection. Read the Phases table: network, stage type, price, per-wallet limit and opening time. Recheck before the mint because organisers may change the schedule.
• Configure the task. In Mint Settings select task A/B/C and its wallets. Enable OpenSea mode, fill Collection with the correct slug/link and set Quantity within the stage limit. Check the global chain and Primary HTTP RPC against the collection. The OpenSea Chain field is for the SIWE fallback; with an API key the slug determines the API collection chain, but it does not fix a wrong global RPC.
• Set the correct stage time. Press Fetch drop info, find the exact GTD/FCFS stage you intend to mint and use Set as T0. This sets the start time; it does not reserve a spot or force the API to serve that stage. Verify Mint start (UTC) afterwards.
• Check the exact wallet. Use Check whitelist in Mint Settings, or Wallet → Check this wallet in Drop Intel. Mint Settings checks the first selected wallet named in the result, not every selected wallet. The request broadcasts nothing and only checks the active stage at that moment. Changing collection, chain, wallet, quantity, T0 or task invalidates the result; late responses from the old form are ignored. A positive result does not guarantee eligibility for a future GTD/FCFS stage. Before your stage opens, an eligible wallet may still receive a rejection.
• Do not exhaust the API quota. Whitelist checks use the same mint-request quota needed at T0. Avoid repeated probes, especially across many wallets. The UI limits repeated manual checks. HTTP 429 applies a shared cooldown to requests with the same key within the component; changing tasks does not clear it. Respect Retry-After and stop probing during the cooldown.
• What happens at T0. The task waits, asks OpenSea for target/calldata/value at the opening, then performs the remaining checks and submission. This adds API latency. Unlike the direct public path, closed-stage transactions are not fully signed in advance.
• Price and readiness. OpenSea Mode shows from OpenSea at T0: a stale preset/public price is not the signed-stage price. The API response supplies the actual value; zero means a free mint, with gas still payable. Until then the funding estimate covers known gas only. Before you arm lists configured wallets/RPC/collection/T0; its checks do not guarantee RPC health or WL eligibility.
• If OpenSea refuses. Before obtaining a transaction, the bot makes at most three mint-data requests within a total five-second HTTP budget. Transient network/5xx failures may be retried; recognised stage/eligibility 422 rejections are retried only near T0, within its first two seconds. Sold-out, wallet-limit, invalid input and API access failures stop the attempt. A 429 respects Retry-After and ends the task if the cooldown cannot fit the budget. There is no automatic switch to public. Retries on failure is a separate transaction recovery setting. A 422 alone does not prove that a promised WL never existed; preserve the diagnostic and verify the exact wallet, stage and time.

6. Public SeaDrop and manual calldata

• Collection versus transaction target. In Mint Target select SeaDrop collection (OpenSea public mint), enter Collection contract address and Qty, then Generate calldata. The NFT collection address is a parameter; the actual transaction goes to SeaDrop. Do not replace its target with the NFT address just because they differ.
• Read the public stage. Open Public Phase info and refresh the contract data on the selected network. A future public stage can be read before it opens; PUBLIC NOT CONFIGURED means no public settings were returned on the verified network, not merely that T0 has not arrived. Check price, opening, ending, supply and wallet limit. Detection of an allowlist or signer does not prove that a particular wallet is eligible.
• Price and amount. Verify Mint Price/value and quantity before arming. The total native value must match the intended call, and a free stage normally has zero mint value plus gas. Gas is separate from the NFT price. Regenerate/review calldata after changing the collection, method or quantity.
• Advanced manual calls. Pro exposes Contract address (msg.to), Raw calldata (hex) and Calldata file (optional); Calldata offers the builder. Apply to Mint Session updates Task A and opens Mint Settings; it preserves that task’s other settings. Review Task A before arming. Proof/signature inputs are specific to the contract and wallet. Do not paste a transaction or signed-stage proof from an unrelated wallet.

7. Time and arming

• Mint start (UTC). Enter the actual stage opening in UTC. Mint start (unix ms, UTC) represents the same instant in milliseconds. Local datetime helper uses the computer’s local timezone; check the resulting UTC value rather than assuming local and UTC times match.
• Immediate start. A missing or past T0 can cause an immediate run when you Arm. Check the warning and confirmation summary. Do not arm an immediate task as a substitute for a dry run.
• Offset (ms, signed). Moves the effective firing time relative to the selected start. Negative fires earlier and may hit a closed stage. Leave it unchanged unless you have a measured reason. NTP correction compensates clock drift, not marketplace eligibility or a wrong timezone.
• Pre-sign offset (ms before T0). Controls preparation timing for the direct transaction path. It does not make OpenSea issue a closed-stage signature before the stage opens.
• Arm & Run. Configure ahead of time, select the correct wallets, press Arm & Run in the pinned bottom bar and read the confirmation summary. The displayed phase depends on the path: OpenSea can show a waiting-stage state rather than Armed — spinning to T0.
• While armed. Keep network access, authentication and native funds available. The local launcher session expires separately from the paid plan: the app returns to Login and stops an armed task when that session expires. Re-enter the Akiro Key and review the task before arming again. Local session checks run on focus and at short intervals without extra marketplace requests. Avoid sending other transactions from the selected wallets: changing the nonce can invalidate prepared work. Do not rely on a last-second recovery.

8. Gas, quantity and Burst

• Max fee (gwei). The maximum per-gas fee you permit, not the NFT price. Too low can prevent inclusion; a high cap also raises the balance needed during checks. Actual fees depend on the chain and inclusion conditions, so do not copy another network’s values blindly.
• Max priority fee (gwei). The priority component for networks using EIP-1559. Keep it compatible with Max fee and network rules. Gas presets read the selected network; Robinhood presets do not add an Ethereum priority-tip floor. The Gas page identifies the chain and native currency: ETH on Ethereum/Robinhood, USDC on Arc. Gas presets are estimates, not a first-block guarantee.
• Gas limit. Maximum execution gas units. Too low can revert after spending gas; too high can require more balance. Normally allow estimation. If Skip gas estimate is enabled, provide a valid Gas limit or preflight will fail.
• Quantity versus Burst count. Quantity is NFTs per transaction. Burst count is the number of transaction attempts in the initial burst, not the number of wallets. Both must respect the remaining per-wallet allowance. Start with Burst count 1; extra transactions on a one-per-wallet mint can revert and cost gas.
• Priority bump per step (%). Increases the priority for burst steps. More aggressive settings can increase costs; inspect the resulting fees and wallet balance. It does not grant additional mint allowance.
• Free mint. Every selected wallet still needs native gas on the mint chain. A token balance on another chain or an ERC-20 balance is not native gas.

9. Pro controls: use only when needed

• Saved configs. Save/load reusable task settings, then review the loaded task, wallet selection, network, collection, gas and T0. A saved configuration can contain an obsolete stage or old time.
• Dry run. Runs preparation/preflight without the final transaction broadcast. It does not reserve NFTs or prove that a closed stage will be available later. OpenSea mode can still request mint data and consume API quota.
• Preflight eth_call. Simulates the call before submission when enabled. A not-yet-open stage can reject a simulation. Disabling simulation does not make an invalid transaction valid.
• Skip checks. Skip gas estimate requires Gas limit. Skip balance check and Skip chain-id verify remove protections; leave them off for a normal setup. Do not use them to suppress an unexplained error.
• Retries on failure / Insurance window (ms from T0). Bound recovery after the transaction execution/broadcast path. Zero retries disables further attempts; the insurance window limits recovery time. Terminal reasons such as sold out or wallet limit stop recovery. These settings do not retry OpenSea 422/429 before a transaction is obtained.
• Wait for receipt / Confirmations / Timeout (sec). Control confirmation tracking. An RPC returning a transaction hash means acceptance, not a successful mint. No receipt or an exhausted wait does not prove success; inspect the explorer before another attempt.
• Queue ladder. Rung offsets (ms from T0) controls the ladder timing. This is an advanced execution strategy, not the ordinary one-wallet setup. Review offsets, nonce behaviour, gas exposure and wallet limits before use.
• Volley Mode (farm). Uses an AkiroVolley Orchestrator and minions for contract-based batching. Inner target, Inner calldata, Minions, Value per minion (wei), Min succeeded and Gas per minion must agree with a separately prepared deployment and the drop’s contract rules. Do not enable it for a normal wallet task; do not assume contract minions qualify for a wallet-bound signed stage.
• Turbo-relay / Anti-MEV (Flashbots). Optional specialised delivery paths, not prerequisites for minting. Use only a supported chain and configured service. Flashbots Exclusive mode restricts delivery routes; it does not apply universally to EVM chains. A custom URL must be a trusted, compatible endpoint.
• Mempool log every N pending tx. Requires a compatible WS RPC and chain support. Zero disables observation. This diagnostic setting is not required to schedule a mint.

10. Proxies and multiple tasks

• Proxies. Switch to Pro to open Proxies. Add a named Proxy URL and assign it to the intended wallet/profile. A URL may contain credentials: do not share it in screenshots or tickets. Test connectivity before relying on it.
• Limits. A proxy does not grant whitelist eligibility, fix a wrong chain or increase an API key’s quota. Proxy support is path-dependent: the API-key REST mint-data path currently creates its client without a proxy. Do not assume a wallet proxy routes every OpenSea request.
• Tasks A/B/C. Each slot has its own run settings and wallet selection. Avoid using the same wallet concurrently in multiple tasks: the nonce and per-wallet mint allowance are still shared on-chain. Task isolation does not isolate a provider account’s quota.

11. Read the result; Stop and Kill

• Per-Wallet Status. Read the outcome for each wallet, not just the task total. A mixed outcome across wallets is possible. When a hash is available, verify the chain explorer, receipt status and NFT transfer before treating the mint as successful.
• Failed before broadcast. Chain-check, configuration or OpenSea API failures can end an attempt without sending a transaction. A later Kill does not mean Kill caused the earlier failure. Preserve the first error.
• Failed after broadcast. Receipt status 0 means the transaction reverted. Missing receipt means success is not confirmed; a submitted transaction may still be pending. A hash by itself is not evidence of a minted NFT.
• Stop. The pinned bottom bar stops the selected task cooperatively and retains its result for diagnosis. A cancellation before broadcast can be shown as Failed with an aborted-by-user reason and no transaction hash; that is not an on-chain revert. Other slots remain independent. A task may need time to leave its current operation.
• Kill task. Tears down/clears the selected task and resets its visible state. It cannot undo a transaction already broadcast to the blockchain. A new run can be blocked until the previous worker has actually exited. Export the log before clearing the screen.

12. Open logs and send a useful support report

• Live Logs. Open Mint Settings, switch to Pro and scroll to the Live Logs card at the bottom. Press Show to expand it; use Export to save the current log to a file. Hide only collapses the display.
• Persistent file. Settings → Logging configures LOG DIRECTORY, LOG FILE NAME and RUST_LOG FILTER. This card is not the live viewer. On Windows the default file is under %APPDATA%\com.akiro.launcher\bot-config\logs\mint-bot.log; use the configured path if you changed it.
• What to send. Send the exported log and the incident time/timezone, launcher version, collection link/contract, network, public wallet address, intended stage, quantity and a screenshot of the task configuration with secrets covered. Include a transaction hash when one exists.
• Configuration and attempt diagnostics. Version 1.5.21 records a safe allowlist snapshot of the effective task configuration after defaults/overrides, a unique diagnostic attempt ID, slot, component versions/image hashes, T0 and API attempt timings. Calldata is represented by selector, length and SHA256; endpoints by host and an opaque ID. Private keys, seed phrases, API/Akiro keys, tokens, signatures, cookies, credentials and raw transactions are excluded. Unknown stage/time-source metadata stays unknown. Keep the incident time and original settings available; do not send full global.json, session credentials or wallet exports.

13. Troubleshooting

• OpenSea 422: wallet not eligible. Check the exact wallet, collection slug and active stage. Before a future stage starts, a rejection can be expected even for a listed wallet. Version 1.5.21 briefly retries recognised stage rejections near T0 within the documented request budget, then reports failure if no mint data is obtained. Investigate with the project/OpenSea when needed; do not automatically conclude that the user never had a WL.
• OpenSea 429. API quota/rate limit. Stop repeated checks and follow the response cooldown. More wallets or whitelist probes can consume the same quota as the mint itself.
• RPC/chain/balance errors. Check Primary HTTP RPC and chain ID, endpoint availability and native balance on that exact chain. Funding a different chain will not help. Do not disable the check until you understand the mismatch.
• PREFLIGHT_SKIP_GAS_EST=true requires GAS_LIMIT. Disable Skip gas estimate or provide an appropriate Gas limit. This is a configuration failure before sending, not proof of a congested RPC.
• ETH price fetch failed; gas-only snapshot. The USD price service could not be reached. This warning affects the USD cost display; by itself it is not evidence that the mint transaction failed. Find the wallet’s actual terminal error.
• Session revoked / offline TTL. Restore the launcher’s connection, check your plan and sign in again as needed. A prolonged network outage or explicit access revocation can stop a mint before sending. Keeping the PC asleep will not maintain execution.
• Sold out / wallet limit / signature used. These are terminal contract restrictions, not a reason to increase Burst or keep retrying. Check existing pending/successful transactions before starting another run.

14. Final checklist before a live mint

• Verify. Correct chain and primary RPC; correct collection and transaction target; exact eligible wallet; intended stage and current UTC opening; quantity within allowance; native funds for price and gas.
• Review. Correct task A/B/C; OpenSea Mode only when required; API key/quota available for closed stages; Burst and advanced flags reviewed; dry-run state intentional; no simultaneous spending from the same wallet.
• Stay ready. Arm early enough to handle preparation errors, keep the computer awake, follow per-wallet status and preserve logs. No software can guarantee a mint, a first block or an NFT on a sold-out stage.