Skip to content
gnoversePublic

About

Replay gno.land mainnet's history against gno changes and report txs whose result would change

Resources

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

25 Commits

Folders and files

Repository files navigation

gnoreplay

Checks whether a change to gnolang/gno would execute gno.land mainnet's history differently: every recorded block is re-executed with the changed code, and every tx whose result differs from the one recorded on chain is reported.

  • gnoreplay/ — the replay tool. It is built inside the gno tree under test (copied to contribs/gnoreplay), so each commit is checked with its own application code.
  • server/ — a service that replays every push and PR on the tracked branches in the background, and publishes the results on its own pages. It only reads from GitHub. Replays run either on the server's box, or each on its own disposable cloud machine.
  • deploy/ — deploying it on Hetzner Cloud.

A full replay of mainnet takes 1h40m–2h on a 2-vCPU worker (about 650,000 blocks / 112,000 txs in October 2026) and grows with the chain, which is why this runs as a background service rather than a CI job.

License

Same as gnolang/gno: the GNO Network General Public License, see LICENSE.md.

About

Replay gno.land mainnet's history against gno changes and report txs whose result would change

Resources

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages