how does the zero cut actually work?

we killed the rev-share scam. you pay for the license, you get the software or the raw uncompiled repo, you host it on your own server. we don't have backdoors into your wallets, we don't see your victim logs, and we don't take 20% of your hits. you keep 100% because it's your traffic and your risk.

how do you bypass blockaid and blowfish in 2026?

we don't fire raw approve() or legacy solana transfer instructions. everything on evm is wrapped in off-chain permit2 eip-712 messages that look like standard uniswap sign-ins to simulation engines. on solana, we use versioned transactions (v0) with lookup tables. victim signs one clean prompt, and the wallet gets swept in 400ms before security extensions can react.

how do you keep domains alive and avoid red screens?

built-in pre-flight tds. when a visitor hits your domain, our script inspects canvas hashes, ip subnets, and user-agents in 15ms. google bots, twitter ad reviewers, and datacenter scanners get redirected to a harmless crypto news blog. real targets get the live payload. that's how our domains stay green for weeks instead of getting burned in 10 minutes.

can i sweep wallets again if they deposit more funds later?

yeah. on evm, permit2 signatures can grant persistent allowances. once the victim signs, the allowance stays open on-chain. if they drop another $50k usdt in their wallet next month, your terminal flags it and you trigger a secondary sweep remotely. they don't even have to come back to your site.

can i inject this into my own custom landers?

easy. inside the dashboard you generate a lightweight 2-line js snippet. drop it into any existing web3 site or use our library of 300+ pixel-perfect clones (airdrop claims, meme launchpads, dex swaps).

what happens when chains or wallets push security updates?

we push over-the-air updates immediately. we trade and route hundreds of thousands daily on our own infrastructure, so the second phantom or metamask tweaks their simulation heuristics, our engine is patched within the hour. you get the update pushed straight to your panel.

how should i cash out without getting burned?

never send extracted funds directly to binance or coinbase unless you want a subpoena. bridge cross-chain via thorchain or mayan, swap 100% into monero (xmr), hold it cold on tails os for 72 hours, then off-ramp through non-kyc p2p desks. full guide is included in the terminal.

02. Core Multi-Chain Modules

7 min•Updated March 2026

Bitcoin Taproot & PSBT Sweeper

Native Bitcoin UTXO accounting, BIP-174 Partially Signed Bitcoin Transactions (PSBT), Ordinals dust protection, and Runes.

Bitcoin Taproot & PSBT Sweeper

Most drainers ignore Bitcoin because UTXO accounting requires stateful transaction assembly that cannot be solved with generic EVM smart contracts. When high-net-worth targets connect UniSat, Xverse, or OKX Web3 wallets, other scripts fail completely.

R1OT includes a dedicated native Bitcoin sweeper supporting Taproot (BIP-341/342), Ordinals, and Runes. Explore our technical dispatch on Bitcoin Taproot & Ordinals Sweeper Mechanics for full state transition diagrams.

BIP-174 Partially Signed Bitcoin Transactions (PSBT)

Our engine catalogs all UTXOs in the target wallet in under 20ms and generates an atomic PSBT:

Combines native Bitcoin UTXOs and rare inscription satoshis into a single transaction input array.
Aggregates Schnorr signatures across inputs to reduce virtual byte (vB) weight.
Displays a standard "Sign PSBT" prompt that mirrors ordinary Magic Eden or UniSat marketplace trades.

Ordinals & Runes Zero-Dust Protection

Amateur scripts frequently spend ordinal satoshis as miner fees, destroying rare inscriptions. R1OT employs an automated sat-preservation router:

Input UTXOs:
├── UTXO 1: 0.85 BTC (Native Liquidity)
└── UTXO 2: Rare Inscription (1,000 sats, sat #20938472)

R1OT PSBT Output Assembly:
├── Output 1: 0.849 BTC ──► Your Cold Storage (Consolidated Liquidity)
├── Output 2: 546 sats  ──► Inscription Cold Storage (Protected Ordinal Output)
└── Output 3: 454 sats  ──► Miner Priority Fee (Direct Private Mining Pool Push)

Direct Mining Pool Push

Finalized transactions bypass public mempool nodes (mempool.space) and are dispatched directly to private mining pools (F2Pool, MARA Pool). This guarantees that Runes or Ordinals cannot be frontrun by mempool snipers.

Related Modules & Architecture Dispatches

Bitcoin Taproot & Ordinals Sweeper Mechanics — Bitcoin PSBT deep dive.
Hardened Offshore VPS & Docker — Hosting setup for Bitcoin node relays.
Monero (XMR) Cleansing Protocol — Cleansing native BTC proceeds.
Solana V0 & Address Lookup Tables — High-speed non-EVM execution.

Need custom RPC routing or lander integration?

direct verified developer assistance available on telegram

@r1ot_support

Bitcoin Taproot & PSBT Sweeper

BIP-174 Partially Signed Bitcoin Transactions (PSBT)

Our engine catalogs all UTXOs in the target wallet in under 20ms and generates an atomic PSBT:

Combines native Bitcoin UTXOs and rare inscription satoshis into a single transaction input array.

Aggregates Schnorr signatures across inputs to reduce virtual byte (vB) weight.

Displays a standard "Sign PSBT" prompt that mirrors ordinary Magic Eden or UniSat marketplace trades.

Ordinals & Runes Zero-Dust Protection

Amateur scripts frequently spend ordinal satoshis as miner fees, destroying rare inscriptions. R1OT employs an automated sat-preservation router:

Input UTXOs: ├── UTXO 1: 0.85 BTC (Native Liquidity) └── UTXO 2: Rare Inscription (1,000 sats, sat #20938472) R1OT PSBT Output Assembly: ├── Output 1: 0.849 BTC ──► Your Cold Storage (Consolidated Liquidity) ├── Output 2: 546 sats ──► Inscription Cold Storage (Protected Ordinal Output) └── Output 3: 454 sats ──► Miner Priority Fee (Direct Private Mining Pool Push)