This project reverse-engineers chat.bankofai.io's authentication and API key generation, automating mass account creation and credit claiming. It pools hundreds of API keys behind an OpenAI-compatible proxy, enabling unified access to various AI models. This is targeted at engineers and researchers interested in AI platform security and automated resource acquisition.

How It Works

The system automates a six-step registration pipeline: generating an EVM wallet, funding it with minimal Base L2 ETH ("dust") for an on-chain check, signing SIWE-like messages for login, and then signing a distinct, AES-encrypted message (using a hardcoded key) to claim free credits. Finally, an API key is generated. Rotating proxies are employed to circumvent IP-based rate limiting on credit claims.

Quick Start & Requirements

• Installation: Clone the repo (git clone https://github.com/BuluBulugege/bankofai-pool_new.git), cd bankofai-pool_new, npm install.
• Prerequisites: Node.js 18+, an EVM wallet funded with ETH on Base L2, and a rotating proxy service (Kookeey recommended).
• Running: Use node auto_sign_claim.js for single/batch registration or npm run dev for the production dashboard.
• Configuration: Requires setting up an .env file with credentials for the Base L2 funder wallet and proxy provider.

Highlighted Details

• AES Key: 1wT1r7z8bZxDHVmZKAs6VFYSXOxmyh0lLByiw5TmF0= (hardcoded in frontend JavaScript).
• Base L2 Dusting: Satisfies an on-chain activity check with a minimal ETH transfer (10M wei).
• Proxy Rotation: Crucial for bypassing the "1 claim per IP" rate limit imposed by the target service.
• Relay Mode: A cost-efficient strategy generating keys at ~$0.017 each by reusing seed wallet funds across multiple accounts.
• Production Throughput: Batch mode achieves ~30-50 keys/min; Relay mode supports ~100-300 keys/batch.

Maintenance & Community

Discussions and updates primarily occur on LinuxDo, a Chinese-speaking tech community. No specific details on core maintainers, sponsorships, or a formal roadmap are provided within the README.

Licensing & Compatibility

The project is released under the MIT license. It is intended strictly for security research and educational purposes, requiring compliance with applicable laws and the terms of service of the target platform.

Limitations & Caveats

This project relies on reverse-engineered client-side logic and hardcoded secrets, making it vulnerable to platform updates or patches. Its primary purpose is to demonstrate vulnerabilities in authentication and anti-bot mechanisms, and its use should strictly adhere to ethical guidelines and legal frameworks.