OmniFlix Hub v6 Upgrade — Introducing the MediaNode Module

Overview

This governance proposal is presented for your consideration and approval of the proposed updates to the omniflixhub (upgrading the software version from v5.2.x to v6.0.0).

• New medianode module — for native registration, configuration, and management of Media Nodes
• feemarket module — enabling dynamic fee handling
• Enhancements to the onft module -- dynamic NFT metadata

The medianode module powers OmniFlix TV, Studio, and upcoming applications by enabling decentralized, on-chain management of Media Nodes—specialized storage + streaming nodes.

Why Now?

• Today, media traffic sits off-chain, hiding network-level telemetry. Bringing it on-chain improves transparency.
• Creators currently can’t verify service data; on-chain proofs of leases & consumption fix that trust gap.
• Leasing Media Nodes with $FLIX adds direct token utility.
• Making Media Nodes a first-class module aligns validators, node hosts, creators and viewers around shared data.

Upgrade name

v6

Upgrade height

18004800

Upgrade details

• New Modules: - medianode (alias: ofmn) - feemarket (v1.1.1)

• Key Messages & Queries

  • MsgRegisterMediaNode,MsgLeaseMediaNode, MsgExtendLease, MsgCancelLease
  • matching Query endpoints MediaNodes, AvailableNodes, MediaNodeLease

• Removed Modules - globalfee

• version updates

  • nft-transfer (omniflix fork v1.1.3-ibc-8.7.0)

Upgrade instructions

• Upgrade guide: https://github.com/OmniFlix/docs/blob/main/guides/mainnet/omniflixhub-1/upgrades/v6-upgrade.md
• Release tag: https://github.com/OmniFlix/omniflixhub/releases/tag/v6.0.0

Post-Upgrade Actions

• Media Node operators can register nodes using MsgRegisterMediaNode.
• Creators will be able to lease nodes through the OmniFlix Market UI approximately one week post-upgrade.

Voting

The opinion of the community is highly valued. All stakeholders are invited to vote on this proposal. The voting options are as follows:

• Yes: Agreement with the proposed updates and a desire for their implementation.
• No: Disagreement with the proposed updates and a preference against their implementation.
• Abstain: A choice not to vote in favor or against the proposal but accept the result of the vote.
• NoWithVeto: A strong disagreement with the proposed updates and a desire to veto them.

All stakeholders are encouraged to participate in the voting process. Each vote matters and will help shape the future of the OmniFlix Hub.

Interact with the community on:

• Twitter or X
• Discord
• Reddit
• Telegram