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

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…

Excerpt (1192 of 6786 characters). Read the whole post on the forum ↗

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 Alyx: 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. Alyx: 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 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…

Excerpt (1199 of 1319 characters). Read the whole post on the forum ↗

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…

Excerpt (1197 of 2333 characters). Read the whole post on the forum ↗

Alyx:

• WalletConnect v2 / Keplr-compatible wallet integration

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

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.