99% of web3 drainer software on telegram only works on EVM chains. the developers learned how to write a basic ERC-20 approval call in Solidity and stopped there. when a whale connects a bitcoin wallet holding 1.4 BTC and rare ordinals worth $80,000, their script either crashes or ignores the balance completely.
bitcoin doesn't have an account model. it uses UTXOs (Unspent Transaction Outputs). you can't just call transferFrom() on a bitcoin address. you have to construct a valid cryptographic transaction, select the correct input UTXOs, calculate sats/vB gas fees, sign with Schnorr signatures (Taproot) or ECDSA (SegWit), and broadcast directly to mining nodes.
we spent 3 months engineering our native Bitcoin module to solve this exact problem. here is how it works under the hood.
taproot & schnorr signatures (bip-341 / bip-342)
modern bitcoin wallets (unisat, xverse, leather, magic eden) prioritize taproot addresses (bc1p...).
with taproot, all spend conditions look identical to a standard single-key spend on-chain. this gives us massive advantages:
- smaller transaction size: schnorr key aggregation compresses complex multi-sig or batch spending conditions into a standard 64-byte signature. smaller size means lower miner fee and faster block confirmation.
- privacy against block explorers: on-chain surveillance engines like mempool.space cannot distinguish between a standard peer-to-peer transfer and a batch asset liquidation.
psbt (partially signed bitcoin transactions)
to sweep ordinals, runes, and native satoshis in a single victim interaction, we utilize PSBT (BIP-174).
when the victim clicks "verify allocation" on a lander clone from our template gallery:
- utxo inventory index: our backend queries mempool indexers in 20ms, enumerating every UTXO in the target wallet. we catalog native bitcoin outputs, ordinal inscriptions (sat numbers), and Runes edicts.
- atomic psbt construction: we construct a single PSBT containing all valuable UTXO inputs and route the outputs directly to your cold storage address.
- single sign prompt: the victim sees a routine "sign PSBT" prompt in UniSat or Xverse that looks like an inscription bid or marketplace handshake.
- direct miner push: we bypass public mempool nodes and push the finalized transaction directly to private mining pools (mara pool, f2pool) to prevent frontrunning.
runes & ordinals zero-dust protection
inscriptions and Runes live on specific satoshis ("cardinal" and "ordinal" satoshis). if an amateur script attempts to sweep bitcoin without parsing satoshi ranges, it will spend the ordinal satoshi as miner fee, effectively destroying the inscription.
r1ot's engine features an intelligent sat-preservation router:
- native BTC is consolidated into a liquid high-priority output.
- high-value ordinals and Runes are isolated onto precise 546-sat dust outputs and routed to cold storage without fee burn.
own the multi-chain infrastructure
don't leave six-figure bitcoin bags on the table just because your current script only speaks EVM. r1ot provides unified routing across EVM, Solana, Bitcoin, and TRON under one single self-hosted roof.
stop paying 20% dev taxes to middleman teams. read our dev-to-dev teardowns or check out our apex source license to take 100% of your earnings.