The governance system contract went live this week. Not "coming soon," not "design phase" — deployed, callable, and visible on the explorer.
What shipped
Every Asentum validator can now create proposals, vote with stake-weighted ASE, propose amendments, and execute passed proposals — all on-chain. The governance contract lives at 0x0000...0003 and supports four proposal categories: general, parameter, AIP (Asentum improvement proposal), and library.
Library proposals are the interesting ones. When a library proposal passes, the JavaScript source code is stored on-chain and automatically injected into the VM's SES compartment. Every contract on the network can use it. The chain literally votes on what code is allowed to run.
The explorer
The block explorer at testnet.asentum.com now has a Governance tab. You can browse all proposals, see vote tallies with for/against bars, view amendments, and for library proposals, read the full source code. It's read-only on the explorer — voting happens through the website or the Asentum wallet extension.
We also added an Approved Libraries page that shows every governance-approved library with expandable source code. This is the asentum_getApprovedLibraries endpoint that the docs reference — now it has a UI.
RPC endpoints
Three new endpoints landed alongside the explorer views:
GET /governance/libraries— all approved librariesGET /governance/library/:name— single library by nameGET /governance/locked/:address— how much ASE a voter has locked in active proposals
These follow the same pattern as the existing /governance/proposals and /governance/proposal/:id endpoints. Everything the frontend needs to build a full governance dashboard.
What's next
The website at asentum.com/governance has the interactive voting UI ready — connect the Asentum wallet extension, browse proposals, vote for or against, create new proposals. It's built and waiting for the Chrome extension to land in the store. Once it does, governance becomes fully self-service.