[IDEA] Open-Source Cosmos Mobile App Template Using ALYX as a Live ATOM Reference Chain

Hub Proposals Proposal Ideas
1

Hi Cosmos Hub community,

I am posting this as an early proposal idea to gather feedback before deciding whether to prepare a formal Community Spend draft.

Project website: alyxai dot org

The public dashboard, Get ALYX page, ATOM Pool 9 page, and proof references can be provided in a follow up comment after the topic is live

ALYX is a live Cosmos SDK and CometBFT Layer 1 blockchain on mainnet. It is already running with active validators, native DEX infrastructure, TokenFactory support, IBC routes, Genesis Liquidity Vaults, and an AI execution layer called Aether.

I want to lead with what was completed recently because it is directly relevant to this idea.

ALYX completed full IBC integration with the Cosmos Hub and executed its first full ATOM Genesis Liquidity Vault cycle on mainnet.

The live execution verified the full path:

ATOM was bridged from Cosmos Hub to ALYX through channel-1885.
Pool 9 was created using the verified ATOM IBC denom.
ATOM was submitted into the Genesis Vault.
The participant received an ALYX allocation.
The treasury matched the same ALYX amount.
Both ATOM and matched ALYX were added into Pool 9.
The LP shares were locked forever on-chain.

This means ATOM is now a first-class settlement and liquidity asset inside the ALYX mainnet economy.

ALYX also has a live Bootstrap Vault for Noble USDC through a separate IBC route, with Pool 6 liquidity locked permanently. Together, ATOM and USDC now serve as core settlement assets on ALYX.

Current ALYX mainnet status:

  • Live Cosmos SDK / CometBFT Layer 1

  • Cosmos Hub IBC route live

  • ATOM Pool 9 live

  • Noble USDC Pool 6 live

  • Permanent liquidity locks live

  • Native DEX live

  • TokenFactory live

  • Aether AI execution layer live

  • 6 active validators

  • 9 DEX pools

  • 18.64M ALYX reserve base

  • Public dashboard available through the ALYX website

The idea

I am considering a future Community Spend proposal for an open-source Cosmos mobile app template, using ALYX as the live reference implementation.

The request would likely be for the ATOM equivalent of $50,000, denominated in USD for budgeting clarity, with the final on-chain amount calculated in ATOM at submission time according to Cosmos Hub proposal requirements.

The goal is not only to build an ALYX mobile app.

The goal is to open-source a reusable React Native mobile template that other Cosmos SDK chains can fork, configure, and adapt for their own ecosystems.

Why this could benefit ATOM and the Cosmos Hub

ATOM is already live on ALYX through IBC and is now used as a settlement and liquidity asset inside the ALYX mainnet economy.

A mobile app template would create a cleaner user path for:

  • ATOM access through IBC

  • IBC asset balances

  • DEX pool discovery

  • Swap interfaces

  • TokenFactory asset display

  • Appchain-native user onboarding

  • Community liquidity programs

  • Cosmos SDK chain mobile UX

Cosmos has strong infrastructure, but many appchains still do not have a polished, configurable, open-source mobile app template for onboarding users. This project would provide a practical starting point for other builders.

Current mobile scaffold

The ALYX mobile architecture is already scaffolded using:

  • React Native

  • Expo SDK 52

  • Expo Router

  • WalletConnect v2 packages

  • Keplr-compatible wallet direction

  • Five-tab mobile structure

  • ALYX chain configuration

  • Mobile screens for trading, AI, profile, exploration, connection, signing, and pool details

The funding would be for completing, hardening, testing, documenting, and open-sourcing the app as a reusable Cosmos mobile template.

Proposed deliverables

The finished open-source template would include:

  • Wallet connection screens

  • Asset balance screens

  • ATOM / IBC asset display

  • DEX pool interface

  • Swap interface

  • Transaction preview and confirmation states

  • Mobile-safe API integration

  • ALYX reference implementation

  • Chain configuration guide

  • Endpoint configuration guide

  • Asset registry configuration guide

  • IBC asset display pattern

  • DEX integration pattern

  • Documentation for other Cosmos SDK chains

  • App store submission-ready build

Possible budget

Estimated request: $50,000 ATOM equivalent.

Budget would likely cover:

  • Mobile feature screen completion

  • WalletConnect v2 / Keplr-compatible wallet integration

  • ATOM and IBC asset flow integration

  • DEX pool and swap interface integration

  • Backend/API hardening for mobile use

  • UI/UX refinement

  • Testing and debugging

  • Open-source documentation

  • Release packaging and app store preparation

Possible timeline

Estimated delivery: 60 to 75 days from funding.

Possible milestone structure:

Milestone 1 — 30%
Public repository structure, architecture, navigation, chain configuration, and wallet foundation.

Milestone 2 — 40%
Working mobile test build with wallet connection, asset balances, ATOM/IBC display, ALYX/ATOM reference flow, and DEX screens.

Milestone 3 — 30%
Final open-source repository, documentation, ALYX reference implementation, and app store submission-ready build.

Accountability

I am open to feedback on the best accountability structure.

Options could include:

  • Direct recipient wallet with public reporting

  • Public multisig

  • Milestone-based release

  • Public GitHub progress tracking

  • Community review before final release

What is not included

This idea does not request funding for prediction markets.

This idea does not request funding for an NFT module.

This idea does not request funding for Delta Wolves migration.

This idea does not request funding for token liquidity.

The scope is only the mobile app template and ALYX reference implementation.

About me

I am SĂłcrates, sole founder and builder of ALYX. I also founded Delta Wolves, an Ethereum NFT community of 7,777 NFTs with around 1,432 holders. Delta Wolves is the founding user base and one of the first community groups onboarding into ALYX.

I built the ALYX chain architecture, DEX, TokenFactory surface, AI layer, IBC integration, Genesis Vault flow, and mobile scaffold.

Feedback requested

I would appreciate feedback on:

  • Whether this is useful to ATOM and the Cosmos Hub

  • Whether the mobile app template is a strong public-good deliverable

  • Whether the proposed budget range is reasonable

  • Whether the scope should be smaller or larger

  • Whether a multisig or milestone structure should be used

  • What documentation Cosmos builders would want included

  • What proof or technical references should be added before a formal draft

Thank you for reviewing this idea.

4

Hello !

To be fair I’m not really understanding what are the true benefit for ATOM other than “atom is live on ALYX” …

Same for the app purpose, feel like there is already 30 or so copy of this already

Having access to atom through IBC isn’t really a feature, just a basic function already live everywhere, IBC assets balance is already available on my wallet, DEX pool discovery for what tokens ? There is already many DEX, what will have your DEX that other DEX do not have ? Swap interface.. again not really a breaking feature, for a DEX. Mobile UX, great but for what and who?

I’m now very sceptical of any new chain with sub hundreds users and no real purpose or real revenue modele, seems like just creating a chain just for the sake of creating a chain, which usually end up very badly

1 Like
5

Thanks for the direct feedback , this is exactly what helps before a formal draft.

On the ATOM benefit question: you are right that IBC connectivity by itself is baseline Cosmos infrastructure, not a differentiator. The actual ATOM-side mechanism I should have led with is the Genesis Liquidity Vault.

ALYX just completed the first full ATOM Genesis Liquidity Vault execution cycle on mainnet. The flow is:

ATOM holders bridge ATOM from Cosmos Hub into ALYX, submit ATOM to the vault, receive an ALYX allocation, and the protocol matches ALYX from treasury. The submitted ATOM and matched ALYX are then added into Pool 9, and the resulting LP position is locked permanently on-chain.

So the point is not only “ATOM is supported.” The point is that ALYX now has a live mechanism that brings ATOM into an appchain economy as a settlement and liquidity asset, with protocol-matched liquidity and a permanent LP lock. That is the concrete ATOM utility surface I should have explained more clearly.

On existing mobile templates: I would genuinely like to see the 30 examples. What I have surveyed is either chain specific apps that are not designed to be forked, or generic Cosmos SDK starter kits without IBC denom resolution, TokenFactory asset discovery, DEX pool auto-discovery, Genesis Vault integration, and appchain specific liquidity flows. If something close already exists and is open-source, I should know about it before drafting a formal proposal. That feedback would be very useful.

On users and revenue: fair challenge, and I will not overstate the current user count. What I can show today is completed on-chain execution: 9 DEX pools, permanently locked liquidity, completed Genesis Vault cycles for both USDC and ATOM, 6 validators running consensus, and 268K indexed volume. The sustainability model is based on protocol fees from TokenFactory launches, pool creation, and swap activity. The mobile app would be the distribution layer that makes those fee surfaces and on-chain actions easier for users to access.

The broader point I take from your feedback is that the framing needs to center on what ATOM holders and Cosmos builders get from this existing in the ecosystem, not on what ALYX gets from building one.

That is a legitimate reframe, and I will apply it before considering any formal draft.

6

as far as i know, keplr mobile does not support connection to other native apps via Application ID yet.
Prove me wrong, but i guess you won’t be able to connect a react native App with keplr mobile this way.
I

1 Like
7

You’re right to call that out, and I should clarify the wallet flow more precisely.

Keplr Mobile does support WalletConnect v2, but the supported mobile flow is not the same as a seamless native deep link connection from a React Native app. The practical model is a companion WalletConnect flow: the app generates a WalletConnect session URI, displays it as a QR code, and the user scans it with Keplr Mobile to establish the session. Transaction signing then flows back through WalletConnect.