Replace a guess with a structure.
The build centres on deterministic protocol graphs. Contract artifacts become explicit nodes and relationships instead of a free-text interpretation being treated as an execution plan.
Protocol action compiler · Nuvixes
Ver
Public betaDeterministic protocol graphs turn intent into inspectable unsigned actions without hiding the path in a black box.
Why this exists
A protocol should be understood before it is acted on.
A contract ABI lists functions. It does not explain the relationships, privileges, or consequences around them. Ver tackles the gap between having code in front of you and knowing what an action actually means.
Keep explanation separate from authority.
AI can help explain the graph, but the underlying path must remain inspectable. Ver prepares unsigned actions so the wallet retains signing authority. The experience aims to make the next step clearer without asking someone to surrender the decision.
Support has to reach the actual chain.
The September release moved beyond the initial development workflow to BOT Chain mainnet support. Packaging and release work followed: a protocol tool also needs to install and run predictably for another builder.
Build journal
The turns
along the way.
Recorded milestones from the build. Dates describe these events, not the entire project history.
Release workflow repaired
Repository history records a fix to build Windows-initiated staging releases on Linux.
BOT Chain support released
The recorded release adds BOT Chain mainnet support, followed by package metadata normalization.
Where it stands
What works today.
A published protocol-compilation product with an inspectable graph and unsigned-action approach. Specific supported paths should be checked in the current product.
The next chapter
What comes next.
Broaden protocol coverage while preserving readable, deterministic outputs.
Based on the Ver repository history, project description, and original protocol demo.
Continue exploringEmberline + Attest