Without this page, the Build part would be only an invitation. This is where what you will trip over is stated in advance, so you decide before writing rather than after deploying.

Limit	What it means for you	Label
The EVM base is pre-stable	This is the project's largest technical risk, and it touches your code directly. Pin versions, keep load low, leave an upgrade path	RUNNING, with risk
The virtual machine executes sequentially	Enough for low permissioned load; do not design something needing high throughput and measure only afterwards	RUNNING
The network is gasless	Users pay no fee — but do not read that as "no limits". There are anti-abuse quotas, and the fuel token is non-transferable	RUNNING
No interoperability channel is live yet	The bridge and border gate are built and tested, but opening the first channel is a gate not yet passed. Do not build flows depending on assets crossing networks	Gate not passed
A test period can be rebuilt	Balances, addresses, contracts and history of an abandoned build do not flow into the next one. Keep your own copy of anything you need	RUNNING
No independent audit yet	It is a mandatory gate of the Real assets level — so do not put other people's real value here	Gate not passed
The repository is closed	You can read the interface, not the inside; you cannot rebuild the whole stack yourself	LEFT BLANK

Diagram

flowchart TB I["Your idea"] --> Q{"Does it need:<br/>high throughput?<br/>assets crossing networks?<br/>other people's real value?"} Q -->|"none of the three"| G["You can build on a test period now"] Q -->|"any of the three"| W["You are waiting on a gate<br/>— the table above names which"]

Figure 27 — Three questions that decide whether you build now or wait.

One thing worth stating separately: do not measure performance here and draw conclusions about later. This document deliberately promises no performance number — no throughput, no finality latency. What you measure on a test period is the number of a build made for testing, on this phase's infrastructure; it says nothing about the official network, in either direction.

And the easier half: most tooling you already know still works, because the chains produced are EVM appchains. What has to be relearned is not syntax but the rules underneath — Contracts and the compliance gate covers it.

In short: a specific list of limits is what someone overstating their case does not want to write — so use it as a test on every piece of infrastructure you consider building on, including this one.