Changelog

Release history for the Monolythium blockchain software (monod). This page tracks protocol upgrades, new features, and breaking changes across all network environments.

Current Version

v0.1.0 -- Initial public testnet release.

Release History

Version	Date	Network	Description
v0.1.0	2026-03-28	Testnet	Initial public testnet launch. LythiumBFT consensus, full EVM support, x/validator registration burn, x/burn fee split (90/10), 53 validator cap, IBC module (activates at block 500K).

정보

Mainnet releases will be added to this table as they are published. Each release undergoes a full testnet validation cycle before mainnet deployment.

Version Format

Monolythium follows Semantic Versioning:

Component	Meaning
Major (X.0.0)	Breaking consensus changes, state machine upgrades requiring coordinated network upgrade
Minor (0.X.0)	New features, non-breaking protocol improvements
Patch (0.0.X)	Bug fixes, performance improvements, no state machine changes

Upgrade Procedures

All network upgrades follow a governance-driven process. Validators must upgrade their monod binary within the specified upgrade window.

How Upgrades Work

1. Proposal -- A software upgrade proposal is submitted on-chain via the governance module, specifying the target block height and new binary version.
2. Voting -- Validators and delegators vote on the proposal during the voting period.
3. Execution -- If the proposal passes, all validators must upgrade their binary before the target block height. Nodes running Cosmovisor handle this automatically.

경고

Failing to upgrade before the target block height will cause your node to halt at the upgrade block. The node will not produce or validate blocks until the binary is updated.

Automated Upgrades with Cosmovisor

Cosmovisor manages binary upgrades automatically by watching for on-chain upgrade plans. This is the recommended approach for all validators and node operators.

See Cosmovisor for setup instructions.

Manual Upgrades

For operators who prefer manual control:

1. Stop monod before the upgrade height
2. Replace the binary with the new version
3. Restart monod

See Upgrades for the detailed manual procedure.

Governance Upgrades

All state machine changes require an on-chain governance proposal. This ensures that:

• The validator set explicitly agrees to protocol changes
• There is a public record of every upgrade decision
• Upgrades are coordinated to prevent chain splits

For details on submitting and voting on proposals, see Governance.

Following Updates

Stay informed about upcoming releases and upgrades:

Channel	Link
GitHub Releases	mono-labs-org/mono-chain/releases
Discord	#announcements channel
Documentation	This page (updated with each release)

Validator Operators

Enable notifications on the mono-chain GitHub repository to receive alerts for new releases. Critical upgrades are also announced in the Discord #validators channel.