Changelog

Great news this week! It looks like we've made significant improvements to your authentication options and documentation structure.

1. New Authentication Methods: Telegram & Line.

2. Updated Documentation Structure. Resources are now split into two main categories: Embedded Wallets & Ecosystem Wallets.

Moreover we've added New Build References and Guides:

• Unity
• JavaScript (JS)
• Unreal Engine

We've updated the UE5 SDK now to accomodate native onbaording with our auth systems, session keys and onchain actions. Get started with the UE5 SDK and blueprints here.

We've also started to rollout our ZKsycn support with selected partners. Feel free to connect with us if you want to use it in your project.

Introducing Identity Linking: You can now connect email, Oauth providers and wallets under one single player identity. Link your player's identity here

We've also spent part of this August incresing the throughput of the overall system to accomodate our enterprise partners. Now with our new architecture we've make it 3x faster to send transactions onchain with average time of ~3sec. The efforts include: further load balancing mechanisms, circuit breakers, new indexer and database migration.

We're happy to announce that we've audited our SSS library in Go and publish the report for more people in the space to use and contribute.

You can see the full announcement here.

Migrated codebase to Viem you can now use Viem or Ethers direcly too. New guides on how to user web3 library connectors here.

This past couple of weeks at Openfort we've been working on improving the infrastructure speed

• New: Export Private Key.
• New: Ecosystem SDK sample.
• New Sample: Now featuring Wagmi sample.

Improvements#

• Stability improvements for openfort JS.
• Improved edge cases for Openfort Identity where user could not logged in after logging out.
• Fixed a bug that was clocking the CPU

The emergence of new gaming chains also means games are being onboarded into different ecosystems and environments. With Ecosystems we help those manage games easily.

New Features#

1. Cross-Chain Game Management

   • Unified infrastructure for managing games across multiple blockchains
   • Support any new EVM rollup you request
   • Embedded gaming wallet functionality

2. Ecosystem Policies

   • Centralized policy management (e.g., gas limits) applicable across all games in an ecosystem

3. White-Label Dashboard

   • Customizable interface for ecosystem administration
   • Project-specific views for individual game developers and ecosystem managers

4. Authentication System

   • Customizable authentication clients
   • Single Sign-On (SSO) support for consistent wallet experience across ecosystem
   • Enhanced security through abstracted private key handling

Technical Improvements#

• API extensions for ecosystem-wide operations
• Enhanced SDK support for multi-game environments
• Improved data aggregation for cross-game analytics

Developer Tools#

• New documentation for Ecosystems integration
• Updated SDKs with ecosystem management capabilities

Compatibility#

• Backward compatible with existing Openfort integrations
• New endpoints added for ecosystem-specific operations

For detailed API changes and integration guidelines, please refer to the full documentation

This update includes several improvements and new features:

Enhanced Authentication#

• Added new login methods: Discord and Epic Games.
• Ability to create server session keys and store them in your gaming backend to make automatic actions.

Documentation Improvements#

• Restructured documentation into two main sections:
  • Identity: Covers authentication and embedded signer.
  • Cloud: Focuses on onchain actions.

Unity SDK Updates#

• Refactored Unity SDK with:
  • Improved support for WebGL.
  • Improved native flows for authentication.

Improvements in Openfort Auth

• New password recovery setup.
• New Social Logins: Fascebook and X(Twitter) -If you need new ones let us know!.
• Added PKCE login for Android, iOS and macOS clients.

Improvements on the Openfort-JS

• Added signTypedData.
• Fixed Openfort URI and constructor when inid library.
• Export 1669 provider.

• Improved the perfomance of our network of RPCs. Incorporated circuit breaker and load balancer that helped us decrease redundancy issues and throughput across the transaction cloud.
• We've added orderbook support to instantly list any asset across Seaport protocol based marketplaces. Starting with Beam subnet support with more coming soon
• Added support for loading the library as a JS script
• 74% size reduction for openfort-js SDK
• Token Swap Module added support for Degen chainx

• Pre-generate embedded wallets associated with a given account, like an email address, without requiring the user to login, all from the backend.

Updated NodeJS and C# SDKs available.

• We've deployed the improvement around webhooks. You can now subscribe to receive webhook notifications on successful, failed, cancelled and broadcasted transactions.

• Improved iframe communication and new endpoints to sign types of transaction from Shield.

Announcing two new endpointto exhange tokens:

• /v1/exchange endpoint, designed to facilitate faster and more efficient token swaps on our decentralized exchange (DEX). This feature allows you to initiate token swaps directly, ensuring that your transactions are executed with optimal speed and precision.
• /v1/exchange/quote endpoint, which provides real-time quotations for token swaps. This allows developers to fetch potential swap details, including fees and slippage, before executing the transaction.

Check the exchange endpoint in the API reference docs.

Also, we're happy to share that Openfort is now Paymaster agnostic. This means you can define custom logic to select the paymaster (if any) to use with the accounts you control. This allows you to use your own paymaster or even use multiple paymasters in different scenarios.

Creating a self-custodial account is one of the key onboarding flows for web3 games. Shield brings a powerful new way to manage the recovery key.

This highly requested feature allows the most advance games to self-host the Shield server themselves in order to add further resilinece in their system.

Use Shield to:

• Use the automatic recovery.
• Use the user's entropy (password.

For custom implementations we also have a self-host Shield.

Openfort Identity is built on a novel combined architecture of smart wallet technology and a secure enclave signing service.

By design our solution is fully equipped with:

• OpenID Connect and OAuth2 support, designed in a non-custodial framework, making it simple to connect any OAuth2 provider for seamless wallet access.
• Custom auth support, so you can use your preferred auth and gaming baxkend solution.
• Built with verifiable and opensource server called Shield.
• Ability to self-host the Shield and the iframe.

→ Try on Unity. → Try on browser.

Read the full announcement blog.

You can now integrate in-app purchases safeliy in your web3 game and start monetizing players regularly (all within the compliance boundaries o Apple and Google).

Here is how we're using in-app purchases in our sample:

• Buy soft-currencies (not crypto).
• Buy NFTs directly with IAP or your soft-currency.
• Sell NFTs for your game token (hard currency).

Read more about IAP in web3.

After deploying one of the first versions of smart accounts compliant with the ERC4337. We've finally pushed the envolope in auditing it with CertiK. Both the Smart Contract Wallets as well as the Paymasters were part of the scope.

We take security of our contracts very seriously and we constantly thinking ways to better explain the thread model and security decision we take internally. To read more about the security at OPenfort you can find go to the Security page.

You can read teh audit here and here is the public profile.

Use backend wallets as you develop your game in order to scale and customize any onchain interaction between the players and your game.

For example:

• Send NFTs to users purchasing a pre-minted NFT instead of minting directly from the smart contract.
• Airdrop users some in-game tokens.
• Escrow user's assets until the outcome is decided (i.e. competition)

Backend wallets can be configured to either use relayers in order to execute transactions or simply with the wallets native network token. his feature allows your app to sponsor gas for your users to transfer NFTs, list items on marketplaces, and more.

Today's fragmented solutions and their gaps—in the areas of throughput, nonce management, reorg detection, transaction retries, and more—force developers to DIY their own transaction, wallet, key, and gas management infrastructure.

Our Transaction Cloud addresses all of the challenges above and more. It abstracts the complexities of writing to blockchains through simple HTTP REST APIs—enabling developers to manage the entire transaction lifecycle with unprecedented ease and scale.

- High-Performance REST APIs: Achieve thousands of requests per second with simple HTTP APIs that eliminate the need for private keys, wallets, or gas management. Integrate transactions effortlessly with one line of code, ensuring scalability and reliability.

- Nonce Management and Idempotency: Automatically ensure transactions are unique and executed in order, preventing double spends and saving engineering time.

- Dropped/Reorg Detection and Auto-Resubmission: Our system automatically retries transactions in case of failures, reducing the need for manual monitoring and enhancing product reliability.

- Horizontally-Scalable Transaction Wallets: Utilize auto-scaling wallets for fast, consistent performance under any load, supporting your growth without architectural changes.

- Auto-Managed Gas with USD Billing: We handle all aspects of gas management, including fluctuations and accounting, allowing you to focus on core operations.

- Real-Time Transaction Lifecycle Management: Get instant updates on transaction statuses from initiation to confirmation, with alerts for any anomalies.

Cross-Chain Signing and Attestations: Facilitate secure interactions across different blockchains with EIP-712 signing and signature-based updates and attestations, reducing complexity and enhancing security.

Gas policies allow you to customize the user experience in your application. The combination of gas policies and rules lets you set control on transactions you want to sponsor and transactions you want the user to charge with.

You can now select policy strategies:

• Sponsor transactions by paying the gas on behalf of the user.
• Let users pay with the in-game token (ERC20) with a dynamic rate (live quote of the token).
• Let users pay with the in-game token (ERC20) with a fixed rate.

Also, you could define policy rules:

• Sponsor interactions with smart contracts.
• Sponsor interactions with the smart account.
• Limit the amount of gas or number of transactions over an interval.

Above and beyond#

• When using the Openfort policies, you will now receive email alerts automatically when you are close to hitting your sponsorship limits. Never see unexpected failed sponsorship again.
• You can now buy gas credits directly in your dashboard to increase your sponsorship limits in seconds with a credit card - no need to manage native tokens and no limits on sponsorship!