Prop 71: Initia Chain Upgrade Proposal #3: Post-Reactor Fixes & IBC Preparation

1. Background

This proposal introduces a follow-up maintenance upgrade after the Reactor upgrade (Proposal 64). The purpose of this upgrade is to fix several minor but previously uncaught issues, improve the developer and operator experience, and prepare the infrastructure for upcoming IBC-based features.

2. Release Binary & Upgrade Resources

• Release Name/Version: v1.3.1
• GitHub Release: https://github.com/initia-labs/initia/releases/v1.3.1
• Upgrade Height: 13,539,863
• Estimated Time: February 17, 2026, at 6:00 AM UTC

3. Proposed Changes

MoveVM

• Sort modules by dependencies during initialize script execution: Ensures a deterministic and dependency-aware execution order for initialization scripts, preventing potential initialization failures caused by non-deterministic module ordering.
• Nano-second block time support: Improves timestamp precision handling to better support higher-resolution time representations across events, SDKs, and indexing pipelines.

Multisig

• Enhance member update logic: Improves correctness and consistency when updating multisig members, reducing edge cases related to member replacement, removal, and threshold changes.

JSON / Events

• Pretty print enum JSON events: Improves the readability and clarity of enum-based events when serialized to JSON

Initia Core (FungibleAsset)

• Fix dispatchable FungibleAsset restriction message type URLs: Corrects message type URL handling in restriction error messages, providing clearer and more accurate feedback to developers and operators.

IBC Hook

• Allow MsgExecuteJSON : Extends IBC hook support to allow JSON-based execution messages.
• Use source-chain store for async callbacks instead of memo storage: Enables asynchronous callback handling using source-chain state, avoiding reliance on IBC memo fields and improving the robustness and extensibility of callback workflows.

OPinit

• Prepare IBC relay support for oracle and attestor updates: Introduces the necessary packet handling and infrastructure to support relaying oracle updates and attestor updates via IBC in future upgrades.

Governance Votes

• YES – You support updating Initia with the changes proposed in this release.

• NO – You oppose implementing the proposed update to Initia.

• NO WITH VETO – This vote signals strong objection. It is used when the proposal is considered:

  1. Spam or irrelevant to Initia,

  2. Harmful to minority stakeholders, or

  3. In violation of Initia’s governance principles or encourages such violations.

     If more than one-third of total votes are cast as "No with Veto," the proposal will be rejected and any deposits will be forfeited (burned).

• ABSTAIN – You choose not to take a stance on the proposal but want your vote counted toward the quorum.