The Wallet Framework for Chains.

The Ecosystem Wallet Framework represents a comprehensive solution for enterprises and developers seeking to implement robust, scalable wallet infrastructure across their blockchain ecosystem. This framework addresses the complexities of wallet architectures while maintaining enterprise-grade security and seamless integration capabilities.

Why we built this#

Let's be honest - building a smart wallet system from the ground up is no walk in the park. You've got to juggle quite a few balls: setting up authentication, picking the right smart contracts for accounts, implementing signers for ownership, and getting all the infrastructure ready for transaction sponsorship and bundling. Phew!

Sure, you could use a third-party provider to handle all this, but here's the tricky part: it needs to be flexible enough to adapt to your needs while still having as little vendore lock-in to integrate. And let's not forget about the developer experience - because nobody wants to spend weeks just figuring out how to implement a wallet system.

What's in the box?#

Here's the cool stuff you get with the Ecosystem SDK:

• User Management: Think of it as your bouncer - keeping track of who's who and making sure only the right people get in
• Smooth Wallet Onboarding: We make it super easy for users to get started with their wallets, add funds, and jump right in
• Your Wallet, Your Rules: Want to make it look and feel like your own? No problem! You've got full control through our whitelabel dashboard and customizable packages
• Works Everywhere: Whether you're building on Unity, Unreal Engine, or browsers, we've got you covered

How it all fits together#

The Ecosystem SDK is built like a well-organized kitchen, with three main stations:

1. Developer Integration Layer: Where you cook up your integration
2. Client-Wallet Communication: The service window where orders (transactions) get passed
3. Blockchain Interaction: Where the magic happens on the blockchain

The main ingredients#

Client SDK (@openfort/ecosystem/client)#

Think of this as your head chef - it runs the show. It handles everything from creating your custom wallet SDK to managing pop-ups and transactions. The best part? It lives right in your app's front-end and can wear your brand's colors. It even comes with built-in security features and plays nice with all the popular blockchain tools.

Communication Module (@openfort/ecosystem/core)#

This is your maitre d' - making sure everything flows smoothly between your client and the wallet. It helps new users get set up with their non-custodial wallets and works in any browser environment. Need more details? Check out our wallet guide.

Framework Prefabs#

These are like your ready-to-use recipe cards. We've got special helpers for different frameworks, including a really nice setup for React (@openfort/ecosystem/react). And yes, you can customize all the components to match your style!

"But why not just use embedded wallets?"#

Good question! While embedded wallets might seem simpler at first glance, they can actually create quite a headache when you're working across an ecosystem. Here's why:

The Embedded Wallet setup#

Picture this: every single app needs its own separate setup - installing packages, generating keys in iframes, handling authentication... It's like having to build a new kitchen for every restaurant in your chain!

The Not-So-Fun parts of embedded wallets#

1. Authentication gets messy

   • Every app needs its own bouncer (authentication system)
   • OAuth2 providers get confused when trying to share wallet access
   • There's no good way to keep track of who's logged in where

2. Less control than you'd like

   • Your partners need access to the master keys (Admin credentials)
   • It's harder to keep track of who's spending what
   • No central control room for permissions

3. More work for everyone

   • Each partner has to figure out their own wallet setup
   • More chances for security slip-ups
   • No easy way to see what's happening across all apps

Why the Ecosystem SDK is better#

What you get:

• One login system that works everywhere (no more authentication headaches!)
• Control all permissions from one place
• A slick dashboard with your brand to onboard projects
• Paymasters and smart accounts by default
• One solid security setup for everything