Skip to main content
Releases are git tags in the contracts repo. This page is generated at build and lists every tag with its date and title. A tag marks the source that a deployment was built from. Match the tag to the commit shown on the explorer for each address on Addresses. Generated pages in these docs (Addresses, Parameters, Books and tiers, Smart contracts, Access controls) are rebuilt from the same checkout, so a docs commit and a contracts tag together pin one consistent snapshot. The core contracts are immutable. A new tag that changes Stockline, USDGPool, LiquidationModule, or EquityOracle means a new deployment, not an upgrade. Parameter changes do not need a tag; they go through the Timelock and show up on Parameters.

​
Tags

No tags yet. The contracts repo is pre-audit and has not cut a release. Until the first tag, treat the testnet addresses on Addresses as the only release. They were deployed from the main branch of the contracts repo. The commit is visible on the explorer’s verified-source page for each contract. When a tag lands, this table fills in on the next build and the row links to the tag on GitHub. What a first release will include: the audited core, the launch books in Books and tiers, and the launch parameters on Parameters. Read Security for the audit status.