RallyProtocol, the mobile layer for Web3, is excited to announce the launch of embedded wallets and gasless transactions on Base.

Building on our success on Polygon—where we helped developers create over a million embedded wallets for mobile users, enabled over 70% of gasless transactions, and integrated with SocialFi leader Orb: Social Network on Lens—we're now ready to empower the next generation of builders.

Building on Base

Base has become the go-to blockchain for developers building real consumer applications, thanks to its established and rapidly growing ecosystem of apps and engaged onchain users. Furthermore, the high volume of stablecoin transactions on Base indicates that apps are creating genuine engagement and utility for the average consumer.

Base makes it easier than ever to bring users onchain, and now, with RallyProtocol’s open and permissionless onchain mobile toolkit, we’re excited to amplify this vision by empowering developers to create onchain mobile apps quickly, simply, and with full sovereignty.

RallyProtocol’s Vision for Base

Our core principles focus on giving developers full control and sovereignty over their apps, users, and onchain experiences. While embedded wallet services like Wallet-as-a-Service (WaaS) and Account Abstraction (AA) are valuable for simplifying onchain onboarding, we believe there are simpler, more developer-friendly solutions that don’t rely on smart contracts, APIs, or third-party subscriptions.

Warpcast's onboarding experience, with its smooth embedded wallet creation that doesn’t require integration with a third-party wallet service, exemplifies what every developer should have access to. Our vision for Base is to provide permissionless and open tools that empower all developers to build onchain mobile apps securely, quickly, and autonomously.

Simplifying Onchain Mobile

RallyProtocol is designed for mobile developers who want to bring users onchain quickly, easily, and without the reliance on third-party services. Here are the features RallyProtocol provides:

Embedded wallets

Create self-custodied wallets embedded on users’ devices, encrypted by the device’s secure enclave. Developers have full sovereignty, meaning wallet facilitation belongs exclusively to them. They maintain complete ownership and control over wallets, social graphs, and data, without any third-party intermediaries.

Gasless transactions

Streamline user onchain experiences by completely eliminating gas fees for users without ever needing smart contract wallets. Build your own stack using our open-source code, or try our stack and let us handle the heavy lifting.

Permissionless and Open Tools

RallyProtocol’s vision is to bring mobile users onchain by providing developers with tools that are simple, non-prescriptive, and aligned with blockchain principles:

• Permissionless & Open: Start creating embedded wallets without needing a developer account or requiring your users to log in with socials.

• Decentralized: Our stack is built with core onchain features that anyone can create and use.

• Self-custodial and secure: Keys are always stored directly on the user’s native device and encrypted by the hardware’s secure enclave.

• Full sovereignty: Full control is given to the developers to decide their UX. No need for permissions or services to facilitate your relationship with your users.

• Censorship-resistant: User wallets can never be censored, revoked, or lost by a third party because they are fully stored only on the user’s device.

About RallyProtocol

RallyProtocol is an open and permissionless onchain mobile toolkit that features embedded wallets and gasless transactions. Our mission is to enable developers to create seamless, end-to-end onchain experiences for native mobile apps while ensuring self-custody, security, and full developer sovereignty. Whether you're building an iOS or Android app in Flutter, Unity, React Native, Expo, Swift, or Kotlin, our tools empower developers to create better onchain mobile experiences quickly and easily.

Want to learn more? Dive into our developer documentation here.