Management API Reference

Architecture

Explore Openfort’s system design and components.

Openfort's smart contracts are open source. Moreover, Openfort is built on public goods infrastructure like the ERC-4337, ERC-7702 or ERC-6551 standards. We choose open source tools which are scalable and make them simple to use.

Openfort is not a 1-to-1 mapping of any wallet solution you've seen. While we offer many of the features that other solutions have, we go much further than anyone else because: (1) we support both Smart wallets (4337) and Smart EOAs (7702), and (2) we build the server stack so you don't have to worry about the reliability of the infrastructure.

Architecture#

Openfort consists of modular components that allow you to plug-and-play the tools to achieve your success. Our product suite is designed to be flexible - you can use individual components or the entire stack based on your needs.

Our infrastructure orchestrates everything under the hood to make development and maintenance easy. The key components we take care of are:

Core Infrastructure#

  • Authentication UI + Wallet Connector: A flexible authentication system that works with both Smart EOAs (7702) and Smart Wallets (4337). This component can be used independently of other Openfort solutions.

  • Invisible wallet: A non-custodial wallet that is invisible to the user. It can be used for both smart EOAs and smart wallets. This wallet is designed to be used with Openfort's infrastructure, but it can also be integrated with third-party key management solutions.

  • Cross-App Wallet: Our newest wallet solution that works seamlessly with all Openfort infrastructure or can be integrated with third-party key management solutions.

  • Backend Wallets: These are externally-owned accounts used internally to manage the project flows and experience. They can execute logic like escrow for competitions or sending a minted asset to a user after winning a competition.

  • Infrastructure: We built a robust infrastructure to support the seamless integration of blockchain functionalities into your applications. With features like REST APIs, SDKs, webhooks, and abstraction infrastructure, developers can efficiently manage their applications while providing a smooth user experience.

    • Bundlers/RPCs: We built a Meta Bundler Network to ensure reliable access to the blockchain. If one fails, another takes over.
    • Paymasters: We built the most customizable paymasters to configure granular rate limits and policies for gas sponsoring, through either our API or dashboard.

Modularity & Flexibility#

Openfort's architecture is designed to be modular, allowing you to:

  • Use the authentication UI and wallet connector with either smart EOAs or smart wallets.
  • Use the invisible wallet with third-party key management solutions.
  • Implement the cross-app wallet with Openfort's full infrastructure or with third-party key management and third-party wallets.
  • Use any paymasters.

Our goal at Openfort is to help all types of applications have wallets that touch the blockchain.