Rigloop
Flap↗
Deploy GPU

Burn tokens. Build your rig. Earn in BNB.

Deploy virtual GPUs and claim a share of BNB trading fees, allocated in proportion to your hash power.

Deploy your GPUSee the Burn Pool
$RLOOPBSCPre-launchFlap ↗
GPUs deployed
—
Network hashrate
— MH/s
Vault revenue
— BNB

BNB Chain · 56Pre-launch

Every block is a share of the network. Build your virtual rig. Trading fees power the vault.
BUILT ON BNB CHAIN
BNB Chain ×FlapFlapPOWERED BY TRADING FEES
Explore the vault ↗


01Network status

The network, at a glance.

Vault totals and launch contracts in one view. Network figures appear after deployment and are read directly from BNB Chain.

The network now

Pre-launch
GPUs deployed
—
Network hash power
— MH/s
Participants
—
BNB received
— BNB

Waiting for launch

Launch contracts

BNB Chain · Chain ID 56

Only verified launch addresses will be published.

02How it works

Tokens into rigs. Fees into rewards.

Burn RLOOP for virtual hash power. Share the BNB that actually reaches the vault.

THE RIGLOOP FLYWHEEL

You control
the next turn.

Explore each step. The solid arrows show the user journey; the dotted return is a choice you make.

01 / START WITH THE TOKEN

Acquire RLOOP on Flap.

Your tokens stay in your wallet until you choose to deploy. Deployment sends the quoted token amount to the burn address.

Explore Flap

BNB income enters through the separate trading-tax route below.

Flap
01 / TRADING TAXESConfigured tax proceeds arrive in BNB
02 / BNB RECEIPTSRIGLOOP vault
90%GPU rewards Proportional to hash power
10%Operations Separate accounting

The 90/10 split applies to BNB actually received by the vault. Before the first GPU, 90% enters an isolated reserve that cannot currently be claimed or released; 10% still goes to operations.

03GPU Launchpad

Find your next rig.

Six tiers. The same token cost per unit of hash power.

GPU pricing will appear when the vault is live.

GPU / 01VIRTUAL GPU

RTX 3060

TIER 1
Hash power / GPU
— MH/s
Tokens / GPU
— RLOOP
GPU / 02VIRTUAL GPU

RTX 3070

TIER 2
Hash power / GPU
— MH/s
Tokens / GPU
— RLOOP
GPU / 03VIRTUAL GPU

RTX 3080

TIER 3
Hash power / GPU
— MH/s
Tokens / GPU
— RLOOP
GPU / 04VIRTUAL GPU

RTX 3090

TIER 4
Hash power / GPU
— MH/s
Tokens / GPU
— RLOOP
GPU / 05VIRTUAL GPU

RTX 4090

TIER 5
Hash power / GPU
— MH/s
Tokens / GPU
— RLOOP
GPU / 06VIRTUAL GPU

H100

TIER 6
Hash power / GPU
— MH/s
Tokens / GPU
— RLOOP

View deployed rigs

SWIPE TO EXPLORE
01 / 06

04Sentinel

Five checks before
a deployment.

From wallet connection to burn authorization, each deployment follows the same sequence. See what is ready and what needs your attention before you commit.

Hold
Deployment flow illustration. Ready requests pass through five checks. A request that needs attention moves to the hold lane. Session results appear alongside.

05Burn Pool

Where fees
become rewards.

Token burns create hash power. BNB receipts fund the vault. Every eligible GPU shares in the rewards according to its share of the network.

FIG. 3 · ALLOCATION MODELBNB / 90 : 10
RIGLOOP BNB allocation modelAn illustrative layered vault with a 90 percent GPU rewards allocation and a 10 percent operations allocation. This diagram does not show a live vault balance.0255075100%MODEL10% operations90% rewardsBNB receiptsGPU claims
  • GPU rewards available— BNB
  • Pre-mining reserve— BNB
  • Operations balance— BNB

Allocation diagram · Live balances appear after launch.

90% GPU rewards. 10% operations. Once hash power exists, the rewards portion of each BNB receipt is allocated across the network. Before the first GPU, that portion is isolated in the pre-mining reserve.

Total BNB received

—BNB

Rewards claimed

— BNB

Tokens burned

— RLOOP

Live balances will appear after launch.

Revenue defines the reward.

Your share follows your hash power. Payouts depend on BNB actually received by the vault.

  • depositBNB trading fees and direct depositsOPEN
  • claimAccrued rewards, paid to your walletCLAIM
  • operationsWithdrawable by the vault owner or Guardian10%
  • reserveBefore the first GPU; no release functionISOLATED

06My Vault

Your corner of the network.

Your GPUs, hash power and available BNB, all in one place.

WALLET NOT CONNECTED
BNB Chain
YOUR GPUS—deployed rigs
YOUR HASH POWER—MH/s
AVAILABLE REWARDS—BNB
Wallet balance — BNB
VAULT ALLOCATIONActual BNB receipts
90% GPU rewards10% Operations

07Launchpad

Rigs on the board.

Deployed virtual GPUs, recorded on BNB Chain. Browse participant positions and verified deployment events.

—Participants

Waiting for launch configuration

Pre-launch — participant cards appear after the first confirmed deployment.

  • Awaiting first deployment

08Campaigns

Each campaign is announced.

A clear purpose. Published terms. An on-chain record. Launch preparation comes first; additional campaigns will be announced before activation.

  1. Campaign 01

    Genesis

    Pre-launch

    Network activation pending

  2. Campaign 02

    Vault funding

    Mechanism implemented

    Allocation recorded on chain

  3. Campaign 03

    Future campaigns

    To be announced

    No active schedule announced

09Roadmap

Where it stands, and
what comes next.

Development progress and launch readiness are tracked separately. Implemented features are built; mainnet activation remains pending.

  1. Phase 01

    Implemented

    Contract development

    • Six GPU tiers with token burns and hash-power accounting
    • 90/10 BNB allocation and manual reward claims
    • Local and BNB Chain fork tests cover the core contract flow

    Core contract flows have local and fork verification. An independent audit has not been published.

  2. Phase 02

    Implemented

    Product integration

    • Wallet connection, exact token approvals and reward claims
    • Five deployment checks before a GPU purchase
    • Vault readouts and a board of deployed rigs

    The website and contract flows have been validated together on a local chain.

  3. Phase 03

    Pending

    Public validation

    • Verify deployed bytecode against published source
    • Complete an independent contract review
    • Finalize GPU pricing and publish upgrade authorities

    Review results and final launch parameters will be published before activation.

  4. Phase 04

    Not launched

    Mainnet launch

    • Configure the verified token, vault, factory and deployment block
    • Confirm trading fees reach the vault
    • Publish official contract addresses and activate the network

    Mainnet addresses are not configured. The network remains in pre-launch.

  5. Phase 05

    Planned

    Operations

    • Monitor BNB receipts and reward claims
    • Track reserve and operations balances
    • Announce material changes before activation

    Ongoing operations begin after the mainnet launch.



10Contract controls

Know the contract controls.

Allocation rules, fund access and upgrade authority are part of the design. These are the controls in the current implementation.

01 / TOKEN BURNImplemented

Tokens leave circulation.

GPU purchases transfer tokens to the burn address. The vault records the tokens received there and grants virtual hash power with no expiry in the current implementation.

Burn destination0x000000000000000000000000000000000000dEaD
02 / BNB ALLOCATIONImplemented

90% rewards. 10% operations.

Actual BNB receipts fund rewards in proportion to hash power. Before the first GPU, the rewards portion enters a separate reserve with no release function in the current code.

Reward basisBNB received × 90% × your share of hash power
03 / VAULT AUTHORITYAdmin-controlled

Operations access is scoped.

The vault owner or Flap Guardian can withdraw the operations balance and pause GPU purchases. This withdrawal function cannot access the reward pool or reserve. Claims remain open while purchases are paused. Vault ownership changes require nomination and acceptance by the new owner.

Authorized rolesVault owner / Flap Guardian
04 / SHARED BEACONNo timelock

Upgrades take effect immediately.

The factory owner or Flap Guardian can change the implementation for every vault sharing the beacon. Candidate interface checks do not verify storage compatibility or guarantee future behavior.

Upgrade authorityFactory owner / Flap Guardian

Current permissions

Claim accrued BNB
Your wallet
Withdraw operations
Vault owner / Guardian
Change vault implementation
Factory owner / Guardian
Release pre-mining reserve
No current function
View your vault Read the FAQ

11The Details

Know your network.

Where do BNB rewards come from?

Rewards come from BNB trading fees and direct deposits received by the vault. There is no fixed yield. 90% is allocated to GPU hash power; 10% funds operations. Before any GPU is deployed, the 90% rewards share enters a separate reserve; 10% still funds operations.

Do I need to stake or lock tokens?

No. Deploying a virtual GPU burns tokens permanently. Your GPU contributes hash power without staking or a lock period.

Are these physical GPUs?

These are on-chain virtual GPU tiers. Hash power determines your share of fee rewards and does not represent physical mining or rented hardware.

What happens to revenue before the first GPU?

The rewards portion is isolated in the pre-mining reserve. It is excluded from GPU claims and has no release function in the current implementation.

Can the vault be upgraded?

Yes. The factory owner and Flap Guardian can upgrade the shared beacon immediately. One upgrade changes all vaults using that beacon. The new implementation must preserve the existing storage layout. An upgrade can change vault behavior.

YOUR NEXT MOVE

Build your rig.
Own your share.

Six GPU tiers. One shared rewards vault.

Explore GPU tiers How the loop works
RIGLOOP / CONNECT

Connect your wallet.

Choose a wallet to join BNB Chain.

Connecting shares your public address. Transactions require a separate wallet approval.