MSG Chain

Ecosystem Registry

Applications that are building on MSG Chain and are listed as first-batch ecosystem applications. An entry records an integration that is under way: it is a factual record, not an endorsement, a partnership statement, or an audit conclusion.

What registration does and does not mean

  • Registration is not an endorsement, an investment recommendation, a partnership statement, or an audit or security conclusion.
  • Registration does not mean mainnet is live. Mainnet status is not launched (No-Go) and flips only on the official launch announcement.
  • Registration does not mean the listed project is production-ready, verified, audited, or generally available.
  • Registration is not a ranking, a rating, or a comparison between projects. The status shown is the chain-side integration state recorded by MSG Chain, not the project's own product maturity.
  • Each project's own official channels are the only authority for its features and availability. A project is added on a recorded authorization — for this first batch the three applications are authorized by their owner — its name is published only on that basis, and its official URL is cited read-only. A listing is removed on the project's request.

First batch

Three applications are recorded as the first batch. All of them carry the same recorded status: integration in development. No public chain endpoint has been published yet, so none of them has been validated against a public chain.

Billion.Life

Consumer dApp

Integration in development

Official site: billion.life

A consumer application that describes itself as built on MSG Chain, combining personal tokens, social interaction, a decentralized store with contract escrow, and traffic monetization.

Aligning its client with the frozen MSG Chain contract: native denomination and decimal scale, the official signing client, and the published route ownership. Its own integration notes still record client-side corrections being applied.

AI Pay

Wallet and payment gateway

Integration in development

Official site: aipay.im

A local-first Web3 wallet with merchant acquiring and payment-gateway functions, shipped as an installable static application that keeps wallet material and merchant data in the browser.

Its MSG adapter is in place and disabled by default (fail-closed). It is enabled once MSG Chain publishes the public window parameters, a browser-reachable endpoint, wallet signing and broadcast, and end-to-end evidence.

AIDID

Decentralized identity application layer

Integration in development

Official site: aidid.im

A decentralized identity application layer and adapter for MSG Chain, covering DID registration and resolution, a third-party login identity layer, and verifiable credentials.

Its adapter follows the frozen contract; the canonical on-chain DID lifecycle is not yet closed by the chain side, so its own material keeps the project at its pre-integration stage.

Each entry shows the mark its own project publishes today. The Billion.Life mark is still the framework default rather than a mark of that project's own, and it is shown temporarily at the owner's instruction; it will be replaced once the project publishes a new one.

A name that looks similar

The chain-side AIPAY protocol family published in the whitepaper is a chain contract and adapter surface. The entry named AI Pay above is an application-side wallet and payment-gateway project. The two are named alike but are not the same object.

Status vocabulary

The registry uses four recorded statuses, and only the first one is in use today. A status records what is true now; it is not upgraded on the basis of a plan.

Recorded status What it means
Integration in development The client is being aligned with the frozen contract, and/or built against a local development network. No public endpoint has been used, because none has been published. This is the status of every entry above.
Local integration verified The conformance self-test passes against a local development network of the same build. This still says nothing about a run on a public chain.
Public endpoint integration MSG Chain has published the public window parameters and the project has re-run the same self-test against a published endpoint.
Live on the public chain The project runs against the public chain in normal operation and publishes its own availability statement.

No entry has reached the second, third or fourth status. The registry records what is true today, and it does not upgrade an entry because a plan says so.

How a listing is recorded

A listing is published on a recorded authorization. For the applications in this first batch that authorization comes from their owner, so no separate per-project confirmation is required. The material below is what a project supplies so the entry is useful, and a listing is removed on the project's request.

  • The public name the project wants shown.
  • An official URL, if the project allows a read-only citation.
  • An official short description, or permission to summarise the project's own official pages.
  • A logo or screenshot file, or an explicit decision to list text only.
  • Confirmation that the project agrees to be listed under that public name (for this first batch the owner's authorization covers it).
  • Confirmation that the official URL may be cited read-only, without republishing project content and without a rating.

A listing changes nothing else. It does not change mainnet status, does not upgrade any whitepaper module status, and is not a release decision.

Machine-readable registry

The same entries, statuses and boundaries are published in machine-readable form, so a tool or agent reads the registry instead of parsing this page.

Open ecosystem.json Integration facts JSON

Before a project can move on

A listed project has to align the chain identity, denomination, address format, ports, route ownership and signing client before anything else can be verified.

Open the developer page

Building on MSG Chain

Start from the docs, the whitepaper machine entry and the local development path; a public chain endpoint has not been published yet.

Open docs Start in 15 minutes