
EVERY BLOCK
BEGINS WITH
WORK.
Build a rig. Search the nonce.
Turn raw computation into a chain you can verify.
CONVEYOR →
Boot your silicon.
60-second session. Mining pauses when this tab is hidden. Your device performs the work; a wallet is optional.
> Node ready. Select a rig to begin. > No payment is required for local computation.
A chain. Not a black box.
| HEIGHT | BLOCK HASH | DIFFICULTY | STATUS |
|---|---|---|---|
| No blocks yet. Start a mining session above. | |||
Proof is in the details.
Select a block to inspect its parent, challenge and nonce. Every accepted block is recomputed before it enters this record.
Records stay in this browser. Export a chain to verify it independently.
Choose your mining temperament.
Different silhouettes. Actual CPU budgets.
Inspect the
block engine.
Drag to orbit the reactor. Its crystal core responds when your miner finds a verified block.
- GEOMETRY
- PROCEDURAL VOXELS
- INPUT
- POINTER / ARROW KEYS
- SIGNAL
- VERIFIED BLOCK EVENT
Visualizes your local mining session.
Change one bit.
Break the proof.
Inspect your latest block, then alter its nonce.
The verifier trusts computation, not the label.
Mine a block to unlock this inspection.
Inside the machine.
From a fractured crystal to a linked block.
Watch the mine come alive.
Finite inventory.
Visible arithmetic.
The FLAP BTC reward design uses funded seasons, fixed epoch ceilings and valid-proof allocation. Explore the schedule before a season opens.
A fixed budget.
A moving challenge.
- FUNDInventory measured after token transfer tax. No unfunded reward balance.
- CHALLENGEEach epoch derives its seed from its preceding BNB Chain block.
- PROVEDouble SHA-256 binds the season, chain, claimant and nonce.
- SETTLEFirst valid claims fill a fixed capacity. One claim per address per epoch.
Four eras pay in an 8 : 4 : 2 : 1 ratio. Unclaimed inventory remains until season end. The on-chain season uses its own challenge; personal browser records are separate.
READ THE COMPLETE PROTOCOL ↗01 / What makes a block valid?+
A versioned header contains chain ID 56, a personal chain identifier, height, previous hash, miner label, difficulty, fresh challenge and nonce. Two SHA-256 passes must meet the leading-zero target. Import checks every link, input type and digest; editing any field breaks validation.
02 / Work, rewards and the treasury+
Browser blocks record computational work. A funded reward season opens after its contract, token inventory and start block are published. The included season implementation fixes capacity and halves rewards across four eras. The emission lab explores allocation from an existing inventory; it does not mint Bitcoin or credit wallet balances. FLAP treasury registration and reward validation are distinct contracts.
03 / The miner NFT concept+
SCOUT, FORGE and MONOLITH form the pixel hardware collection concept. Equipping a rig here chooses CPU workers. A collectible's on-chain ownership and any season eligibility require the published NFT contract; visual rarity never changes the validity of a hash.
04 / Permission and settlement+
The project vault retains primary and backup wallet management. Each authorized wallet can call its asset-management methods. Reward budgets must use actual funded inventory and published season terms. An exported work record is portable evidence, not a transferable token.
Give your Agent
a precise mission.
Copy a bounded mining task. The same header format powers browser workers and independent verification.