Today, we're excited to unveil [Openfort Kit](http://kit.openfort.xyz/) - your shortcut to creating polished wallet experiences that convert curious visitors into engaged users.

Build web3-native authentication flows with beautiful UI components in minutes instead of weeks. Start creating now to capture mainstream audiences faster.

##Why are we doing this?
When we first simplified wallet integrations, our goal was to help developers ship secure authentication in hours rather than days. That's why we build [Openfort JS](https://www.openfort.xyz/docs/guides/getting-started). To help any developer customize as much as they wanted the user experience. Great number of teams benefited from such granularity and build [incredible products](https://www.openfort.xyz/blog/categories/customer).

**But we're not done.**  

What if you could deploy production-ready flows in minutes instead of hours?  
What if every team member - not just engineers - could collaborate on crypto onboarding?  
That's why we built [Openfort Kit](https://www.openfort.xyz/docs/guides/react).

## What problem are we solving?
Every crypto team faces the same dilemma:  

1. **Design Debt** - Most wallet UIs feel either overly technical or visually disjointed from brand identities.  
2. **Time Sinks** - Teams waste weeks rebuilding auth flows instead of focusing on core products.  
3. **Conversion Leaks** - Clunky experiences scare away 79% of non-crypto native users. 

The result? Projects either cater exclusively to crypto veterans or struggle through endless iteration cycles trying to appeal to mainstream audiences.

Wallet experiences should be intuitive, brand-aligned, and conversion-optimized - regardless of a team's blockchain expertise.

## Why now? 
Three seismic shifts make this possible:  

1. **Wallet maturity** - Standards like ERC-4337, 7702 (and more) and tools like ConnectKit enable flexible authentication flows. Project can now enjoy full power of smart wallets with the convenience of having React hooks.  
2. **Consumer expectations** - Users now demand web2-level polish for web3 experiences. More crafted experiences can be build across device and platforms. 
3. **Conversion science** - We've analyzed 1M+ onboarding attempts to identify proven UX patterns. Faster and secured onboardings enable increse the rate of conversion.

We've baked these insights into pre-built components that:  
- Match your existing design system.  
- Support multiple auth methods (social, embedded, traditional).  
- Include linking and unlinking of identities. 

Just as v0 and Vercel changed frontend development, we're reimagining how teams approach web3 UX. This is just the end of a journey and we'll see any consumer facing software have a wallet integrated. Build with taste, build with Openfort kit.

openfort-kit.png

Introducing Openfort kit

Automating blockchain transactions, managing digital assets programmatically, and crafting seamless user experiences require robust infrastructure. At Openfort, we’ve built **[backend wallets](https://www.openfort.xyz/docs/guides/server/dev)** to empower developers to execute on-chain actions at scale while maintaining security, flexibility, and enterprise-grade performance. Let’s explore how they work and why they matter.  

## What are backend wallets?
Backend wallets are developer-controlled accounts that run on your server, enabling automated blockchain interactions without manual user input. Unlike traditional user wallets, they:  
- Operate programmatically via APIs.  
- Support gasless transactions via ERC-2771 forwarders or ERC-4337 paymasters.  
- Manage assets at scale for use cases like treasury systems, NFT drops, or cross-chain operations.  


### Why Openfort’s backend wallets?
Our infrastructure combines **EOA flexibility** and **ERC-4337 smart account capabilities** to address critical Web3 challenges:  

1. **Automated Transactions**: Execute batch mints, disbursements, or trades without user signatures.  
2. **Gas Abstraction**: Sponsor gas fees via custom forwarders or Openfort’s paymaster.  
3. **Enterprise Security**: Custodial wallets with Google Cloud TEE-based key management.  
4. **EVM Compatibility**: Seamlessly deploy on Ethereum, Polygon, Base, and other EVM chains.  

![backend.png](https://strapi-oube.onrender.com/uploads/backend_f8a8eff4b8.png)


## Key features & architecture
### Secure key management
- **Google Cloud TEE backend**: Private keys are secured in Trusted Execution Environments (TEEs), ensuring cryptographic operations remain isolated from external threats.  
- **Custody flexibility**: Choose between custodial EOAs (ideal for treasury management) or non-custodial options with verified ownership.  

### Cross-chain scalability 
While currently focused on **EVM chains** (Ethereum, Polygon, Base), Openfort’s infrastructure is designed for future expansion to non-EVM networks like Solana and Bitcoin.  

### Policy engine & transaction controls  
- **Granular rules**: Enforce allowlists, transaction limits, or contract-specific interactions.  
- **Idempotent execution**: Prevent duplicate transactions with built-in deduplication.  
- **State sync**: Monitor transaction statuses in real time via webhooks or Websockets.  

### High performance infrastructure
- **Below 300ms signature times**: Optimized cryptographic libraries ensure low-latency operations.  
- **Four 9s uptime**: Globally distributed nodes guarantee reliability for mission-critical applications.  


## Key use cases
### 1. **Treasury management**  
- Automate payroll in stablecoins.  
- Manage protocol-owned liquidity pools.  
- Distribute rewards or refunds programmatically.  

### 2. NFT operations at scale
- Batch-mint NFTs for gaming items or collectibles.  
- Update dynamic metadata (e.g., evolving in-game assets).  
- Airdrop assets to user wallets post-purchase.  

### 3. Shared & automated wallets
- **Collaborative Control**: Configure multi-party approval (m-of-n) for DAO treasuries or institutional wallets.  
- **AI-Driven Agents**: Program wallets to execute stop-loss trades, recurring payments, or DeFi strategies.  

### 4. Cross-Border Payment Systems
- Manage millions of wallets for users or machines.  
- Automate stablecoin disbursements with gas sponsorship.  


## Getting started in 3 steps

### 1. Create a backend wallet
Via Dashboard:  
1. Navigate to [Backend Wallets](https://dashboard.openfort.xyz/).  
2. Click **Add Account** and name your wallet (e.g., “Minting Account”).  

<div align="center">  
  <img  
    alt="Openfort Backend Wallet Dashboard"  
    src="https://blog-cms.openfort.xyz/uploads/dev_account_dashboard_f73e699b8b.png"  
    width="80%"  
  />  
</div>  

Via [API](https://www.openfort.xyz/docs/guides/server/quickstarts/sdk):  
```typescript  
const Openfort = require('@openfort/openfort-node').default;  
const openfort = new Openfort(process.env.OPENFORT_SECRET_KEY!);  

// Create custodial EOA  
const account = await openfort.settings.createDeveloperAccount({  
  name: 'Escrow Account',  
});  
```  

### 2. Configure gas policies
- **For EOA wallets**:  
  - Deposit native tokens for gas.  
  - Use Openfort’s default ERC-2771 forwarder or deploy your own.  

- **For smart wallets**:  
  - Set paymaster rules (e.g., sponsor gas for specific users).  

### 3. Execute transactions
```typescript  
// Gasless NFT mint using a forwarder  
const tx = await openfort.transactions.create({  
  chainId: 80001, // Polygon Mumbai  
  account: account.id,  
  to: NFT_CONTRACT_ADDRESS,  
  data: mintCalldata,  
  policy: "GASLESS_FORWARDER"  
});  
```  

### Advanced capabilities
**Automated Gas Sponsorship**  
- Never manually top up wallets. Use Openfort’s paymaster to dynamically fund transactions.  
- Define policies to sponsor gas for specific users, contracts, or transaction types.  

**Flexible custody models**  
- **Custodial EOAs**: Retain full control for internal operations (e.g., treasury accounts).  
- **Non-Custodial Options**: Verify ownership via signed messages for user-assigned wallets.  

**Multi-chain event listeners**  
- [Register webhooks](https://www.openfort.xyz/docs/guides/server/webhooks) to track onchain events (e.g., incoming payments, contract interactions).  
- Sync wallet states across frontend and backend systems in real time.  


### Why developers choose Openfort
- **Unified APIs**: Manage EOA and ERC-4337 wallets with one SDK.  
- **Zero Infrastructure Overhead**: No need to self-host relayers or signers.  
- **Multi-Chain Ready**: Currently EVM-focused, with seamless chain switching.  


### Start building today
1. **[Sign up](https://dashboard.openfort.xyz)** for a free account.  
2. Explore our **[guides](https://docs.openfort.xyz/guides/server/dev)** on escrow systems and gasless minting.  
3. Need help? Join our **[Discord](https://discord.gg/openfort)** for developer support.  


Empowers applications to execute transactions seamlessly, manage digital assets at scale, and deliver user-centric experiences

blog-backend.png

Building scalable applications with backend wallets

Last Friday marked the end of [Openfort Launch week 1](https://www.openfort.xyz/launch-week), our launch week focused on empowering developers to build better ecosystem wallets and cross-chain experiences.

In the last five days, we shipped five major features and improvements.

Here's a quick recap of what we launched:

[Day 1: Ecosystem customization tool](##Day-1-Ecosystem-customization-tool)
[Day 2: Ecosystem SDK 2.0](##Day-2-Ecosystem-SDK-2.0)
[Day 3: Guest accounts and new samples](##Day-3-Guest-accounts-and-new-samples)
[Day 4: React Native SDK](##Day-4-React-Native-SDK)
[Day 5: Chain abstraction framework](##Day-5-Chain-abstraction-framework)
[Extra: ZkSync contract audit](##Extra-release-ZkSync-audit)

If you prefer watching instead of reading, **check out [this video](https://youtu.be/dPZB_6LvBwA)**

## Day 1: Ecosystem Customization Tool

On Monday, we introduced a new tool designed to make building ecosystem wallets more accessible to everyone. The Ecosystem Customization Tool simplifies the process of creating tailored wallet experiences through an intuitive interface.

Key features include:
- Pre-built theme selection
- Custom color palette configuration

[Read announcement](https://www.openfort.xyz/blog/ecosystem-customization-tool)

## Day 2: Ecosystem SDK 2.0

Tuesday brought a major upgrade to our SDK, focusing on developer experience and enhanced functionality. Ecosystem SDK 2.0 introduces several groundbreaking improvements:

- Removed API key requirements for simpler integration
- Added ERC5792 standard compatibility
- Implemented encrypted communication via Mobile Wallet Protocol (MWP)
- Streamlined package management

[Read announcement](https://www.openfort.xyz/blog/announcing-ecosystem-wallet-2)

## Day 3: Guest accounts and new samples

On Wednesday, we unveiled Guest Accounts, a feature designed to reduce friction in user onboarding. This powerful addition allows users to:
- Start using apps immediately without login requirements
- Maintain persistent access through local storage
- Seamlessly upgrade to full accounts when ready

[Read announcement](https://www.openfort.xyz/blog/guest-accounts)

## Day 4: React Native SDK

Thursday saw the alpha release of our React Native SDK, bringing Openfort's powerful wallet functionality to mobile development. The release includes:
- Full React Native compatibility with ecosystem SDK and embedded wallet
- Comprehensive Expo support
- Cross-platform authentication
- State synchronization across web and mobile

[Read announcement](https://www.openfort.xyz/blog/react-native-sdk)

## Day 5: Chain Abstraction Framework

We concluded the week with our most ambitious release yet: the Chain Abstraction framework. This revolutionary system enables:
- Cross-chain interactions using time-locked vaults
- Integration with MagicSpend++ and Polymer's Prove API
- Ecosystem-owned liquidity provision
- Trust-minimized execution with onchain proving

[Read announcement](https://www.openfort.xyz/blog/chain-abstraction)

## Extra release: ZkSync audit
A final suprise. We announced the ZkSync smart contract audit as well as the overall improvements in our infrastructure enabling us to speed the acount creation and processing for our clients.

[Read announcement](https://www.openfort.xyz/blog/extra-launch-1)

## Looking Forward

This launch week represents a significant step forward in our mission to make wallet development and cross-chain interactions more accessible and efficient. From simplifying wallet creation to enabling seamless cross-chain operations, each feature was designed with developer experience and user needs in mind.

See you in the next one!

Everything we launched during the first launch week.



wrapup.png

Openfort Launch Week 1: Wrap up


1/ **Launching Full Support for zkSync and Elastic Chains!**  
Our smart contract accounts are now **fully audited** and available on [zkSync and Elastic Chains](https://github.com/openfort-xyz/openfort-zksync-contracts). This update brings all the features, security, and seamless integration that Openfort is known for to even more ecosystems. Whether you're building on zkSync or an Elastic Chain, Openfort is here to supercharge your projects.

2/ **React Native Sample for Ecosystem Wallets**  
We’re thrilled to announce the release of our **[React Native Sample](https://github.com/openfort-xyz/ecosystem-wallet-expo-example)** for ecosystem wallets!   
Powered by the **Mobile Wallet Protocol**, this makes mobile-native interactions effortless and intuitive. Wallet interactions can now happen entirely on mobile, opening the door to smooth, frictionless onchain experiences for your users. Check [our docs to get started](https://www.openfort.xyz/docs/guides/ecosystem/react-native-integration).

Stay tuned—additional library support is on the way!

3/ **Under-the-Hood Improvements: APIs & Scalability**  
While you might not see these changes directly, you'll *definitely* feel them:  
✨ **API Endpoints** are now **1.5x faster**  
✨ We’ve increased chain stack scalability to handle over **5x the load**  
This means your apps can handle more users and higher transaction volumes without skipping a beat.

These updates reflect our commitment to empowering developers and scaling Web3. We can’t wait to see what you build with zkSync, Elastic Chains, and mobile ecosystem wallets. Let’s shape the future of onchain experiences—together. 


We're bringing audited contracts on ZkSync, React native support for ecosystem wallets and performance improvements.

extra.png

Extra Releases: Audits and samples

Ecosystems serve as parent entities for groups of apps operating across different blockchains. Openfort [ecosystem wallets](https://www.openfort.xyz/docs/guides/ecosystem) enable seamless interoperability between applications, allowing ecosystems to design their ideal, unified wallet experience. The next evolution is to consolidate user liquidity across apps, providing a single, unified balance that is instantly spendable across the ecosystem.

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/learn/intro), simplifying contract development by replacing manual cross-chain messaging with a more intuitive and native approach of **on-chain proofs**.

![chain-cmd.jpg](https://strapi-oube.onrender.com/uploads/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](https://strapi-oube.onrender.com/uploads/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 seamless liquidity for your users.  

chain-abstraction.png

Chain Abstraction framework for ecosystems

We’re thrilled to announce our [React Native SDK](https://www.openfort.xyz/docs/guides/javascript/react-native)! As mobile continues to play a pivotal role in the adoption of onchain apps, this SDK bridges the gap for developers building cross-platform experiences.  

Already being tested with a few apps, this release is designed to empower React Native developers with robust tools to integrate wallet functionality effortlessly.  

### What’s included in this release?  
1. **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.  

2. **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  

![react-native.png](https://strapi-oube.onrender.com/uploads/react_native_055bbfbd88.png)

This alpha version enables developers to:  

- **Authenticate users** seamlessly across web and mobile platforms  
- **Provision embedded self-custodial wallets** with ease  
- **Enable signatures and transactions** for a streamlined user experience  

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

### Already live in alpha 🚧  
This SDK is currently being tested with select apps, and the feedback has been promising. Developers are already exploring new ways to create smooth mobile onchain experiences for their users.  

### What’s next?  
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.  

Bringing seamless onchain functionality to mobile apps.  

React-native.png

Announcing React Native SDK

### Introducing Guest Accounts ✨  

In consumer apps, your funnel is everything. Sometimes, the best way to engage users is to let them start exploring immediately—before requiring them to log in.  

That’s why we’re excited to introduce **[Guest Accounts](https://www.openfort.xyz/docs/guides/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](https://strapi-oube.onrender.com/uploads/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)!  

Let users dive into your app instantly, no login required.  


guest-accounts.png

Guest accounts and new samples

A streamlined, upgraded way to build better wallets for your ecosystem.  

We’re excited to unveil **Ecosystem SDK 2.0**, a major upgrade designed to make wallet development faster, easier, and more powerful.  

With this release, we’ve focused on addressing developer feedback and improving the overall experience of building ecosystem wallets. Whether you’re iterating on your existing wallet or starting from scratch, SDK 2.0 is built to empower developers to create better wallets with fewer hurdles.  

### What’s new in Ecosystem SDK 2.0  
This upgrade introduces several key improvements:  

1. **No API keys required**  
   Streamline your development process by removing the need for API keys, making integration simpler than ever.  
   
![meme-keys.jpg](https://strapi-oube.onrender.com/uploads/meme_keys_6574c230cf.jpg)

2. **Compatibility with the [ERC5792 standard](https://www.eip5792.xyz/)**  
   Ensure your wallet is aligned with the latest standards, enhancing interoperability and consistency across platforms.  

3. **Encrypted communication protocol**  
   Our rebuilt stack now includes encrypted communication. At the core of this experience is [Mobile Wallet Protocol (MWP)](https://mobilewalletprotocol.github.io/wallet-mobile-sdk/docs/spec/), which allows external applications to securely interface with a wallet.  

4. **Improved the end-user experience.**  
   Say goodbye to frustrating issues with network switching and added further functionality for developers to choose the onboarding configuration—SDK 2.0 fixes these common pain points for a smoother user experience.  

### How we got here  
The original Ecosystem SDK gave developers the tools to customize and deploy wallets, but we knew there was room for improvement. With **SDK 2.0**, we’ve addressed the most common feedback from our developer community and introduced features that make the development experience more intuitive and efficient.  

### What’s next  
SDK 2.0 is a significant step forward, but we’re not stopping here. We’re already working on more updates to bring additional functionality and ensure your wallets stay ahead of the curve.  

Get started with [Ecosystem SDK 2.0](https://www.openfort.xyz/docs/guides/ecosystem) today and take your wallet development to the next level.  

Launching an improved version of the ecosystem SDK. Now without the need to include api keys and much more reliable and secure communication protocol

ecosystem-2.png

Announcing Ecosystem Wallet 2.0

### Introducing the Ecosystem Customization Tool  
Create your own ecosystem wallet with full control, from themes to setup.  

**Building an ecosystem wallet just got easier.**

With the new **Ecosystem Customization Tool**, developers can design and deploy their own wallets with ease. From selecting themes to customizing colors and downloading packages, this tool simplifies the entire process of building a tailored wallet experience.  

### How we got here  
When we launched **Ecosystem V1** two months ago, we prioritized giving developers the flexibility to customize essential parts of their wallet stack. This approach resonated with technical users, enabling them to fine-tune their wallets with precision.  

However, we noticed an opportunity to make this process more accessible for everyone, regardless of technical expertise. That’s why we created the **Ecosystem Customization Tool**: to empower all users—developers and non-developers alike—to shape their wallet experience intuitively.  

### How it works  

![customize-ecosystem.png](https://strapi-oube.onrender.com/uploads/customize_ecosystem_299be739d8.png)

The Ecosystem Customization Tool is designed to be straightforward and user-friendly. Here’s what you can do:  

1. **Choose a theme:** Select from a range of prebuilt themes or start fresh with a blank canvas.  
2. **Customize colors:** Define a color palette that matches your brand or personal preferences.  
3. **Download packages with ease:** Streamline the setup process by managing dependencies through an intuitive downloader.  

With these features, creating a wallet that reflects your style and functionality is just a few clicks away.  

### What’s next  
This is just the beginning. As we continue to improve the **Ecosystem Customization Tool**, we aim to add even more options for design and functionality, ensuring you have everything needed to craft a seamless wallet experience.  

Start building your [customized ecosystem wallet today](https://build.openfort.xyz).

Enabling an even easier way to customize your ecosystem wallet directly from your browser

LW-ecosystem.png

Ecosystem Customization Tool

**"Let a Thousand Ecosystems Flourish"**

## Our Journey: From Embedded Wallets to Unified Gaming Ecosystems

Earlier this year, we launched [Identity](https://www.openfort.xyz/blog/embedded-smart-accounts), introducing a revolutionary embedded wallet solution for Web3 games. This enabled developers to create self-custodial wallets natively across platforms and devices, transforming the way players onboard and interact with onchain assets. Our solution simplified the integration of blockchain wallets, allowing developers to focus on delivering engaging gameplay.

However, as gaming ecosystems evolved, we identified a new challenge: the need for managing assets and identities across multiple games within unified platforms. While our embedded wallet worked perfectly for individual games, multi-game studios and token-unified platforms required a more comprehensive solution.

## Introducing the Openfort Ecosystem SDK

![openfort_ecosystem.png](https://blog-cms.openfort.xyz/uploads/openfort_ecosystem_43e2988f53.png)

To meet the needs of today’s Web3 gaming landscape, we’re proud to unveil the **[Openfort Ecosystem SDK](https://www.openfort.xyz/docs/guides/ecosystem)**—an all-in-one solution that expands on our original embedded wallet concept and enables seamless, multi-game experiences within a unified ecosystem.

### Key Features of the Openfort Ecosystem SDK

1. **Ecosystem Wallet = Unified Wallet**  
   At the core of our Ecosystem SDK is the concept of a **unified wallet**, which allows players to use a single wallet across multiple games within the same ecosystem. This eliminates the need for separate wallets for each game, enhancing user experience and simplifying wallet management.

2. **Seamless Player Experience**  
   Players can maintain a consistent identity and manage their assets effortlessly across all games within an ecosystem. The unified wallet streamlines onboarding and asset management, making it easier for players to engage across multiple games.

3. **Developer-Friendly Integration**  
   Our Ecosystem SDK offers developer-friendly tools that simplify game development and ecosystem management. It includes built-in features for managing ecosystem-wide policies, offering greater flexibility and security for developers.

4. **[Wagmi and RainbowKit Support](https://www.openfort.xyz/docs/guides/ecosystem/libraries)**  
   We’re excited to announce integration with **Wagmi** and **RainbowKit**, making it easier for developers to incorporate our ecosystem wallet functionality into existing projects. This means developers can leverage our SDK while maintaining familiar development workflows.

## Benefits for Players and Developers

### For Players:
- **Simplified Onboarding:** Players can register through social logins, passkeys, or wallet connectors, ensuring a frictionless entry into the game.
- **Unified Wallet Experience:** A [single wallet](https://www.openfort.xyz/docs/guides/ecosystem/configuration/wallet-ui) across multiple games within an ecosystem, providing seamless cross-app support and asset management.
- **Enhanced Security:** With **[Openfort Shield](https://www.openfort.xyz/docs/guides/javascript/embedded-signer/recovery)**, players benefit from enhanced security without compromising the user experience.

### For Developers:
- **Interconnected Applications:** Build and manage interconnected games and apps using a [single SDK](https://www.openfort.xyz/docs/guides/ecosystem/intro).
- **Comprehensive Management Tools:** Utilize a [customizable dashboard](https://www.openfort.xyz/docs/guides/dashboard/ecosystem) to manage entire gaming ecosystems from one platform.
- **Streamlined Developer Experience:** Enjoy opinionated developer flows that simplify integration and management processes.

![openfort_dashboard.png](https://blog-cms.openfort.xyz/uploads/openfort_dashboard_5517978e65.png)

## Looking Ahead: Shaping the Future of Web3 Gaming

The **Openfort Ecosystem SDK** marks a significant milestone in Web3 gaming infrastructure, providing the tools needed to build interconnected multi-game platforms. Our vision is to empower developers to create the next generation of Web3 gaming ecosystems—where players enjoy a unified experience, and developers can easily manage ecosystems.

Together, let’s shape the future of Web3 gaming, where ecosystems thrive and players experience seamless, interconnected worlds.

Stay tuned for more updates, and get ready to build the next era of gaming ecosystems with **Openfort**!

Introducing Ecosystem SDK: The Next Evolution in Cross-app interactions. A timely solution to the fragmentation and complexity challenges that have been hindering the chains' growth.

Playbook Cover Final-min.jpg

Introducing Ecosystem SDK



## The Role of Minting in Web3 Games

In Web3 gaming, minting in-game assets—like NFTs and tokens—is a fundamental component. For many games, it’s not only key to gameplay but also a crucial source of revenue.

## What is Minting?

Minting refers to the creation of new NFTs (Non-Fungible Tokens). Think of it as the digital equivalent of stamping a coin or printing a physical collectible. Once an NFT is minted, it becomes a unique, verifiable asset on the blockchain, with its ownership and properties immutably recorded.

Minting is essential for Web3 gaming, where assets like characters, items, or land are transformed into NFTs, giving players true ownership and the ability to trade these assets outside the game’s ecosystem. For Web3 engineers, understanding minting processes and tools is vital for building engaging, decentralized game economies.

## Minting and Gas Fees

Minting NFTs incurs a cost known as gas fees. Gas fees are essentially transaction costs paid to the blockchain network (like Ethereum) to compensate for the computational power required to execute and record transactions. The cost of minting varies based on factors such as network congestion and transaction complexity.

### What Happens After an NFT is Minted?

Once an NFT is minted, it is permanently recorded on the blockchain. This allows it to be transferred, sold, or traded like any physical collectible. In NFT gaming, players can own unique in-game items that can be sold or traded on secondary markets, adding a new dimension of value and ownership to their gaming experience. Ownership history and transaction details are transparent and easily verifiable on the blockchain, ensuring security and trust.

## NFT Metadata: Defining Uniqueness

NFT metadata plays a critical role in defining an NFT’s uniqueness and value. It includes details like the NFT’s name, description, and attributes, which distinguish it from other tokens. There are two main types of NFT metadata:

- **On-Chain Metadata:** Stored directly on the blockchain, providing higher security and immutability, but at a higher cost. Once created, on-chain metadata cannot be altered.
- **Off-Chain Metadata:** Stored outside the blockchain, typically on decentralized storage solutions like IPFS (InterPlanetary File System). This option is cheaper and offers greater flexibility, but it relies on the availability and integrity of the external storage provider.

## NFT Royalties: Continuous Revenue Streams for Developers

![Royalty.svg](https://blog-cms.openfort.xyz/uploads/Royalty_51a9ab4341.svg)

Royalties are a game-changing feature of NFTs, especially in Web3 gaming. They allow creators, such as game developers, to earn a percentage of sales whenever an NFT is resold. This creates a continuous revenue stream, incentivizing high-quality asset creation while supporting ongoing development.

In gaming, NFT royalties help sustain ecosystems by rewarding developers for their contributions, ensuring a healthy loop of creation, sales, and reinvestment in new content.

## Minting with Openfort: A Streamlined Solution for Web3 Engineers

Openfort simplifies the minting process for game developers through a comprehensive infrastructure, supporting the creation and management of NFTs at scale.

### 1. **ERC-721 Standard**
The ERC-721 standard is widely used for minting NFTs, ensuring each token is unique and verifiable. With Openfort, developers can easily mint ERC-721 tokens, streamlining the creation of one-of-a-kind in-game assets. You can even [batch transactions](https://www.openfort.xyz/docs/guides/javascript/smart-wallet/send#transactions) for a smoother user experience.

### 2. **Pre-Minted Assets and Minting Accounts**
Openfort also supports pre-minted assets through **Minting Accounts**, allowing developers to efficiently manage and distribute large numbers of NFTs. This feature is crucial for game studios looking to maintain control over asset distribution while handling large-scale minting operations. Learn more about managing pre-minted assets with [Openfort’s minting accounts](https://www.openfort.xyz/docs/guides/server/dev).

## Crafting In-Game Assets: Minting and Metadata Updates

NFT gaming goes beyond simple asset creation—it also involves crafting new assets. This process can be done in two primary ways:

### Mint and Burn
Minting new NFTs by burning existing ones is a popular mechanic. In this process, old NFTs are destroyed, and new ones with enhanced attributes or higher value are minted in their place. This mechanic is used in many Web3 games to allow players to upgrade or evolve their assets.

![burnAsset.svg](https://blog-cms.openfort.xyz/uploads/burn_Asset_4ed0aac3b4.svg)

### Updating Metadata
Instead of minting a new NFT, game developers can choose to update the metadata of an existing NFT. This is less resource-intensive and can be more efficient, especially when altering or enhancing in-game assets without creating entirely new tokens.

![metadataAsset.svg](https://blog-cms.openfort.xyz/uploads/metadata_Asset_44959d9af5.svg)

## Atomic Transactions: Ensuring Smooth, Secure Asset Creation

In NFT gaming, **atomic transactions** ensure that multi-step processes—like minting or crafting multiple NFTs—either succeed entirely or fail without partial execution. This prevents incomplete transactions and ensures a seamless experience for both players and developers.

By leveraging Openfort’s robust infrastructure and minting APIs, Web3 engineers can efficiently create, manage, and trade NFTs. Whether it’s ERC-721 minting, managing pre-minted assets, or implementing crafting mechanics, Openfort provides the tools you need to bring NFTs to life in your game.

## Elevating Gaming Economies with NFTs

Minting NFTs is one of the key tasks for Web3 engineers, especially in gaming, where these assets become the building blocks of player-owned economies. With Openfort’s support for minting, metadata management, royalties, and crafting, you can provide players with true digital ownership, enhancing both gameplay and revenue potential.


Minting of in-game assets in game like NFTs and tokens are one of the most crucial parts of web3 games and a source of revenue for most games

Group 650.svg

Minting gaming assets: NFTs and beyond for web3 games

## Our Journey: From Smart Accounts to Embedded Wallets

When Openfort began over a year ago, we pioneered one of the first ERC-4337 implementations of smart accounts for Web3 games. Our solution made it easier for developers to integrate blockchain technology, offering simpler transaction signing, gasless transactions, and support for native game frameworks.

To further support developers in onboarding users, we're excited to introduce **[Embedded Wallets](https://www.openfort.xyz/docs/guides/javascript/wallets)**—a seamless solution that combines authentication, in-app transaction signing, and smart accounts to enhance user experiences in apps and games.

## Understanding the Crypto-Enabled Stack

As blockchain adoption grows, developers need a simplified way to manage on-chain interactions. We talk to developers daily and understand that navigating the current crypto stack is more complex than ever. That’s why we’ve broken it down into three core layers: authentication, embedded signing, and smart accounts.

### The Three Layers of the Crypto-Enabled Stack

1. **Authentication**: Identifying who is executing the on-chain actions.
2. **Embedded Signer**: Authorizing and controlling on-chain actions.
3. **Smart Account**: Managing assets and recording blockchain transactions.

Our **Embedded Wallet** solution integrates all three layers into a unified experience, making it easier for developers and players to interact with Web3 technology.

![Crypto-enabled-stack.svg](https://blog-cms.openfort.xyz/uploads/Group_504_71412174c3.svg)

### The Authentication Layer: Simplifying user access  
[Authentication](https://www.openfort.xyz/docs/guides/javascript/auth) is essential to ensuring secure and user-friendly blockchain interactions. Traditionally, users are identified by their wallet addresses. With **embedded wallets**, we introduce a more accessible approach, allowing users to log in through email, social media accounts, or existing wallets.

This approach bridges the gap between Web3 and traditional web applications, enabling users to interact with blockchain-based apps without needing deep technical knowledge. For game developers, this means they can combine tools like Unity Gaming Services with blockchain technology to gather richer player data and improve management.

### The Embedded Signer Layer: Simplifying authorization  
The **[Embedded Signer](https://www.openfort.xyz/docs/guides/javascript/embedded-signer/recovery)** is how users authorize blockchain actions. Typically, transaction signing can be complicated and requires users to manage private keys. With **in-app wallets**, we remove that complexity by decoupling signing from the user's identity, offering a more secure and flexible transaction process.

Our embedded wallets seamlessly integrate this authorization layer with authentication, allowing users to approve transactions without worrying about key management. This ensures security and simplifies the user experience.

### The Smart Account Layer: Secure and flexible smart contracts  
At the core of blockchain interactions are smart accounts. Our **[Smart Account](https://www.openfort.xyz/docs/guides/javascript/smart-wallet/connected-wallets)** layer leverages ERC-4337 standards to provide advanced features like gasless transactions, automated batch transactions, and heightened security, all while keeping user assets secure.

These smart accounts are decoupled from the signer, offering flexibility for users to control their assets independently. Whether transferring assets or making on-chain purchases, the combination of smart accounts and **in-app wallets** creates a cohesive system for managing on-chain activities.

## Putting It All Together: Embedded wallets

![Openfort_stack.svg](https://blog-cms.openfort.xyz/uploads/Openfort_stack_925e4c7102.svg)

By combining authentication, embedded signing, and smart accounts, Openfort’s **[Embedded wallet](https://www.openfort.xyz/docs/guides/javascript/wallets)** deliver an integrated, user-friendly solution for Web3 applications and games. Whether you're developing a game or another blockchain application, our technology provides the flexibility to configure wallets according to your needs, without requiring browser extensions or external wallets.

### The Road Ahead: Enhancing wallet interoperability

Our focus now is on enabling seamless wallet interoperability across multiple applications. **In-app wallets** are laying the groundwork for easier asset management and transfers, making Web3 more accessible for both developers and users. Key benefits of this approach include:

- **Easier On-Ramps**: No need to repeatedly onboard assets after the first transaction.
- **Asset Visibility**: Developers can view assets across different apps in the ecosystem.
- **Secure Asset Composability**: Users can act on their assets securely across various apps.

Today, we offer advanced features like batched transactions, transfers from EOA wallets, and support for WalletConnect and Seaport protocols. In the future, we’re exploring even deeper integrations, including linking/unlinking signers and identity hubs, to push the boundaries of Web3 gaming and connectivity.

Stay tuned for more developments, and don’t hesitate to reach out if you’re interested in early access or want to learn more about Openfort’s embedded wallets and in-app wallets!

Unlock seamless Web3 experiences with Openfort's Embedded Wallets. Unifying authentication, in-app signing & smart accounts for easy onboarding. 

Embedded-wallets.svg

Announcing Embedded Wallets

## Overview
In this article, we will explore the concept of Recoverable Account and how it can be used using Openfort’s APIs. We will discuss the benefits of Recoverable Accounts, the design of Openfort Recovery, and what the future holds for this technology in the context of blockchain games and developers.

## Understanding Social Recoverable Accounts
Recoverable Accounts are a type of smart wallets that offer a method to recover lost access to a self-custodial account when not in possession of the seed phrases. It is Ethereum co-founder Vitalik Buterin's [preferred method](https://vitalik.eth.limo/general/2021/01/11/recovery.html) for securing a wallet.

Social Recoverable Accounts -also named social recovery- use smart contracts and Recovery Contacts (also known as Guardians) to add an additional layer of security. When a player loses access to their wallet (in this case, the private key controlling their Openfort account), they can reach out to their recovery contacts to sign a transaction to recover their wallet. 

Even though guardians can sign via direct onchain transfer, **with Openfort they also can leverage our API to avoid paying fees**; sending the signed message for them.
## Openfort Recovery Design

Openfort Recovery Design is inspired by the Social Recovery systems implemented by Argent. The owner of the wallet is always in full control, and a threshold is assigned for a minimum number of guardians to recover the wallet. 

![RECOVERY1.svg](https://blog-cms.openfort.xyz/uploads/RECOVERY_1_14825505d9.svg)

The owner can:
- Propose a new guardian.
- Cancel the proposal of a new guardian.
- Revoke a guardian.
- Cancel the revocation of a new guardian.
- Cancel the recovery mode.
- Transfer the ownership of the account (2 step process).

A guardian can:
- Start a recovery process.
- Lock and unlock the account for a period of time (`lockPeriod`).

Anyone can:
- When a guardian has been proposed for enough time (`securityPeriod`), confirm its proposal.
- When a guardian has been revoked for enough time (`securityPeriod`), confirm its revocation.
- When in recovery mode, submit the list of needed signatures (from half of the guardians) to complete the recovery of the account.

## Recovery Walkthrough

Given a player that has already connected their self-custodial wallet and Openfort has already deployed a smart wallet, we’re looking at an example where Openfort is by default the only guardian to recover the account. 

![RECOVERY2.svg](https://blog-cms.openfort.xyz/uploads/RECOVERY_2_2b90e665d7.svg)

This is just for demonstration purposes. In reality the players with self-custodial wallets have full control of their smart accounts and can decide who to add or remove as guardians. As a game developer you can suggest a friendly configuration where the game is one of the guardians to ease the recoverability process of the account. 

When "Start Recovery Process", this action calls the start recovery function in the contract, signaling the default Guardian (Openfort in this case) to initiate the recovery process.

Openfort (the guardian) has 2 days to complete the recovery process (gather all required signatures).Once signed, it approves the recovery process and the ownership of the account changes to the new address specified during the recovery initiation. 

In the event of the owner’s private key being found or the process being started by a malicious guardian, the owner can cancel the recovery process anytime before being completed.

### Trying out Openfort's Sample
For developers eager to dive into the code Openfort has made their contracts available in the [Openfort Contract Repository](https://github.com/openfort-xyz/openfort-contracts/tree/main/contracts/core) and the [sample](https://github.com/openfort-xyz/samples/tree/main/recoverable-accounts).

To get started with the sample:

- Clone the Sample Repository: This is the first step to accessing the sample code.
- Setting up the Environment: Before diving into the code, ensure you've set up the environment correctly. Create the `.env` file from the `.env.loca` example and populate it with the necessary information. All the required details can be fetched from the Openfort dashboard.
- Starting the Sample Application: Once everything is set up, execute `yarn` and then `yarn start` to get the sample application running.


## Wrapping up
Excited to use recoverable accounts in your game? Let's get started by looking at our [documentation](https://openfort.xyz/docs) and our [video walkthrough](https://www.youtube.com/watch?v=E8e1pklBbgw) for more.

If you have more questions/ideas/queries, join our Developer Discord and let us know there. Furthermore, you can follow us on Twitter for our updates as we keep shipping.


In this article, we will explore the concept of Recoverable Account and how it can be used using Openfort’s APIs. 

Group 385.svg

Technical Dive: Social Recoverable Accounts 

## Understating the ERC-6551
ERC-6551 is an Ethereum standard that allows ERC-721 tokens to have their own smart contract accounts, also known as Non-fungible Token Bound Accounts (TBA). This means that NFTs can now own digital assets and interact with various applications. The system doesn't require any changes to existing ERC-721 NFTs.

The ERC-6551 mechanism consists of three key parts: a registry, an account interface, and a minimal proxy implementation. The registry is permissionless and immutable, and it deploys a smart contract account for an NFT. 

The account interface sets the standard process, rules, and limits for account creation. ERC-1167 minimal proxy contracts are used in deploying accounts, making account implementations much easier and cheaper.

ERC-6551 is an improvement over ERC-721 because it overcomes some of the limitations of ERC-721. ERC-721 tokens are static and can only show static data or information. They are also not composable and cannot interact with other on-chain assets or contracts independently. ERC-6551, on the other hand, maintains backwards compatibility with previously minted ERC-721 NFTs and deploys smart contract accounts for NFTs via a permissionless registry. 

Check the [technical ERC-6551 proposal](https://eips.ethereum.org/EIPS/eip-6551) as well as the [non-technical write up](https://medium.com/future-primitive/tldr-nfts-have-their-own-wallets-try-it-here-http-tokenbound-org-6fac135a1f9d) from the authors.

## The Gaming Use Case for ERC6551
### Before ERC6551
In a traditional gaming application, players could own their characters as ERC-721 NFTs. However, all related assets that they collected within the game would also sit as separate tokens in the owner's wallet. This could be inconvenient for players, as they would have to keep track of multiple tokens and manually transfer them between their character and their wallet. 

Additionally, it would be difficult for game developers to create in-game UIs that allowed players to easily manage their assets.
### With ERC6551
ERC6551 allows game developers to create "inventories" for players. This means that all of a player's game-related assets can be automatically transferred into their character's wallet. This makes for a better user experience, as players no longer have to keep track of multiple tokens. 

Additionally, it allows game developers to create in-game UIs that are much more user-friendly.

For example, imagine a game where players can collect different weapons and armor. With ERC6551, players could simply equip their weapons and armor directly from their character's inventory. This would make the game more immersive and engaging, as players would no longer have to switch between their wallet and the game UI to manage their assets.
### Benefits of ERC6551 for gaming
ERC6551 offers a number of benefits for gaming applications, including:
- Improved user experience: ERC6551 makes it easier for players to manage their game-related assets.  You can now create a smart account via a minted or airdropped NFT
- Enhanced gameplay: ERC6551 can be used to create more immersive and engaging gameplay experiences. For example, players could use ERC6551 to equip their characters with different weapons and armor, or to purchase items from in-game shops.
- Increased security: ERC6551 can help to improve the security of game assets. This is because token-bound accounts are more secure than traditional wallets (EOAs).
Overall, ERC6551 is a valuable tool for gaming applications. It can be used to improve the user experience, enhance gameplay, and increase security.

## Challenges and Limitations of ERC-6551
While ERC-6551 brings a new layer of functionality to NFTs, it also introduces a set of challenges and limitations:
1. Complex NFT User Experience: ERC-6551 adds additional features and capabilities to NFTs, which also brings a new layer of complexity. Users need to have a higher level of understanding to fully utilize these advancements. 
2. Implementation Complexity: Implementing the ERC-6551 standard into existing ERC-721 tokens requires creating and configuring a new smart contract. This process can be complex and requires technical expertise. Additionally, it may involve paying for the services of a blockchain developer. 

At Openfort we want to overcome these challenges by smoothing and standardizing the interactions directly via APIs, offering an already build implementation catered towards web3 gaming. 

Let’s see how we’ve done this. 

## Combining the ERC6551 and ERC4337
The creation of smart wallets within in-game assets represents a leap forward into the evolution of the player experience in the game. No longer the standard unlocks new utility for NFTs but also allows for composability with other standards, in this case the famous ERC4337 (Account Abstraction).

At Openfort, we looked at the different ways we can combine them together to untap novel use cases while enjoying an optimal player experience. Here are the findings and thoughts as well as the path to follow if you’re looking to implement and offer “wallet-less” experience to your players. 

### Option 1: NFT is owned by an Openfort 4337 account

![Group 348.svg](https://blog-cms.openfort.xyz/uploads/Group_348_05b11271b9.svg)

The first option drops an ERC721 into a newly created smart wallet with Openfort. The ERC721 is 6551 compatible allowing it to store the different in-game assets, while the interactions happen at the Openfort level (4337 compatible) ensuring there is a smooth player experience -gasless txs and zero txs prompts. 

Nevertheless this option has constraints because the actions need to be encoded before sent and get the new owner form the logs via the implementation ABI.
All in all:
- (+) It uses session keys, which can enable a popup-less experience for users.

- (-) You deploy two smart wallets making it more costly to interact.

- (-) While the implementation works with Openfort it is cumbersome to use via the API.

See the implementation in our [Github repository](https://github.com/openfort-xyz/samples/tree/main/ERC6551-token-bound-accounts#option-1).

### Option 2: NFT is owned by an EOA and EIP6551 account is EIP4337 compliant

![Group 349.svg](https://blog-cms.openfort.xyz/uploads/Group_349_48e9e86864.svg)

This option reduced the complexity of the implementation, because now you don’t need to deploy two smart contract wallets but rather make the TBA compatible with ERC4337 directly while the EOA has the ERC721 ownership. 

The main disadvantage here is that you need to be careful the way you apply session keys within the game in the case an NFT owner decides to transact their token. 

All in all:
- (+) It reduces the complexity of the solution while also lowering the gas spending (you only create one smart wallet instead of two).
- (~) You can still benefit from session keys in your game but need to make sure to revoke them if the NFT is transferred to a new owner.

See the implementation in our [Github repository](https://github.com/openfort-xyz/samples/tree/main/ERC6551-token-bound-accounts#option-2).
## How can I use Token Bound Accounts with Account Abstraction?

Openfort’s 4337 account and a 6551 account are quite similar. The main difference is that the ownership of the 4337 account is defined by who has the signer and the ownership of the 6551 account is defined by who has the NFT.

Both have therefore the option of transferring ownership. 
- For the 6551 account, approve and transfer the ownership of the NFT.
- For the 4337 account, [transfer](https://www.openfort.xyz/docs/guides/javascript/smart-wallet/advanced/transfer-ownership) ownership of the account.

While both options are doable we recommend following **the second implementation better**. It’s natively supported [via our endpoints](https://www.openfort.xyz/docs/reference/api/create-an-account-object) and ensures a smooth player experience as long as we implement the revocation of session keys is needed given a change of ownership of the NFT (we can help with that). You can check the ERC6551 smart contract [here](https://github.com/openfort-xyz/openfort-contracts/blob/main/contracts/core/erc6551/ERC6551OpenfortAccount.sol).


If you have more questions/ideas/queries, join our [Developer Discord](https://discord.com/invite/t7x7hwkJF4) and let us know there. Furthermore, you can follow us on [Twitter](https://twitter.com/openfortxyz) for our updates as we keep shipping.

Learn the in's and out's of the ERC6551 with Openfort's smart accounts and learn how to make them both together for your game.

Group 344 (2).svg

Token Bound Account with Account Abstraction – New Era

In the burgeoning domain of Web3, an innovative concept has emerged—session keys. These keys are akin to the well-known JSON Web Tokens (JWTs) but come with a twist, facilitating decentralized user verification in contrast to the centralized verification in traditional systems. 

## Session Keys in Action
Session keys are cryptographic keys used to establish a secure connection between a player's device, the game server and the user's web3 account. They act as temporary, specific-use keys for Web3, offering a much-needed solution. Session keys are similar to JWTs in the Web2 realm but come with more versatility, essentially serving as "programmable JWTs."

They are generated inside the player's device and are used to authenticate requests from the player. Session keys are short-lived and typically expire after a certain period of inactivity or when the player logs out.

These keys permit users to interact with a game based on predefined conditions, such as duration, token spending limits, post frequency, or other functions specific to the smart contract.

Incorporating session keys into web3 games offers several advantages:

- **Security:** Session Keys are scoped, and smart contracts can dictate which instructions a specific session key can accept. By storing expiry and access information at the contract level, session keys become less vulnerable to security risks. Additionally, layered security further protects user assets.
- **User Experience (UX):** Session keys significantly improve crypto UX by eliminating the need for constant wallet popups while a user performs actions within a dApp for a specified duration.
- **Interoperability:** Session keys function at the contract level, allowing users to continue using their preferred browser wallets while interacting with a dApp that supplies a session key in the background. This maintains app interoperability and enhances UX.

## Gaming and Session Keys

One of the most promising applications of session keys lies in the gaming domain. Given that many modern games involve in-game purchases, trades, and other transactions, session keys can drastically improve the gaming experience.

By allowing users to pre-authorize a range of transactions, games become smoother and more engaging. Players no longer need to pause their game every time they make a transaction, leading to uninterrupted gameplay.

![How session keys work-1.svg](https://blog-cms.openfort.xyz/uploads/session_key_walkthrough_ff19816585.svg)

Let's explore the four major steps involved in this process.

- When players log in, they should generate a session key on their device and send it to your game server. The sensitive part of the session key (the session private key) is always securely stored on the player's device and is not disclosed.
- The player includes the public part of the session key in subsequent requests from the player's device to the game server for authentication. Such requests should be digitally signed by the secret part of the session key.
- On the game server, validate the session key and the signature before processing the request. Periodically refresh the session key during the player's session to maintain security.
- Players can invalidate the session key whenever they want, e.g.: after logging out or after a certain period of inactivity.

## The Bright Side of Session Keys

![SessionKeysExample (1).svg](https://blog-cms.openfort.xyz/uploads/Session_Keys_Example_1_e31e7c28fb.svg)

Session keys can potentially redefine user interactions with games, offering a seamless experience that's unprecedented in the Web3 domain:

- **Bypassing Confirmations:** No more disruptions! Session keys can help bypass continuous transaction confirmations, especially beneficial in applications where frequent small transactions are made.
- **Offline Operations:** Session keys enable users to execute transactions even when offline. For example, a user can participate in an NFT drop without having to be online at the time of the drop.

## Setting New UX Standards

The introduction and adoption of session keys are not just about improving transactions; they are setting a new standard for user experience in the Web3 domain. By offering features like offline transactions and bypassed confirmations, session keys are paving the way for more intuitive and user-friendly games.

Excited to use session keys? Let's get started by looking at our [documentation](https://www.openfort.xyz/docs/guides/javascript/smart-wallet/advanced/session-keys) and our [Youtube video](https://www.youtube.com/watch?v=rh2E02PATlU) for more. 

If you have more questions/ideas/queries, join our [Developer Discord](https://discord.com/invite/t7x7hwkJF4) and let us know there. Furthermore, you can follow us on [Twitter](https://twitter.com/openfortxyz) for our updates as we keep shipping.


Session keys are cryptographic keys used to establish a secure connection between a player's device, the game server and the user's web3 account.

Group 329.svg

Technical Dive: Unveiling Session Keys for smooth UX

_Article updated November 2024_

Are you building the next big blockchain game or app? Or are you creating an entire ecosystem or chain? Openfort has the tools you need, no matter your goal. Let's find the perfect solution for you.

## Our objective: Helping onchain economies grow

Openfort's mission is to catalyze the **growth of onchain economies**. We believe that by building 1) a robust onboarding with integrated signer management and 2) a cutting-edge middleware platform, we're expanding opportunities for thousands of projects to create create fun and engaging experiences where users actively participate in the economies they generate. 

>Build the necessary infrastructure for hit games like Clash of Clans to thrive onchain.

## For game and app developers

As a game studio or startup project, you need a robust, user-friendly wallet infrastructure that seamlessly integrates with your project. There are many considerations if you're building in the space and Openfort offers one of the most generous tiers to test and initially scale your product to market fit.

Here's how Openfort stacks up against other solutions in the market:

| Feature | Openfort | Thirdweb | Sequence | Privy |  
|---------|----------|----------|----------|-------|
| Frictionless onboarding | ✅ | ✅ | ✅ | ✅ | 
| Open source embedded signer   | ✅        | ⚠️      | ⚠️       | ⚠️       |
| Account abstraction infrastructure | ✅ | ✅ | 🔄 (Not 4337) | 🔄 (Third party)  | 
| Gaming SDKs (Unity & Unreal Engine)  | ✅ | ✅ | ✅ | ❌ | 
| Marketplace orderbook | ✅ | ❌ | ✅ | ❌ | 
| Backend wallets | ✅ | ✅ | ❌ | ❌ |

### Why choose Openfort

1. **Game developer kit**: Our APIs and SDKs cover Unity, UE5, vanilla JS, and popular backends like .net or NodeJS. We provide you with all the tools you need in the client and in the server, either JS or non-JS environments.
2. **Performance first**: Apps and games demand constant resources and infrastructure to allocate for user spikes and virality. Our servers manage nonces automatically, offers the fastest transaction processing, and handles retries and gas spikes, ensuring smooth gameplay even during high-traffic periods.
3. **User-friendly onboarding**: We offer various onboarding methods, including email, social login, passkeys, and injected wallets, making it easy for players to get started. Moreover if you want to user your own custom auth solution or an OIDC compatible token we can help.
4. **Open-source guarantee**: Our open-source signer solution (named Shield) and hosted recovery options, provides transparency and flexibility in security management. becasue using smart wallets even if Openfort is down you can assure your users will have access to wallet via onchain recoverability. 

Get started with **[embedded wallets](https://www.openfort.xyz/docs/guides/getting-started)**.

## For ecosystems and blockchains

At Openfort we think Ecosystem Wallets are the optimal solution for project that want to offer a wholesome ecosystem experience. Similar to how explorers are an essential part of the infrastructure, unified wallets are a must if you're developing developer friendly ecosystem with an excellent user experience as an unique feature.

Here's how Openfort compares in this space:

| Feature | Openfort  | Dynamic | Privy  | Thirdweb |
|---------|----------|----------|--------|-----------|
| JS SDK               | ✅        | ✅       | ✅       | ✅       |
| Unity SDK            | ✅        | ❌       | ✅       | ✅       |
| Unreal Engine SDK    | ✅        | ❌       | ❌       | ✅       |
| Social login (Auth)  | ✅        | ✅       | ✅       | ✅       |
| Custom auth provider | ✅        | ❌       | ❌       | ❌       |
| Embedded signer *1   | ✅        | ⚠️      | ✅       | ✅       |
| Smart account *2     | ✅        | ⚠️       | ⚠️       | ✅       |
| Whitelabel dashboard | ✅        | ❌       | ❌       | ❌       |
| Cross-app SDK        | ✅        | ❌       | ❌       | ❌       |
| Open-source framework | ✅ | ❌   | ❌ | ❌ |

_*1 Openfort embedded signer doesn't depend on third party services.
*2 Openfort develops smart accounts and supports third party accounts._

### Why choose Openfort

1. **Unified UX and UI**: Our ecosystem architecture allows you to host your own subdomain and brand while keeping your own packages registry. no need to create or wrap anything else. 
2. **Cross-device onboarding**: With support for major game engines and client SDKs, Openfort makes it easy to integrate apps and games within your ecosystem.
3. **Open-source communication framework**: Manage pop-ups, session keys, and smart accounts effortlessly across your entire ecosystem.

Get started with **[ecosystem wallets](https://www.openfort.xyz/docs/guides/ecosystem)**.

Whether you're building a single game or an entire ecosystem, Openfort provides the tools and infrastructure you need to succeed in the blockchain space. Choose Openfort for a scalable, flexible, and user-friendly wallet solution that grows with your project.

Discover how Openfort powers blockchain games and ecosystems with robust wallet infrastructure, open-source tools, and user-friendly onboarding. Try it now!

Group 283-min.png

Openfort vs Other Solutions: Wallets for Developers

## Overview

One innovation in the blockchain space is ERC4337, a standard for account abstraction on the EVM ecosystem. In this document, we will delve into the Paymaster component of ERC4337 and its functionality within the framework.

## Understanding Gasless Transactions

Paymasters, or "gas sponsors," in ERC4337 are smart contracts that enable transaction sponsorship through third-party-designed mechanisms. Often referred to as [gasless transactions](https://www.openfort.xyz/docs/guides/dashboard/gas-sponsorship)
Gasless transactions empower contracts to pay on users' behalf under any given conditions, unlocking a new realm of possibilities for transaction sponsorship mechanisms on EVM blockchains.

![PaymasterArchitecture-min.png](https://blog-cms.openfort.xyz/uploads/Paymaster_Architecture_min_6f6cfb813d.png)

Let's explore the four major steps involved in this process.

- **Step 1: Welcoming UserOperations**

Openfort, functioning as the primary orchestrator, receives a set of UserOperations. This phase represents the initiation of the ERC-4337 transaction flow.

- **Step 2: Meeting the Paymaster Contract**

Openfort communicates with the Paymaster contract, contingent on the inclusion of the Paymaster within the UserOperation. The Paymaster contract is responsible for potentially covering transaction fees for Contract Accounts. Openfort then verifies if the Paymaster has a sufficient deposit or if the associated Contract Account possesses the required gas fees.

- **Step 3: Custom Fee Logic in Action**

If a Paymaster is involved, it can apply its proprietary fee logic. This allows for a flexible and tailored transaction fee structure based on the specific Paymaster's criteria.

- **Step 4: Signature Validation and Execution Initiation**

At this juncture, Openfort collaborates with the Contract Account and, when applicable, the Paymaster to authenticate the signatures present in the UserOperation. The Contract Account serves as the interface between the user and Openfort, ensuring streamlined transactional communication. Upon successful signature validation, Openfort conveys the necessary data from the UserOperation to the Contract Account, initiating the transaction execution.

## Types of Paymasters

Paymasters can generally be categorized into two types: those with off-chain logic and those with on-chain logic, or simply put those that abstract the payment of network tokens and those that abstract the payment of network tokens with an alternative ERC-20 token. 

### Standard Paymasters: Sponsoring transaction fees

![PaymasterArchitecture (1)-min.png](https://blog-cms.openfort.xyz/uploads/Paymaster_Architecture_1_min_568b3ecc56.png)

Currently, to transact on blockchains you'll need the network token to pay for gas (i.e. Polygon you need MATIC). Standard Paymasters offer an alternative approach to this requirement.

Openfort verifies the logic of the paymaster, determines if the paymaster should cover the transaction costs, and signs offchain to pay the gas costs. These costs are directly extracted from the paymaster (smart contract pool) filled with network tokens, similar to the operation of relayers with meta-transactions. 

[Get started with the sponsored transactions](https://www.openfort.xyz/docs/guides/javascript/smart-wallet/send#transactions)

### ERC20 Paymasters: Paying with ERC-20 tokens

![PaymasterArchitecture (2)-min.png](https://blog-cms.openfort.xyz/uploads/Paymaster_Architecture_2_min_f815f9fd48.png)

ERC20 Paymasters present another innovative solution. This approach allows for the integration of a Paymaster with an existing ERC-20 token, such as USDC or your own game token. In this scenario, the Paymaster can pay for gas fees with:
- A fixed amount of ERC20 conversion. This implies that the fixed ERC20 amount will pay the amount of gas fees. This brings consistency to the end user experience but also exposes the game to win/lose ERC20 if the value is above/below the gas fee.
- A dynamic amount of ERC20 conversion. This let's you cover the gas fees based on the conversion rate of your ERC20. This could be your preferred conversion rate or simply the conversion rate in a DEX (we'll use an Oracle for that). 

[Get started with the ERC20 Paymaster](https://www.openfort.xyz/docs/guides/dashboard/gas-erc20)

**Extra notes:**
- You can use the ERC20 from a players wallets to also subsidize for the network gas fees. It collects digital currencies from the user, converts them into native tokens based on the prevailing exchange rate, and pays for gas fees on behalf of the user.
- You can create policy rules to be more granular on the sponsorhip details, based on contracts. functions and limits like gas cot or timme. 
- Get your gas reports directly on the dashboard on monthly basis and pay directly with Fiat without holding tokens/crypto yourself.


If you have more questions/ideas/queries, join our [Developer Discord](https://discord.com/invite/t7x7hwkJF4) and let us know there. Furthermore, you can follow us on [Twitter](https://twitter.com/openfortxyz) for our updates as we keep shipping.

One innovation in the blockchain space is EIP-4337, a standard for account abstraction on the EVM ecosystem. In this document, we will delve into the Paymaster component of EIP-4337 and its functionality within the framework.

Group 328 (1).svg

Technical Dive: Gas Sponsorship via Paymasters


There's no one right way to build with Openfort. Whether you want high-touch, high control, or more of a set-it-and-forget it approach, our SDKs and API have what you need. This post is rather short but sharing the architecture representation of what we've built. 

### Simplified Overview of Openfort
Openfort provides SDKs and APIs for the most popular smart wallet features, including transaction relay and gas sponsoring, transaction batching, session keys, social recovery, and more.

![Group 295-min.png](https://blog-cms.openfort.xyz/uploads/Group_295_min_3ec4bfb35f.png)

## Openfort's Architecture

1. **Hyperstructure-Based Infrastructure:** Openfort takes infrastructure to the next level with hyperstructures, simplifying digital asset access, enhancing liquidity, and expanding network value.

2. **Server-Centric Architecture:** Openfort's infrastructure is backend first instead of client first, tailored specifically for the gaming industry's backend requirements.

3. **Ecosystem Integration:** Games can tap into existing gaming ecosystems, leveraging network effects, shared tokens, policies, and wallet infrastructures. This allows for unprecedented interoperability and value creation across multiple games and platforms.

![Openfort Features](https://blog-cms.openfort.xyz/uploads/Features_Openfort_min_75f88075b3.png)

Learn about the Openfort's architecture with our diagrams and see how it can help you get your game to the next level,

coverEcosystem

Technical Dive: Openfort's Architecture

**“Increase the number of successful blockchain powered games in the world”**

We do this by helping developers be better at their gaming projects.

## TL;DR
Openfort's philosophy centers on providing frictionless experiences for users and developers, promoting open and free solutions without lock-in, and nurturing a community-driven approach. Openfort offers the flexibility to self-host or opt for a pro version, aligning with open-source principles.

## First Principle: Enhancing the user and developer experience
Openfort's philosophy is to pursue seamless experiences for users and developers. Openfort provides easy-to-use tools and APIs, enabling developers to focus on crafting engaging applications without managing complex infrastructure. Users should be able to interact with applications effortlessly, irrespective of the technology involved.

We aim to remove obstacles for developers by providing standardized APIs and SDKs. These tasks include blockchain interactions, wallet management, and transactions. This approach empowers developers to concentrate on producing exceptional games and applications, free from concerns about underlying systems.

## Second Principle: Promoting Open Solutions and Avoiding Lock-In
Embracing an open, free, and iterative approach is at the core of Openfort's philosophy. Openfort supports self-hosting and pro versions to cater to user preferences and requirements. This approach motivates users to take ownership of their projects and adapt the codebase as needed. This environment enables developers to experiment, learn, and grow without constraints.

## Third Principle: Fostering a Community-Driven Approach
A vibrant developer community is central to Openfort's philosophy. It emphasizes the importance of collaboration, support, and resource-sharing among developers. The platform's goal is to establish a thriving ecosystem where developers can contribute to the platform's growth and improvement. This will shape the project's future based on their needs and feedback.

As part of Openfort's commitment to open source, developers are actively invited to share their knowledge, collaborate on projects, and provide feedback in order to enhance the platform. Its supportive and inclusive environment empowers its users to drive innovation and develop cutting-edge applications.

If you have more questions/ideas/queries, join our [Developer Discord](https://discord.com/invite/t7x7hwkJF4) and let us know there. Furthermore, you can follow us on [Twitter](https://twitter.com/openfortxyz) for our updates as we keep shipping.

Openfort offers the flexibility to self-host or opt for a pro version, aligning with open-source principles.

CoverPhilosophy

Embracing Openness: Openfort's Philosophy

## Overview
Gaming, a realm that has been a part of our culture since the advent of Pong in the 1970s, has seen a significant transformation over the years. Today, we are witnessing the rise of broader ecosystems involving multiple games, publishers, and organizational structures. This evolution is not just about the games themselves, but also about how players interact with them and each other.

At Openfort, we've been working on a framework that reimagines the gaming ecosystem. This framework offers key features such as single sign-on, interoperability, achievement tracking, enhanced permissioning flows, and ecosystem control. We believe this approach will benefit players, developers, and various gaming ecosystems by providing seamless integration, cross-game compatibility, and frictionless onboarding.

## The Openfort Framework: A New Approach to Gaming

Our framework introduces several features that are designed to enhance the gaming experience:

- Single Sign-On Across Games: One ecosystem-level profile serves as an SSO for any game within the ecosystem.
- Interoperability: Secure and standardized cross-game compatibility for in-game currencies, assets, and more via a player's managed or connected external wallet.
- Achievement Tracking: Ecosystem-level support for soul-bound tokens, achievements, XP, rank, and more.
- Enhanced Permissioning Flows: OAuth-like authorization for asset control across ecosystem games.
- Ecosystem Control & Security: Explicit approval for games requesting access to profile assets and authentication.
## Creating a Seamless Experience for All

Our framework is designed to work seamlessly for everyone involved:

1. Players: APIs work with ecosystem profiles and standard game-level player accounts, requiring no additional implementation.
2. Developers: No extra logic is needed to make frictionless API calls on behalf of players using ecosystem profiles. The same accessToken and decryptWalletKey are provided for seamless integration with existing API usage.
## Potential Use Cases

Our framework can be applied to a variety of scenarios:

- Gaming DAOs with Partnered Games
- Game Publishers with Multiple Games
- Game Marketplaces
- Gaming Guilds and Gaming Communities

![EcosystemOverview](https://blog-cms.openfort.xyz/uploads/Ecosystem_Overview_f652153a6d.svg)

## Benefits of Gaming Ecosystems

The Openfort framework offers a multitude of benefits that enhance the gaming experience for both players and developers:

- **Customization and Branding**: Partners can create their platform's UI/UX flow for ecosystem integration with fully documented APIs or opt for the existing UI/UX flow. Customization options include brand colors, logos, icons, background images, domain/subdomain attachment, and more.

- **Security and Permissioned Asset Access:** The ecosystem auth flow offers a clear and user-friendly method for games to request permission to access a player's ecosystem profile wallet assets. This approach mirrors conventional OAuth permissioning flows and mitigates the risk of compromised assets.

- **Effortless Integration for New and Existing Games:** The ecosystem product seamlessly integrates with new or existing games by simply implementing a "Sign In With..." button within the game. This approach requires no additional logic or development overhead, ensuring a seamless onboarding experience for both players and developers.

- **Keep Your Gaming Progress Secure and Uninterrupted:** With your Game ID, switching, losing, or reinstalling devices won't disrupt your gaming progress. Your account remains secure and accessible, allowing you to effortlessly pick up right where you left off.

- **Simplify Your Gaming Experience:** Imagine a unified gaming experience where you can seamlessly connect all your games to a single ID. By creating an ID, you'll enjoy a streamlined gaming experience across our entire ecosystem.

- **Play, Connect, and Foster a Vibrant Community:** Connecting with fellow gamers is an integral part of the gaming experience. With Game ID, you can find and connect with other players and friends. The friends you make in one game will be visible in other games they play, fostering a vibrant and connected community.

- **Take Your Game Progress To The Next Level:** Your Game ID holds the key to unlocking our marketplace, where you will effortlessly be able to trade, buy, and sell assets from all games within the ecosystem. Managing your virtual assets becomes a seamless and enjoyable part of your gaming journey.

Let's get started by looking at our [documentation](https://www.openfort.xyz/docs/guides/ecosystem) and our [Youtube video](https://www.youtube.com/watch?v=s8wMDpTTzJE).

If you have more questions/ideas/queries, join our [Developer Discord](https://discord.com/invite/t7x7hwkJF4) let us know there and follow us on [Twitter](https://twitter.com/openfortxyz) for our updates as we keep shipping.

Transform your gaming experience with the Openfort framework—seamless single sign-on, cross-game interoperability, and achievement tracking. 

Introducing Openfort kit

Introducing Openfort kit

Building scalable applications with backend wallets

Openfort Launch Week 1: Wrap up

Extra Releases: Audits and samples

Chain Abstraction framework for ecosystems

Announcing React Native SDK

Guest accounts and new samples

Announcing Ecosystem Wallet 2.0

Ecosystem Customization Tool

Introducing Ecosystem SDK

Minting gaming assets: NFTs and beyond for web3 games

Announcing Embedded Wallets

Technical Dive: Social Recoverable Accounts

Token Bound Account with Account Abstraction – New Era

Technical Dive: Unveiling Session Keys for smooth UX

Openfort vs Other Solutions: Wallets for Developers

Technical Dive: Gas Sponsorship via Paymasters

Technical Dive: Openfort's Architecture

Embracing Openness: Openfort's Philosophy

Gaming Ecosystem: Cross-Game Integration

Product

Resources

Company

Openfort blog

Introducing Openfort kit

Introducing Openfort kit

Building scalable applications with backend wallets

Openfort Launch Week 1: Wrap up

Extra Releases: Audits and samples

Chain Abstraction framework for ecosystems

Announcing React Native SDK

Guest accounts and new samples

Announcing Ecosystem Wallet 2.0

Ecosystem Customization Tool

Introducing Ecosystem SDK

Minting gaming assets: NFTs and beyond for web3 games

Announcing Embedded Wallets

Technical Dive: Social Recoverable Accounts

Token Bound Account with Account Abstraction – New Era

Technical Dive: Unveiling Session Keys for smooth UX

Openfort vs Other Solutions: Wallets for Developers

Technical Dive: Gas Sponsorship via Paymasters

Technical Dive: Openfort's Architecture

Embracing Openness: Openfort's Philosophy

Gaming Ecosystem: Cross-Game Integration