setyamickala/fastmint-fcfs-agentic

What it does

fastmint-fcfs is an agent skill, not a standalone app. It teaches agents such as Claude Code, Codex, Cursor, or any tool that reads SKILL.md to send one mint, claim, or buy transaction the moment a sale opens on BNB Smart Chain. Signing goes through Binance Agentic Wallet using the baw CLI, so no private key sits on the machine; the agent only prepares calldata and picks the timing.

The speed comes from running three triggers in parallel after the sale opens: an NTP-corrected clock at T+0, the first block whose timestamp reaches the start time, and a successful eth_call from the wallet. The first preview that returns simulationCode 000000000 is executed exactly once, and other in-flight previews are dropped. That is why the README reports roughly T+1.3–1.5s to broadcast and T+2.1–2.2s to inclusion, versus 5–6s for the earlier sequential design see the timing diagram and measured numbers.

Quick start

Prerequisites: Node.js ≥ 20 (ethers 6.13 is bundled, no npm install), the Binance Agentic Wallet CLI installed globally, and the Binance App with Agentic Wallet and Developer Mode enabled, with the wallet balance under the Developer Mode cap installation notes.

1. Put the fastmint-fcfs folder where your agent reads skills from, for example mkdir -p .claude/skills && cp -r fastmint-fcfs .claude/skills/, then make the launcher executable.
2. Sign in once: baw auth signin --json, open the returned urlForWeb, match the pairing code in the app, then run baw auth verify --qrCodeId <qrCodeId> --json and confirm baw wallet status --json reports CONNECTED.
3. Run cd fastmint-fcfs && ./fastmint.sh bench to rank RPCs, check clock offset, wallet status, Developer Mode, BNB balance, and Agent ID. This step is read-only.
4. Run ./fastmint.sh recon <mint-url> to extract the contract, ABI, opening time, supply, price, and candidate calls, then rehearse with ./fastmint.sh fire --to 0xSALE --data 0x... --start 23:00 --dry and inspect the decoded call = ... line.
5. Fire in the background with ./fastmint.sh fire --to 0xSALE --data 0x... --start 23:00 --label project_free, then run ./fastmint.sh logs to read the TIMELINE line, transaction hash, explorer link, and decoded revert if it stopped.

The full workflow, including paid mints and dynamic arguments, is in the usage flow and command reference.

Constraints and safety rules

This only supports BSC. The chain ID, RPC pool, Agent ID registry, and explorer are hardcoded to Binance Smart Chain FAQ. Paid mints require an explicit --value plus a --maxValue cap from the user; a call with value above the cap, or a value greater than zero without a cap, is rejected. The same call is refused after execute because a lock file is written first, so retrying after an error or revert is not part of the design. A wallet that is not connected requires the user to sign in again, and the skill must not run baw auth signin by itself. A Binance risk block, a RISK flag, or an allowance change in the preview is meant to stop the run rather than be bypassed safety rails.

Expect session expiry after two idle days, possible Binance-side simulation failures before the opening block (error 351805), and ISP DNS hijacking of binance.com in some networks, for which the README recommends encrypted DNS or a VPN troubleshooting. No license is declared.

HotRepo's take

The project appeared on the new-project board on 11 Nov 2026, when it was recorded with 107 stars and 7 forks inside its first observed growth window. That is early, single-snapshot evidence, not a trend. More relevant is the engineering angle: it replaces a serial preview-then-execute pipeline with racing clock, block-head, and eth_call triggers, and the tradeoff is explicit — the two-step baw flow cannot simulate before the sale opens, so speed has to come from when the preview is fired, not from skipping the simulation. Whether the reported 2-second figure generalizes depends on RPC latency and Binance node state, which the README itself marks with a ±0.4s caveat.