Requant documentation

Using Requant Lab

Requant Lab plays virtual proof-of-work networks. Open it at requant.network/lab. Nothing needs to be installed and there is no account. The interface is in English and Russian (EN/RU at the top).

First visit

Guide at the top opens a tour in three chapters: what is on the screen, an experiment of your own, the run taken apart. The tour can be stopped at any step, and the same menu holds a glossary of terms (reorganization, orphan, difficulty, seed, series and more).
Start with an example. The list at the top has ready worlds (a split, attacks, hashrate surges) and real networks such as Bitcoin. Something happens in each of them.

Watch

The run is computed on the server; you watch a recording. Pause, tempo (×20 is twenty times faster than world time), back to the start, and the slider: drag it anywhere, forward and back.
Jumps. Next block, next fork and next event go straight to what matters. The run's chapters (the start, each impact, the outcome) are buttons: a click goes to the start of a chapter.
The main figures. Found: blocks the miners found. Height: the main chain's length. Off chain: blocks that lost the race. Reorgs: how often nodes dropped their branch for another. Branches: versions of the chain in the network now. Difficulty: how hard a block is to find, against the start. Found equals height plus off chain.
The stage. The network as a constellation: dots are nodes, the large ones miners; the number in a label is the node's share of the main chain's blocks. Blocks fly along the links, a ring is a block just found, the parts of a split network drift apart, the colour is a node's branch. The switch beside it shows the network on a globe instead. Drag to turn, use the wheel or two fingers to zoom, click a node to inspect it.
Before and after. The same run before the first impact and after it, side by side. One run is one throw of chance; to tell an effect from luck, compare with a clone or run a series (below).

Build an experiment

Build mode puts the plan on a timeline under the stage. Each impact is a bar on its lane (miners, nodes, connectivity): drag it to move it in time, drag an edge to stretch it, click it to set it up. Any edit rebuilds the world a second later.
Impacts. Miner power and hashrate change power; nodes offline switches nodes off; partition splits the network; latency, bandwidth and packet loss spoil the links; pool strategy, eclipse and the pool attack are attacks; load adds a burst of transactions. The die beside a lane makes an impact random: it fires with a set chance on each tick, repeatably by seed. Targets are picked by clicking nodes on the stage.
Your network. How many nodes and how they are linked, delays and loss on the links, geography, miners and pools, the difficulty rule and the block reward. A real network's profile can be the starting point. The network stays under every plan; a network has several plans.
Compare with a clone. When the plan has impacts, the lab builds the same world without them on the same seed and shows the figures side by side: what the impact did and what was chance.
TOML. The whole world as scenario text: copy it, edit it by hand or paste someone else's. A scenario that does not build leaves the world before on the screen and says what is wrong.
Library. Plans and networks are kept in this browser and can be exported and imported as a JSON file. Worlds of the session can be opened again.

The run taken apart

The tabs under the stage:

Chain: the tree of blocks, the main chain and the side branches. Click a block to see who found it and how it spread.
Blocks: every block in a table, with height, finder, time, branch and how many nodes took it.
Journal: finds, reorganizations and which node took which tip when; it can be narrowed to one node.
Detailed journal: every message of the run. The browser computes the same world on the same seed again right in the tab, and the result matches the server's. Search it by text, node 2, #17 or block 17. The browser does this for worlds of up to 32 nodes.
Network: difficulty and power over the run, and when and why the difficulty was recomputed. Where the difficulty adjusts, a control is offered: the same world at a fixed difficulty.
Result: blocks, orphans, reorganizations, interval, coin issuance, who found the blocks and, with pools, their rewards and payouts to miners. Download it as a PDF report or send it as a link.
Server: long worlds on the server and a series of runs (below).

Series and server worlds

A series of runs plays the same world on many seeds and shows the spread of each figure with 95% intervals; two worlds are compared on shared seeds. It answers the question one run cannot: which difference is real.
Worlds on the server go on without an open tab: pause, continue, clone, stop and download them. There are no accounts: a world opens with a key kept in this browser, and an idle world is deleted after 7 days.
Quotas are counted per address per hour and keep the server shared; the current limits are in the API's health answer.

Save the moment puts the world at this second into a file; Open a moment brings it back.
Share gives a link that opens the same world at the same moment.
Video records a clip of the stage with the figures as an MP4.
Files are named requant-lab-….

The examples include three Requant protocol scenarios (R01-R03). They open in the TOML editor and run on the server, where every block is a real Requant regtest block checked by each node with Requant's consensus code. The browser does not compute them. See Real Requant blocks in the lab.

Limits

The lab is a model: its figures are the output of the scenario and seed, not measurements of the Requant testnet or of a real network. Real-network profiles are scaled for a demonstration. See How the lab models a network.