Every claim on this site has a matching entry here.
If a limitation is missing it is because we have not found it yet — not because we decided it read badly. Several of these are things a competitor would use against us.
- We cannot stop an invalid state root.
2 addresses may challenge on this rollup and 1 is active — all the operator’s. We detect and publish. We do not intervene, and we demonstrate the refusal every six hours rather than describing it.
- The roll counts keys, not people.
One operator running fifty nodes under fifty keys appears as fifty rows. Reputation blunts the incentive; it does not settle it. Proving independent infrastructure is a roadmap item and is not done.
- Deciding who was right is still centralised.
Settling a confirmed assertion needs a view of Ethereum that no contract on this chain has. One owner key makes that call today. It cannot alter anybody’s published attestation — every one is signed — but it is a single point and it is listed here rather than glossed.
- A careless node loses nothing.
There is no slashing, deliberately: the moment disagreeing costs money, everybody copies the majority and the one node that spotted a real fault goes quiet. The price is that lazy verification is cheap. Decay after fourteen days idle is the only pressure.
- Force inclusion is not an escape route.
Four days against a 100 ms block time. Worth monitoring, useless for getting a trade in, and anybody who calls it a fallback is describing something that does not work.
- The fund cannot make anybody file anything.
It moves money to an address the operators named. If that recipient takes it and files nothing, the only recourse is that the whole thing is on chain for ever. That is real, it is not a guarantee, and it is the weakest link in the design.
- A daily root proves what we recorded, not that we recorded everything.
Anchoring on Ethereum makes the day unrewritable after the fact. It cannot prove an attestation was never made. The defence against that is plural — many independent nodes each keeping their own copy — which is an argument for the network, not a property of the root.
- Most of the contracts are not deployed.
The token launches separately and everything keys off it. Until then the registry, tracker, hub, vaults and router are tested code awaiting audit, and every page that depends on one says so rather than rendering an empty table.
A Court of Attachment received presentments and recorded them. It could not pass sentence. Knowing that was the point of having one.