We're excited to announce that Openfort has successfully deployed compatible smart accounts on ZKsync! This integration brings powerful account abstraction capabilities to Zksync’s high-performance Layer 2 network and the ZK Chains like Sophon.

### Key highlights:
- Native support for ZKsync’s account abstraction model
- Seamless deployment process using ZKSync's custom tools
- Enhanced transaction flexibility and security for users
- Potential for gas-free transactions and advanced account features

Our smart accounts on ZKsync enable developers to build more user-friendly apps and games with features like social recovery, multi-signature control, and customizable spending limits. By leveraging ZKsync’s scalability and Openfort's account infrastructure, we're paving the way for mainstream adoption of web3 applications.

Stay tuned for a detailed tutorial on how to integrate these smart accounts into your ZKsync projects. We can't wait to see what innovative use cases the community builds with this new capability!

For inquiries, collaborations, or to join our discussions, connect with us on [Discord](https://discord.com/invite/t7x7hwkJF4). Stay updated with our progress by following us on [Twitter](https://twitter.com/openfortxyz).


We're excited to announce that Openfort has successfully deployed compatible smart accounts on ZKsync and the Elastic Chain. 

large_ZKSync.png

medium_ZKSync.png

small_ZKSync.png

thumbnail_ZKSync.png

ZKSync.png

Openfort adds ZKsync and Elastic Chain support

**Overview**
Openfort's UE 5 SDK enables developers to create embedded wallets and ecosystem wallet compatibility for their games and applications. The SDK provides a simple API to interact with wallets, login with email or socials, as well as create Smart Wallet session keys.

With this SDK, you can keep the onboarding of your users in-client and grant a session key to your Openfort powered backend to interact with the blockchain, no signature in sight.

Get started by following the documentation [here](https://www.openfort.xyz/docs/reference/unreal-engine).

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

**Features**

* **Onboard first time users** - ephemeral guest wallets.
* **Create and login to self-custodial wallets** - unlocking email and social authentication to create persistent, cross-platform, cross-device and cross-sdk signless embedded wallets.
* **Unlock the power of Account Abstraction** - unlock the ability to sponsor gas and interact on behalf of users by upgrading any wallet to a Smart Wallet, and using Session Keys to grant scoped access to your backend - fully compatible with solution.
* **Wide Compatibility** - the SDK is compatible with the Ecosystem SDK as well, allowing you to leverage the latest features and improvements across the chain's environment.

For more information visit https://github.com/openfort-xyz/openfort-unreal-engine

UE SDK enables developers to onboard and use smart accounts natively on the gameplay. 

unreal_logo.svg

Announcing Openfort Unreal Engine SDK

At Openfort, our mission is to empower developers to create great games with seamless blockchain integration. Today, we're excited to share a significant milestone in our journey towards more secure and transparent infrastructure: the results of our recent security audit for our Shamir's Secret Sharing (SSS) library, implemented in Go.

You can find our [Go SSS library](https://github.com/openfort-xyz/shamir-secret-sharing-go) and the [full audit report](https://drive.google.com/file/d/1fQ5lCg-JgH_TcSt9hCwcIv-psP_8Nbze/view?usp=sharing).

## The Importance of Shamir's Secret Sharing

Shamir's Secret Sharing Scheme (SSS) is a cryptographic primitive that allows a secret to be divided into multiple parts, or shares, with a threshold number required to reconstruct the original secret. This technique is crucial for secure key management and distribution in various cryptographic applications, including blockchain wallets and secure multi-party computation.

Fun Fact: Shamir's Secret Sharing Scheme was invented by Adi Shamir, one of the creators of the RSA algorithm, in 1979. It's a testament to its robustness that it remains a crucial part of modern cryptography over four decades later!

### Deep Dive: How SSS Works

At its core, SSS relies on a fascinating property of polynomials: any degree-k polynomial can be uniquely identified by any set of k+1 distinct points. Here's how it works:

1. **Encoding the Secret**: The secret S is encoded into a polynomial f(x) of degree k-1 over a finite field Fp. The polynomial takes the form:

   f(x) = S + r₁x + r₂x² + ... + rₖ₋₁xᵏ⁻¹

   where S is the secret (constant term) and r₁, r₂, ..., rₖ₋₁ are random coefficients.

2. **Generating Shares**: n distinct shares are generated by evaluating f(x) at different points. Each share is an ordered pair (xᵢ, f(xᵢ)).

3. **Recovering the Secret**: Any k shares can reconstruct the original polynomial using Lagrange interpolation, allowing recovery of the secret S by evaluating f(0).

## Our Audit Journey

In our commitment to security and transparency, we engaged Cure53, a renowned security firm, to conduct a thorough cryptography review and source code audit of our Go SSS library. The audit, completed in August 2024, focused on ensuring the correctness and security of our implementation.

### Key Findings and Implemented Solutions

1. **Overall Soundness**: The audit revealed that our SSS library is generally sound and correctly implemented. The use of GF(2^8) for the underlying field was noted as a good choice for simplification and future-proofing.

2. **Timing Variance Resolution**: A low-severity issue (OFT-01-001) was identified, showing a small timing variance in the GF256 multiplication. We've addressed this by implementing a constant-time solution, enhancing the library's resistance to potential timing attacks.

3. **Enhanced Input Validation**: Following the auditors' suggestion (OFT-01-002), we've implemented more robust input validation during the reconstruction process. This improvement enhances the library's resilience against potential attacks and ensures smoother error handling.

### Technical Deep Dive: Ensuring Implementation Security

One critical aspect of SSS implementation that our library carefully addresses is the "zero share problem". This occurs when a share's x-coordinate is zero, potentially revealing the secret directly. Our Go implementation includes safeguards against common pitfalls:

- **Counter-based shares**: We ensure our share generation starts from 1, not 0, avoiding accidental zero shares.
- **User input handling**: Our library implements strict checks to prevent user-supplied values or identifiers that could lead to zero shares.
- **Secure random number generation**: We use Go's crypto/rand package to generate secure random numbers, mitigating the risk of zero or predictable shares.

These measures, along with the improvements suggested by the audit, make our SSS library a robust and secure choice for developers. If you're curious, check how we're combining the SSS library with [Shield](https://www.openfort.xyz/docs/guides/auth/recovery) and our [security approach](https://www.openfort.xyz/docs/security) at Openfort.

## Our Commitment to Open Source

We're excited to announce that we're open-sourcing both our SSS library and the full audit report. As the first of its kind implemented in Go, we believe this library will be a valuable addition to the cryptographic community.

By making our library and audit results public, we aim to:

1. Contribute to the broader understanding of secure SSS implementations
2. Invite peer review and continuous improvement of our codebase
3. Provide a valuable resource for developers and researchers in the field, especially those working with Go

Fun Fact: The concept of open-source security is often referred to as "Linus's Law", named after Linus Torvalds: "Given enough eyeballs, all bugs are shallow."

## Looking Ahead

The audit results have provided us with valuable insights, and we've already implemented the suggested improvements. We're committed to maintaining the highest standards of security and will continue to invest in regular audits and open collaboration.

We encourage the community to review our library, provide feedback, and contribute to its ongoing development. Together, we can build a more secure and robust foundation for the future of decentralized applications.

Join us in our mission to make blockchain integration safer and more accessible for game developers worldwide. Let's build the future of gaming, securely and transparently, together.

Today, we're excited to share a significant milestone in our journey towards more secure and transparent infrastructure

large_Audit Thumbnail Final-min.jpg

medium_Audit Thumbnail Final-min.jpg

small_Audit Thumbnail Final-min.jpg

thumbnail_Audit Thumbnail Final-min.jpg

Audit Thumbnail Final-min.jpg

Securing the Future: Openfort's SSS Library Audit and Open Source Commitment

We're excited to announce that Openfort has successfully deployed compatible smart accounts on ZKsync! This integration brings powerful account abstraction capabilities to Zksync’s high-performance Layer 2 network and the ZK Chains like Sophon.

Native support for ZKsync’s account abstraction model

Seamless deployment process using ZKSync's custom tools

Enhanced transaction flexibility and security for users

Potential for gas-free transactions and advanced account features

Our smart accounts on ZKsync enable developers to build more user-friendly apps and games with features like social recovery, multi-signature control, and customizable spending limits. By leveraging ZKsync’s scalability and Openfort's account infrastructure, we're paving the way for mainstream adoption of web3 applications.

Stay tuned for a detailed tutorial on how to integrate these smart accounts into your ZKsync projects. We can't wait to see what innovative use cases the community builds with this new capability!

For inquiries, collaborations, or to join our discussions, connect with us on 

. Stay updated with our progress by following us on 

For inquiries, collaborations, or to join our discussions, connect with us on [Discord](https://discord.com/invite/t7x7hwkJF4). Stay updated with our progress by following us on [Twitter](https://twitter.com/openfortxyz).

Openfort adds ZKsync and Elastic Chain support

Key highlights:

Securing the Future: Openfort's SSS Library Audit and Open Source Commitment

Announcing Openfort Unreal Engine SDK

Product

Resources

Company