Drop your 0x
Robinhood → Receive → Ethereum → copy. Paste it to the bot once — validated and checksummed on the spot.
Register your wallet and 𝕏 handle once. When a challenge drops, post your tweets, submit the links, and $BVAULT leaves the vault straight to your wallet — caught on-chain and announced with the exact amount. Receipted on Blockscout, every time.
The order matters — every payout walks this exact path, and the chain gets the last word.
Robinhood → Receive → Ethereum → copy. Paste it to the bot once — validated and checksummed on the spot.
Your handle is locked to your Telegram with a unique index. Sybil doubles get bounced at the database, not by vibes.
An admin fires it from the panel. Every registered wallet gets the brief, the reward, and how many tweets it takes.
Links go in one by one — 1/3… 2/3… 3/3. Every tweet is claimed per challenge; recycle someone else's and you're bounced, with the link named.
Proofs hit the admin queue next to your @handle. Approve fires the ERC-20 transfer from the vault — pending → paying → paid, exactly once.
The watcher catches the transfer leaving the vault, dedupes by tx hash, and pings you the exact amount + Blockscout link.
unique index on the handle — sybils bounce
per-challenge link dedupe, transactional
mid-review swaps redirect nothing
The green dot is your reward. Watch where it goes.
Every 15 seconds the bot scans Transfer logs from the vault address on Robinhood Chain. Bot-sent or paid by hand — the moment $BVAULT moves to a registered wallet, the transfer is caught, deduped by tx hash, matched to the holder, and announced with the exact amount.
No payout goes unreceipted. No payout gets announced twice. The chain is the source of truth, and the bot just reads it out loud.
Transfer(from = VAULT) → match wallet → announce amountThe vault key lives on the server. The instant an admin taps Approve & pay, the bot fires the ERC-20 transfer, waits for confirmation, and DMs you the amount with the Blockscout link.
Sends are serialized through one nonce queue — no collisions, no stuck transactions, and a double-tapped Approve can't double-pay.
Approve marks the submission and tells the admin exactly what to send where. The payment happens by hand, from cold storage if you like.
The watcher does the rest — it spots the manual transfer leaving the vault, links it to your approved submission, and announces the amount like nothing was different.
pending → paying → paid / failed with atomic status transitions. Two admins racing the same Approve button? One payout, exactly once.
One wallet. One 𝕏. Real challenges. On-chain receipts.
Open the bot on Telegram ↗