Bringing embedded wallets for mobile now with React Native SDK compatible with Expo. Create wallets, signatures and payments.

React Native SDK for cross-platform embedded wallet development

React Native support for embedded wallets


We’re building a framework to consolidate liquidity across every chain. Our **Chain Abstraction** solution allows users to spend a single, unified balance instantly, regardless of which blockchain the application is built on.

## What is Chain Abstraction?

Chain abstraction is a technology that hides the complexity of multi-chain interactions from the user. Instead of manually bridging assets or holding multiple native tokens for gas, users interact with a single "abstracted" balance. Behind the scenes, the system handles cross-chain proofs and time-locked vaults to ensure transactions are executed securely and instantly. At Openfort, we enable ecosystems to act as their own liquidity providers, sharing the value usually taken by external "solvers" back with their users.


A significant step towards unifying liquidity across the space are cross-chain interactions. By leveraging **time-locked vaults** and **onchain proofs**, our ecosystems can now provide users with a unified balance instantly accessible across all apps within their ecosystem.

This first implementation builds on:
- [MagicSpend++](https://ethresear.ch/t/magicspend-spend-now-debit-later/19678/9) with **time-locked vaults** to simplify cross-chain operations while ensuring security and speed.
Vaults can be yield-bearing. Users deposit once to enable chain abstraction and put their money to work. Different yield strategies will come.

- [Polymer's Prove API](https://docs.polymerlabs.org/docs/build/start), simplifying contract development by replacing manual cross-chain messaging with a more intuitive and native approach of **on-chain proofs**.

![chain-cmd.jpg](/images/blog/chain_cmd_a5719f7cb5.jpg)

## Why this matters
Chain abstraction is an ambitious space with many approaches. Most rely on third parties (fillers/solvers) that will compete to front liquidity on destination chains in exchange for fees. At Openfort, we grant the ecosystem the power to become an LP for its users and only rely on external liquidity when required.

With our setup, ecosystems can deploy tailor-made 4337 chain abstraction infrastructure. They become Liquidity Providers (LPs) for their users, sharing with them the value that would otherwise have been captured by fillers/solvers.

- **Intents**: Allow users to express what they want to do, regardless of the underlying blockchain.
- **Time-locked vaults**: Assets locked in the vault serve as a guarantee for Payamasters.
- **Onchain proving**: Ecosystem can’t be repaid without cross-chain execution proof —zero trust assumption. The InvoiceManager contract tracks onchain repaid invoices to forbid double repayment.

This means your users can securely:
- Buy assets on one chain using liquidity from another
- Deposit any ERC20s on any chain to increase their chain abstracted balance
- Interact with apps across blockchains without friction

## How it works

![mermaid.png](/images/blog/Screenshot_2024_12_30_at_14_47_19_7704205675.png)

At the heart of our system are:
- **Time-locked vaults**: Securely lock user funds, ensuring they’re only used as intended. It can be yield-bearing.
- **Chain abstraction paymasters**: 4337 compatible paymasters which handle gas and destination chain transaction costs. Ecosystems own them. They’re approving the required ERC20s after validating the Openfort backend signature.

In practice, an ecosystem can deploy its onchain infrastructure, acting as a liquidity provider for its users. Funds locked on the origin chain are released only after transaction proof is obtained from the destination chain.

This design ensures:
- **Frictionless user experience**: Transactions feel as fast as same-chain operations.
- **Non-custodial security**: Openfort Backend authorizes transactions but cannot spend funds.
- **Trust-minimized execution**: Users can withdraw all their chain abstracted balance after a configurable lock period. Ecosystems can rage-quit (i.e., instantly withdraw all liquidity from their paymasters). Neither Openfort nor the Ecosystem can get refunded without the userOp execution proof verified on the source chain.

This approach makes interop simple, fast, and secure. Ecosystems can share value with users instead of solvers while ensuring liquidity is always available where needed.

## What's next?
For ecosystem: automatic liquidity rebalancing between chains with Openfort custom alerts when a Paymaster balance is lower than a programmable threshold.

For users: Put your money at work. [Our chain abstraction demo](https://github.com/openfort-xyz/openfort-chain-abstraction) is built around basic time-locked vaults, but we will deploy yield-bearing vaults with different DeFi protocols.


Bridging ecosystems to create smooth experiences for their end users across any chain.

Chain abstraction framework enabling unified cross-chain transactions

Chain Abstraction Framework with ZK Proofs


You can now onboard users instantly without requiring a login. Our new **Guest Accounts** feature allows players to jump into your app and start building their digital inventory immediately, with the option to link a permanent identity later.

## What is an Openfort Guest Account?

A Guest Account is a temporary, local-first wallet that is created automatically when a user opens your app. It uses the device's local storage to persist a player ID and an embedded wallet, allowing the user to return and continue their progress without needing to authenticate. When the user is ready, they can "link" their guest account to a social login or email, preserving all their assets and history as they transition to a full account.

That’s why we’re excited to introduce **[Guest Accounts](https://www.openfort.io/docs/products/embedded-wallet/javascript/auth/guest)**, a seamless way for users to "continue as a guest" and upgrade to full accounts later. This feature is ideal for gaming and shopping apps, where reducing friction is key to keeping users engaged.

## How Guest Accounts work
1. **Instant engagement**
   When users onboard via guest accounts, they can interact with your app right away. Behind the scenes, Openfort creates a **persistent player ID** and a fully-functional embedded wallet tied to the user’s local storage.

2. **No login friction**
   Guest accounts allow users to return to your app on the same device and access their account and wallet without needing to log in. This makes re-engagement effortless.

3. **Easy account upgrades**
   Guest accounts are fully upgradeable to logged-in accounts. By simply calling the `link()` function, users can transition seamlessly.

## Streamlined samples: Focused and maintained
We’ve also simplified our sample projects to better support your development journey.

After listening to community feedback, we realized that too many sample projects could be overwhelming. To address this, we’ve curated the most useful and maintainable examples to make it easier for developers to get started.

Our newest addition? **Rapid Fire**, a streamlined example that showcases the power of Openfort’s ecosystem. It’s designed to help you implement key features quickly and efficiently, so you can focus on building.

![rapidfire.png](/images/blog/rapidfire_d14709acdf.png)

## What's next
Guest Accounts and our updated sample library are just the latest steps in making wallet integration effortless and user-friendly. We’re committed to continuing to simplify and enhance your development experience.

Check out the docs and explore the [new samples today](https://github.com/openfort-xyz/samples)!

## Related reading

- [React Native SDK for embedded wallets](/blog/react-native-sdk) -- use guest accounts in your mobile app with the React Native SDK
- [Embedded wallets explained](/blog/embedded-wallet-explained) -- learn how the wallets created behind the scenes for guest users actually work
- [Openfort wallets: build vs. buy](/blog/openfort-wallets-build-vs-buy) -- see why integrating a managed wallet solution beats building from scratch
- [How to build Telegram Mini-Apps with React](/blog/telegram-mini-apps) -- guest accounts pair well with Telegram Mini-Apps for zero-friction onboarding
- [Session keys for smooth UX](/blog/technical-dive-session-keys) -- combine guest accounts with session keys to let users transact without signing prompts


You no longer need to ask users to authenticate to have a wallet pregenerated. Let users dive into your app instantly, no login required.   

Guest accounts for instant login-free onboarding with pre-generated wallets

Onboard new users with Guest accounts

- [What is the Openfort React Native SDK?](#what-is-the-openfort-react-native-sdk)
- [What's included in this release?](#whats-included-in-this-release)
- [What you can do with the React Native SDK](#what-you-can-do-with-the-react-native-sdk)
- [What's next?](#whats-next)
- [Related reading](#related-reading)

What you can do with the React Native SDK

 for embedded wallets is now in alpha. As mobile leads the way for onchain app adoption, this SDK gives developers the tools to build cross-platform wallet experiences that feel native and fast.

Our **React Native SDK** for embedded wallets is now in alpha. As mobile leads the way for onchain app adoption, this SDK gives developers the tools to build cross-platform wallet experiences that feel native and fast.

[What is the Openfort React Native SDK?](#what-is-the-openfort-react-native-sdk)

 is a development kit that brings embedded, non-custodial wallet features to mobile apps built with React Native and Expo. It allows developers to provision "invisible" wallets, handle onchain signatures, and sync user state across web and mobile platforms. By removing the need for browser extensions or separate wallet apps, it enables a frictionless checkout and gameplay experience on mobile devices.

The Openfort [React Native SDK](https://www.openfort.io/docs/products/embedded-wallet/react-native) is a development kit that brings embedded, non-custodial wallet features to mobile apps built with React Native and Expo. It allows developers to provision "invisible" wallets, handle onchain signatures, and sync user state across web and mobile platforms. By removing the need for browser extensions or separate wallet apps, it enables a frictionless checkout and gameplay experience on mobile devices.

[What's included in this release?](#whats-included-in-this-release)

React Native compatibility with the Ecosystem SDK

Easily integrate the features of the Ecosystem SDK into your React Native apps, allowing for smooth wallet integration and management. Integrate a cross-app wallet with your 

**React Native compatibility with the Ecosystem SDK**
Easily integrate the features of the Ecosystem SDK into your React Native apps, allowing for smooth wallet integration and management. Integrate a cross-app wallet with your [react native app](https://www.openfort.io/docs/products/cross-app-wallet/usage/react-native).

With full compatibility with Expo, developers can enjoy the benefits of rapid development cycles while delivering native-like experiences.

**Expo support**
With full compatibility with Expo, developers can enjoy the benefits of rapid development cycles while delivering native-like experiences.

[What you can do with the React Native SDK](#what-you-can-do-with-the-react-native-sdk)

![react-native.png](/images/blog/react_native_055bbfbd88.png)

This alpha version enables developers to:

 seamlessly across web and mobile platforms

**Authenticate users** seamlessly across web and mobile platforms

Provision embedded self-custodial wallets

**Provision embedded self-custodial wallets** with ease

**Enable signatures and transactions** for a streamlined user experience

, so users can switch between web and mobile without losing progress.

And just like our other SDKs, **state syncs across clients**, so users can switch between web and mobile without losing progress.

This is just the beginning. As we gather feedback from early testers, we'll continue to improve and expand the React Native SDK. Expect additional functionality and deeper integrations in future updates.

 -- combine the React Native SDK with guest accounts to let users start without login friction

[Onboard users with guest accounts](/blog/guest-accounts) -- combine the React Native SDK with guest accounts to let users start without login friction

 -- understand the architecture behind the self-custodial wallets provisioned by this SDK

[Embedded wallets explained](/blog/embedded-wallet-explained) -- understand the architecture behind the self-custodial wallets provisioned by this SDK

 -- why using a managed wallet SDK saves months of engineering effort

[Openfort wallets: build vs. buy](/blog/openfort-wallets-build-vs-buy) -- why using a managed wallet SDK saves months of engineering effort

 -- learn how session keys enable gasless, frictionless transactions in mobile apps

[Session keys for smooth UX](/blog/technical-dive-session-keys) -- learn how session keys enable gasless, frictionless transactions in mobile apps

Introducing global wallets with the Ecosystem SDK

 -- see how the Ecosystem SDK pairs with React Native for cross-app wallet experiences

[Introducing global wallets with the Ecosystem SDK](/blog/gaming-ecosystems) -- see how the Ecosystem SDK pairs with React Native for cross-app wallet experiences

React Native support for embedded wallets

In this article

Let your business run on stablecoins

In this article

Let your business run on stablecoins

What is the Openfort React Native SDK?

What's included in this release?

What you can do with the React Native SDK

What's next?

Keep Reading

Onboard new users with Guest accounts

Chain Abstraction Framework with ZK Proofs

Try Openfort Free