Bnkr Wheel

Second buyback done. basescan.org/tx/0xd4e88b39a…

Buyback completed on bankrwheel Transactions executed successfully, and tokens are being repurchased as we speak. basescan.org/tx/0x650ec790a…

BnkrWheel is live on Base 📺 CA: 0xE3b227598dDdC616fB3282aE9c52089b0a38DbA3 The automated buyback engine is running. Fees are being claimed. Tokens are being bought back. Every interval. No stops This is not a promise on a roadmap. This is a contract deployed and executing right now Built on Base. Powered by Bankr. Automated by The Kraken The wheel is spinning

Why Base Because automated buybacks need two things: low gas and fast confirmation Every cycle BnkrWheel runs costs gas. If you're on a chain where a swap costs $8 in fees your buyback strategy bleeds money before it even starts On Base the cost per execution is fractions of a cent. That means the bot can run tight intervals without eating into the value it's supposed to be creating Fast finality means every buyback settles quickly. No waiting. No stuck transactions clogging the loop BnkrWheel was built on Base from day one. Not ported. Not adapted. Native

Meet The Kraken That's the algorithm inside BnkrWheel that handles every buyback execution It watches the WETH balance accumulating from Bankr protocol fees. The moment your configured threshold is hit it moves. No delay. No approval needed It routes every purchase through Bankr's audited swap infrastructure on Base. Low fees. Fast finality. Clean execution Over 1,200 buybacks completed and counting The Kraken doesn't sleep. It doesn't take weekends off. It doesn't forget It just buys

Tokenomics don't fail because of bad design They fail because of bad execution A team promises buybacks. The first month looks great. Then someone gets distracted. Then the market dips. Then nobody remembers the last time a buyback actually happened BnkrWheel was built to solve exactly that One protocol. One loop. Fees get claimed. Tokens get bought. Every interval. No exceptions We didn't build this to impress anyone. We built it because execution should never depend on someone remembering to do it

The stack behind BnkrWheel is intentionally simple Frontend: Vite serving static HTML. A config UI that generates your runtime command. No wallet connections. No key inputs. No browser storage Backend: Node.js 18+ running locally on your machine. The Bankr CLI authenticates and executes every swap through Base's network The separation matters The web layer builds parameters. Your terminal runs them. Your environment holds the keys. Nothing sensitive ever crosses into the browser Built on Base for low fees and fast finality. Integrated with Bankr for audited swap execution Simple stack. Clean trust boundary. That's the architecture

BnkrWheel doesn't reinvent the wheel. It plugs into what already works Bankr CLI handles authentication, signing, and swap routing on Base. BnkrWheel sits on top as the automation layer that decides when to pull the trigger WETH fee claiming goes through Bankr's audited contracts. Token purchases route through Bankr's existing swap infrastructure One integration. Two functions. Zero custom smart contracts needed on your side You bring the token address. Bankr brings the execution layer. BnkrWheel connects both and runs forever

Most buyback promises die in a group chat Someone forgets. Someone gets busy. The market moves and nobody executes BnkrWheel removes the human from the equation entirely Set a threshold. Set an interval. The bot handles the rest The result: consistent accumulation, reduced sell pressure, and a floor that builds itself over time No announcements needed. The chart does the talking

Every token has sellers Not every token has something buying back 24 hours a day 7 days a week BnkrWheel turns protocol fees into constant buy pressure on Base. Automatic. Nonstop. No one has to press a button While you sleep the bot is claiming WETH and converting it back into your token That's not marketing. That's math working in your favor every single interval

BnkrWheel technical breakdown: Operations and Security Production workflow for running this properly Start with conservative thresholds and moderate intervals. Run in observation mode first to verify timing. Monitor logs for failed swaps, slippage events, or RPC instability. Tune only after watching several execution cycles Security model: No private key input anywhere in the UI No browser persistence of signing secrets All signing happens through local wallet tooling or Bankr CLI Credentials stored in environment variables, never in frontend fields Keep Node and Bankr CLI updated. Pin your runtime environment for reproducibility. Document your strategy presets per token and per market condition The frontend is a config layer. Your terminal is the execution layer. Your local env is the trust boundary Nothing crosses that line

BnkrWheel technical breakdown: Parameter Tuning Four parameters control everything Token Address: Verified contract on Base. Wrong chain or unverified address means failed swaps or wasted gas Interval: How often the bot checks and evaluates. Short intervals increase responsiveness but stack gas overhead. Start moderate and tune after observing several execution windows Minimum WETH: The threshold before a buyback triggers. Set too low and you get fragmented micro swaps. Set too high and you miss accumulation windows. Find the balance for your fee volume Network: Base only for now. Your RPC config and runtime tooling must be aligned to the same chain The command updates dynamically as you change values in the UI node index.js --token 0x... --interval 5 --min 0.01 --network base Run it. Monitor logs. Adjust. Repeat

BnkrWheel technical breakdown: Stack and Architecture The project runs on two layers Frontend: Static HTML + CSS + JS built with Vite. No framework. The UI is a configuration interface that generates your runtime command. It never touches your keys Runtime: Node.js 18+ executing locally. The generated command passes your parameters to the Bankr CLI which handles authentication, signing, and swap execution on Base The frontend does not execute transactions. It does not store secrets. It does not persist anything in the browser Your keys live in your local environment variables. The web layer only builds the command string. Execution stays on your terminal That separation is the entire security model

BnkrWheel technical breakdown: The Execution Loop The core runs a four step cycle on repeat 1. Reads protocol fee state and claimable WETH amount from Bankr 2. Evaluates available balance against your configured minimum threshold 3. If threshold is met, executes a buy action through the configured route on Base 4. Waits for the next interval and starts again No cron jobs. No external triggers. One process running locally on your machine polling the protocol state and executing when conditions are right The interval is configurable down to the minute. Default is 5 That's the entire engine

The problem with manual buybacks Somebody has to remember Somebody has to execute Somebody has to care at 3am on a Sunday BnkrWheel removes all three problems It runs locally on your machine Your keys never leave your environment Every swap goes through Bankr's audited contracts on Base Over 1,200 buybacks executed so far This is what sustainable tokenomics looks like when you automate the hard part

How BnkrWheel works in 30 seconds 1. Fees accumulate as WETH inside the Bankr protocol 2. The bot claims those fees automatically at set intervals 3. When WETH hits your threshold it executes a buyback 4. Repeat forever The algorithm behind it is called The Kraken It runs 24/7 on Base with no manual intervention You configure it once and walk away

Most projects talk about buybacks Then forget about them two weeks later BnkrWheel doesn't forget It's an automated buyback engine on Base that claims protocol fees and converts them into constant buying pressure No human in the loop No missed windows No excuses Just a bot doing its job every 5 minutes