Merge Wallet Introduction

[2vxsfae]

Introducing Merge Wallet: Self-Custodial RBTC/RIF Mobile Wallet

Hi Rootstock collective!

I’ve built Merge Wallet - an open-source mobile wallet designed specifically for the Rootstock ecosystem. It’s functional and ready for community testing, contributions, and collaboration.

What is Merge Wallet?

A self-custodial RBTC mobile wallet that brings Bitcoin DeFi to your pocket:

• Cross-platform (iOS, Android, Web) via Capacitor 8

• BIP39/BIP44 standard key derivation (m/44’/60’/0’/0/0)

• AES-256-GCM encryption + biometric authentication

Current Features

Wallet creation and import via seed phrase

RBTC balance display and transactions

QR code send/receive functionality

Network switching (Mainnet/Testnet)

Contact management

PIN/biometric security

Multi-language support

Why This Matters

The demand question: Who actually needs this?

Currently, Rootstock users must rely on general-purpose wallets (MetaMask, Trust Wallet) that treat RSK as just another EVM chain. But Rootstock isn’t just another chain - it’s Bitcoin’s DeFi layer with unique characteristics:

• Bitcoin-native users need mobile access without compromising self-custody

• RSK-specific optimizations (gas estimation, network switching, RBTC handling)

• Mobile-first onboarding for mainstream Bitcoin adoption

• Reference implementation for other developers building on RSK

The ecosystem needs native mobile infrastructure. This wallet addresses that gap.

Try It Now

GitHub Repository: [Link - Always verify code before running]

**Please verify all code before running** - this is self-custodial software handling private keys.

The wallet handles core operations well and represents a solid foundation for community development.

Community Input Welcome

Key questions for the community:

- Is this something you would actually use?

- What RSK-specific features would add most value?

- Interest in beta testing and contributing to development?

Current limitations to address:

- No security audit yet

- Limited to basic wallet functions (no DeFi integrations)

- Single developer project (needs contributors)

Feedback & Issues:

- GitHub Issues: [Repository link] for bugs and feature requests

- Telegram Group: [Link] for discussions and feedback

Your honest feedback helps determine if this addresses a real need in the ecosystem.

[SEEDGov]

Hi @2vxsfae congrats for the project!

Mi honest initial opinion:

@2vxsfae

Try It Now

GitHub Repository: [Link - Always verify code before running]

Do you plan to list it on Google and/or Apple Playstore? Personally, for reasons of trust and security, I never download apps from links. It’s not that I don’t trust you, it’s just my general security approach, and I assume it’s the same for many people.

Especially given this situation:

@2vxsfae

Current limitations to address:

• No security audit yet

---

---

---

@2vxsfae

Key questions for the community:

• Is this something you would actually use?

Personally, I find multi-chain wallets more useful because I’m a heavy user of crypto across different chains and protocols. But I see how a maxi BTC and Rootostock user might find value in a chain dedicated wallet.

[2vxsfae]

Thanks for the honest feedback , really appreciate it.

On distribution: We have already submitted to the Google Play Store and are preparing the Apple App Store submission now. The goal is to get it into official channels as soon as possible so no one has to sideload or trust a random link.

On multi-chain vs. dedicated: Fair point. Most users have funds or are active on multiple chains, so that need is real. Our bet is Rootstock-first, not Rootstock-only. We want development to be community driven and organic, so only what people actually need gets added. Users can open issues for chains they want supported, and we will promptly add them based on that demand.

[Eren_DAOplomats]

Congratulations @2vxsfae on shipping this first iteration. We agree on security with @SEEDGov , we will not be fully confident to try / ask others to try with their funds. if you simply start adding other chains, you will be directly competing with giants like MetaMask and Trust Wallet, which dilutes your unique value proposition. Instead of adding chains, I highly suggest leaning into Rootstock’s composability by natively integrating ecosystem primitives (like Money On Chain, Tropykus, or Sovryn) directly into the wallet interface. That is what would make this a sticky with respect to rootstock ecosystem.

[SEEDGov]

@2vxsfae

On multi-chain vs. dedicated: Fair point. Most users have funds or are active on multiple chains, so that need is real. Our bet is Rootstock-first, not Rootstock-only. We want development to be community driven and organic, so only what people actually need gets added. Users can open issues for chains they want supported, and we will promptly add them based on that demand.

That makes sense. You can check out the Core App example; perhaps it can help you continue developing the product. It’s a wallet developed by Avalanche, so naturally it’s heavily focused on Avalanche’s features and capabilities (such as as improved gas fee efficiency, staking or earning through Avalanche protocols), but it’s also a multi-chain wallet that supports other blockchains.

[Curia]

Before jumping into features, I think the more important question is: who is this wallet actually built for?

Is the target a Bitcoin maxi, or someone who already uses MetaMask and other wallets? That distinction matters a lot, because trying to capture everyone usually means serving no one well.

If I put myself in the shoes of a regular DeFi user, I’d actually want multi-chain support. So the question shouldn’t be “if we add multi-chain, how do we compete with existing wallets?” Instead, it should be “What does Rootstock already offer that creates unique value for wallet users?” Whether that’s swapping, yield opportunities, RIF Relay removing the need to hold RBTC for gas, or other native ecosystem advantages, those are the things that can differentiate the experience.

I’d suggest staying multi-chain compatible while making Rootstock the place where the best experience lives. Lean into Rootstock’s existing strengths and surface them directly within the wallet. That’s what turns a generic wallet into something users have a clear reason to choose and continue using.

[2vxsfae]

Exciting news - Merge Wallet is now live and available for testing on Google Play Store!

You can download and test the app here: https://play.google.com/store/apps/details?id=com.mergewallet.app

This marks the first public release of Merge Wallet - an open-source, self-custodial mobile wallet built specifically for the Rootstock ecosystem.

Features:

- Native RBTC transaction capabilities

- Direct Money On Chain integration for minting/redeeming DOC and BPro

- Sovryn swap and lending capabilities built-in

We’ve made significant improvements based on early tester feedback:

- Enhanced security measures implemented

- Improved UI/UX for better accessibility

We’re particularly interested in your feedback on:

1. Onboarding experience - Was it clear and easy to follow?

2. Transaction flow - Any confusion or friction points?

3. Ecosystem integrations - Are the Money On Chain and Sovryn features discoverable and useful?

4. Overall usability - What would make you more likely to use this as your primary wallet?

Please try it out and share your honest thoughts - both positive and constructive criticism are invaluable as we continue to refine the experience. Your feedback will directly influence our next update cycle.

Looking forward to hearing from you all!

[SEEDGov]

What happened here? We find it interesting to continue this discussion with @2vxsfae

[2vxsfae]

@SEEDGov The Merge Wallet went live 2-3 weeks ago but I didn’t get a chance to introduce it to the community. Kindly have a look at https://play.google.com/store/apps/details?id=com.mergewallet.app .
Apart from basic transaction functionality I was able to plug into MOC and Sovryn protocols.

@Curia - spot on about target clarity. There isn’t a Rootstock maxi wallet on mobile right now. That’s the gap we’re filling.

What’s working:
• Native RBTC transactions
• Direct MOC integration (mint/redeem DOC, BPro)
• Sovryn swaps and lending
• Self-custodial with seed backup

The problem I’m trying to address: Rootstock users are stuck using MetaMask mobile or desktop browsers to access protocols. You can’t easily check your DOC position or do a Sovryn trade on the go.
My question: Is mobile access to these protocols actually needed? What other Rootstock integrations would make this essential for daily use?

[SEEDGov]

@2vxsfae

My question: Is mobile access to these protocols actually needed?

Let me share my perspective based on my own personal experience, which, of course, I would not extrapolate to all users.

I am generally not someone who performs these kinds of transactions from my mobile, I do it my computer. However, what I do find valuable in a wallet mobile app is the ability to easily monitor my wallet, including having a consolidated view of my overall portfolio and balances. For example, I find it particularly useful to be able to see not only the assets held directly in the wallet, but also funds deposited in lending protocols, so I can quickly understand my total balance and how much assets I have allocated across different products.

[DAOstar_gov]

Hello @2vxsfae , thanks for the updates and for continuing to push Merge Wallet forward with the MOC and Sovryn integrations and publishing onto the Google Play store, congratuations that is an accomplishment!

Regarding your question on whether mobile access is needed, as the ecosystem has moved to the new V3.2.2 Guidelines, the burden of proof for demand validation has been shifted to the builders (the question that you asked above). For consumer apps like Merge Wallet, a formal grant application will require concrete MVP usage metrics rather than qualitative community feedback.

To help the delegates properly evaluate the necessity and impact of this project, could you share some initial usage data? Specifically:

• What are the current active wallet counts or daily/monthly active users (DAU/MAU)?

• What are the transaction volumes processed through the app so far?

Additionally, please keep the V3.2.2 grant requirements for the cross-funding transparency and terminal milestone holdbacks in mind as you prepare your roadmap. Tks!

[Curia]

Since you’ve decided to focus on the Rootstock maxi user, I think what’s still missing is this:

@Curia

“What does Rootstock already offer that creates unique value for wallet users?”

On that front, I’d suggest prioritizing RIF Relay integration. Removing the need to hold RBTC for gas is a real onboarding differentiator that no generic wallet surfaces, and it would add meaningful depth to the unique value proposition you’re building toward.

@DAOstar_gov

To help the delegates properly evaluate the necessity and impact of this project, could you share some initial usage data? Specifically:

• What are the current active wallet counts or daily/monthly active users (DAU/MAU)?

• What are the transaction volumes processed through the app so far?

These are important questions, and I agree they’ll be central once a grant application is on the table. But the main purpose of this thread is asking delegates for product feedback, and the app only launched a few weeks ago, the numbers won’t tell much of a story yet. Still, it’s a good prompt for @2vxsfae to start setting up basic usage tracking now, so the demand evidence is ready when you apply for a grant.

[DAOstar_gov]

Totally agree with your comments, @Curia regarding usage data. Our intent in requesting that information is that we would like for the author to start thinking (and as you suggested) tracking it now, if their intent is to submit this project for a grant proposal. For us, without this data - if this project does move forward to a grant proposal - we would unable to verify ROI/RT ecosystem value. Tks!

[ChronoTrigger]

I think something worth looking at, is that the Rootstock native mobile wallet thesis has already been tested, and not once. Defiant was mobile first, self custodial and Rootstock native, and it ceased activities in July 2024. The RIF Wallet was the official native wallet with RIF Relay built in, and it has since been repositioned as a B2B framework for other builders rather than a consumer product it ships itself. Beexo is the one still standing, and it was the first wallet to integrate RIF Relay, so the gasless angle is already shipped rather than open ground.

That reframes the demand question in a more useful way. The point is not whether a Rootstock mobile wallet can be built, it clearly can. It is why this one reaches and holds users that two better resourced attempts could not. Early usage on a three week old app will not answer that, but the comparison to what Defiant and the RIF Wallet did and did not reach goes much further, and it is evidence you can gather without waiting for your own numbers to mature.

None of this is a reason to stop, @2vxsfae, it is the question to answer before a grant proposal. It’d be great if you can name one or two things a Rootstock user cannot do well on Beexo today and can show Merge doing them, with the MOC and Sovryn actions being the obvious candidates. If an angle can be found here, this can go a long way into validating the business case, and an eventual grant proposal.