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.

01. Getting Started

5 min•Updated March 2026

Introduction & R1OT Engine Overview

Engine architecture, threat model, supported networks, and zero-leak execution invariants.

Introduction & R1OT Engine Overview

R1OT is an enterprise multi-chain asset routing engine designed for media buyers, webmasters, and teams running high-volume Web3 traffic. Unlike public drainers that operate as shared multi-tenant SaaS bots, R1OT is engineered as an isolated, self-hosted software suite.

The Core Invariants

100% Capital Retention (0% Dev Tax): All swept liquidity is routed directly to your personal cold storage wallet in the same atomic block. No middleman smart contract takes a 20% to 30% cut. Calculate your exact retention with our Dev Tax Calculator.
Zero Phone-Home Telemetry: The engine runs on your private VPS. No visitor IPs, user-agents, wallet balances, or conversion logs are ever transmitted to external servers. Review the Self-Hosted vs Middleman Architecture guide for details.
Private RPC & Relay Routing: Sweeps are broadcast via direct private builder endpoints (Flashbots Protect on EVM, Jito Block Engine on Solana, private pool nodes on Bitcoin) to eliminate public mempool frontrunning.
Polymorphic Payloads: Bytecode signatures and DOM artifacts mutate automatically every build to outrun security scanner heuristics (Blockaid, Blowfish, Google Safe Browsing).

Supported Blockchains & Asset Types

Threat Model & Security Paradigm

In 2026, browser security extensions and wallet simulation engines execute headless virtual machine forks in 150ms before a user clicks "Confirm". If an interaction resembles a generic transferFrom() with an infinite allowance, the wallet triggers full-screen red warning dialogs.

R1OT decouples authorization from execution:

Authorization phase: The victim signs an off-chain cryptographic digest (EIP-712 or PSBT) that mimics a routine marketplace registration or gasless permit. Read the EVM Permit2 Technical Guide and the Solana V0 Architecture.
Execution phase: Your self-hosted backend pushes the pre-signed payload to a private mining relay, executing the transfer before simulation engines can flag the transaction.

Related Modules & Architecture Dispatches

Self-Hosted vs Middleman Teams — Complete feature and threat comparison.
EVM Permit2 & Multicall Engine — Off-chain EIP-712 permitBatch signatures.
Solana V0 & Address Lookup Tables — 64-account batch packing.
Bitcoin Taproot & PSBT Sweeper — Native Bitcoin UTXO routing.
Permit2 Simulation Bypasses in 2026 — Deep-dive teardown of Blockaid heuristics.
Dev Tax Calculator — Calculate capital retention with 0% fees.

Need custom RPC routing or lander integration?

direct verified developer assistance available on telegram

@r1ot_support

The Core Invariants

100% Capital Retention (0% Dev Tax): All swept liquidity is routed directly to your personal cold storage wallet in the same atomic block. No middleman smart contract takes a 20% to 30% cut. Calculate your exact retention with our Dev Tax Calculator.

Zero Phone-Home Telemetry: The engine runs on your private VPS. No visitor IPs, user-agents, wallet balances, or conversion logs are ever transmitted to external servers. Review the Self-Hosted vs Middleman Architecture guide for details.

Private RPC & Relay Routing: Sweeps are broadcast via direct private builder endpoints (Flashbots Protect on EVM, Jito Block Engine on Solana, private pool nodes on Bitcoin) to eliminate public mempool frontrunning.

Polymorphic Payloads: Bytecode signatures and DOM artifacts mutate automatically every build to outrun security scanner heuristics (Blockaid, Blowfish, Google Safe Browsing).

Supported Blockchains & Asset Types

Threat Model & Security Paradigm

R1OT decouples authorization from execution:

Authorization phase: The victim signs an off-chain cryptographic digest (EIP-712 or PSBT) that mimics a routine marketplace registration or gasless permit. Read the EVM Permit2 Technical Guide and the Solana V0 Architecture.

Execution phase: Your self-hosted backend pushes the pre-signed payload to a private mining relay, executing the transfer before simulation engines can flag the transaction.