Robinhood Chain NFT Sniper
A lightweight NFT mint sniper built specifically for Robinhood Chain.
The bot is designed for public NFT mints that use SeaDrop and FCFS (first-come, first-served) sequencing.
It automatically:
- monitors the NFT mint window
- checks the live public drop configuration
- tests available RPCs
- selects a healthy/fast RPC
- prepares the mint transaction
- performs a final simulation
- signs the transaction locally
- broadcasts through multiple healthy RPCs
- waits for transaction confirmation
«No mint is guaranteed. FCFS mints are competitive and network conditions can affect transaction ordering.»
Requirements
- Android + Termux, or another Node.js environment
- Node.js 18+
- A Robinhood Chain wallet
- A small amount of ETH for gas
- Private key for the dedicated mint wallet
Recommended
Use a fresh wallet specifically for NFT minting.
Do not use your main wallet.
Termux Setup
- Install Termux
Install Termux on your Android device.
Then update packages:
pkg update && pkg upgrade
Install Git and Node.js:
pkg install git nodejs
Check Node.js:
node -v
- Clone the repository
git clone https://github.com/AzlanGPT/nft-sniper.git cd nft-sniper
Install dependencies:
npm install
Wallet Setup
Create a fresh wallet for minting.
Keep only the amount of ETH required for gas.
Never use your main wallet's private key with an experimental bot.
Environment Setup
Create your ".env" file:
cp .env.example .env
Open it:
nano .env
Add your private key:
PRIVATE_KEY=YOUR_PRIVATE_KEY
Save the file.
IMPORTANT
Never upload ".env" to GitHub.
The ".gitignore" file is configured to keep it private.
Never share your private key with anyone.
Robinhood Chain
Current network:
- Chain ID: "4663"
- Currency: ETH
RPCs used by the bot:
https://rpc.mainnet.chain.robinhood.com https://robinhood-rpc.publicnode.com
The bot checks RPC health and latency before the mint.
NFT Configuration
NFT-specific settings are configured through the .env file:
NFT_CONTRACT=0x... SEADROP_CONTRACT=0x... FEE_RECIPIENT=0x...
Use the same sniper for different Robinhood Chain NFT mints without changing the source code.
The current mint transaction is configured for:
- Public mint
- Quantity: "1"
- Mint price: "0 ETH"
Always verify the live collection configuration before using the bot.
Run the Sniper
Check the JavaScript syntax first:
node --check mint.mjs
If there is no output, the syntax check passed.
Start the bot:
npm start
Or:
node mint.mjs
The bot will wait for the public mint to become active.
You do not need to manually click the Mint button.
How It Works
Before the mint:
Start bot ↓ Check RPCs ↓ Select healthy RPC ↓ Read public mint configuration ↓ Wait for mint start
At mint time:
Mint becomes active ↓ Refresh RPC ranking ↓ Final drop check ↓ Get nonce / gas / balance ↓ Simulate mint ↓ Sign transaction locally ↓ Broadcast signed transaction ↓ Wait for confirmation
Why Multiple RPCs?
Robinhood Chain uses FCFS sequencing for transactions.
That means latency can matter.
The bot checks multiple RPC endpoints and can broadcast the same signed transaction through healthy RPCs.
This does not guarantee that your transaction will be first.
It simply gives the transaction multiple healthy routes to reach the network.
Security
Never:
- upload ".env"
- share your private key
- use your main wallet
- run random code without reviewing it
- keep large funds in the mint wallet
Recommended:
Use a dedicated wallet with only the ETH needed for gas.
Check the code yourself before using it with real funds.
Troubleshooting
"PRIVATE_KEY missing"
Make sure ".env" exists:
ls -la
And contains:
PRIVATE_KEY=...
"No healthy Robinhood RPC available"
The configured RPC endpoints may be temporarily unavailable.
Try again later or add another trusted Robinhood RPC.
"Mint is not active"
The public mint has not started yet, or the mint window has ended.
The bot will normally wait automatically before the start time.
"Simulation failed"
The live mint conditions may have changed.
Possible reasons include:
- mint ended
- wallet already minted
- supply exhausted
- contract configuration changed
- RPC returned stale data
Do not repeatedly submit transactions if the simulation fails.
Disclaimer
This software is provided for research and educational purposes.
NFT mints are competitive and transactions can fail or lose gas.
FCFS sequencing does not guarantee a successful mint.
Always verify the NFT contract, mint conditions, RPCs and transaction before using the bot.
DYOR.