Forte acquired Sealance in February 2025, adding the startup’s zero-knowledge policy technology to Forte’s on-chain compliance tools. The acquisition price was not disclosed. Forte says the combined offering is intended to let developers enforce identity and transaction rules without putting users’ full identity records on a public blockchain—but it does not make players anonymous or, by itself, make a game legally compliant.
What Forte acquired—and when
Forte Labs acquired Sealance Corp. in February 2025. VentureBeat reported the deal on February 27, and Forte’s press material is dated February 28. Neither the purchase price nor the deal structure was disclosed. VentureBeat reported that Sealance’s cryptography and information-security specialists joined Forte; the acquisition combines Sealance’s technology with Forte’s Rules Engine and wider compliance offering. VentureBeat’s acquisition report and Forte’s press page provide the announcement context.
Sealance had emerged from stealth in 2022 with seed backing from investors including Galaxy, Ribbit Capital and Coinbase Ventures, according to its announcement at the time. Its acquired technology is described as a zero-knowledge policy engine: a way to prove that a user or transaction meets a rule without disclosing all the underlying information.
Why identity and privacy are difficult in Web3 games
A public blockchain can make wallet addresses, balances, transfers and contract activity visible to anyone. A player may want to own and trade an in-game asset without exposing a real-world identity or making a complete transaction history easy to associate with them. Yet a game with tradable assets, cash-out features or financial products may need controls for KYC, sanctions, fraud, jurisdiction and other legal or operational risks.
Developers also face game-specific abuse: bots, multiple accounts used to claim rewards, market manipulation, exploitative trading and stolen wallets. Identity and policy checks can help limit some behavior, but a proof of identity is not a cure for account sharing, collusion, device farms or credential theft.
Privacy claims need a further qualification: avoiding personal records on-chain does not erase the public activity of a wallet. Forte’s own privacy policy warns that blockchain information may be public and immutable, and that information written to a blockchain may not be alterable or deletable.
What a zero-knowledge proof does—and does not do
A zero-knowledge proof lets one party demonstrate that a statement is true without revealing the secret or all the data used to establish it. In a game, the statement might be “this wallet belongs to a participant who passed the required check” or “this transfer satisfies the game’s eligibility policy.” A smart contract or policy system can act on that result rather than receiving a passport number or a complete identity file.
That is selective disclosure, not necessarily anonymity. A KYC provider or other credential issuer may still collect and verify documents in the first place. Depending on the system, that provider, a game operator or another party may retain records or be required to disclose them under applicable procedures. Wallet activity, timing and transaction patterns can also reveal information even when a proof conceals personal attributes.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →Forte says its ZK Policy Engine does not see, collect or store personal information and does not take custody of currencies being transacted. These are company claims about the product; they do not establish what a separate identity issuer collects, how credentials are revoked, or who can access related records. The ZK Policy Engine page describes Forte’s intended model, but the public materials do not specify all production architecture and data-handling details.
How the Sealance and Forte tools are intended to work together
Forte’s Rules Engine is designed to apply controls to on-chain activity, including rules around minting, burning, transfers, wallet access, transaction limits and economic safeguards. The Sealance technology is intended to add a privacy-preserving way to establish that a wallet or transaction meets a policy. In a simplified illustrative flow—not a confirmed deployment for a named game—a player completes an identity or compliance check, obtains or presents a credential, and supplies a proof of eligibility. The rules infrastructure then permits, restricts or rejects an action based on that result.
- A player seeks to trade a tokenized game item.
- An identity or compliance process establishes whether the player meets the game’s requirements.
- The system generates or verifies a proof that the wallet is eligible under the applicable policy.
- The rules layer uses that result to allow or deny the transfer, without necessarily placing the player’s full identity record on-chain.
The exact production architecture, supported credential issuers, proof formats, revocation model and developer API details are not specified in the public materials. Forte’s developer documentation describes the Rules Engine’s capabilities, but product descriptions should not be mistaken for proof that each use case has been deployed by a game publisher.
What game developers could use it for
Forte presents its tooling as a way to express and enforce rules around wallets, tokens and transactions. Potential game applications include restricting transfers to eligible participants, applying different limits based on verification status, controlling who can mint or redeem assets, and limiting access to particular marketplaces or rewards. Developers might also use eligibility checks for age-restricted content or jurisdiction-based restrictions, subject to the relevant legal and operational requirements.
The distinction matters: Forte documents capabilities and intended uses, but the sources available do not identify a game publicly using the Sealance integration in production. Nor do they establish performance, transaction-cost effects or a measured reduction in fraud. A team evaluating the product should request a working implementation and evidence for the specific controls it plans to rely on.
The acquisition reaches beyond gaming
Forte’s background is closely tied to blockchain gaming. It previously announced a strategic partnership with Zynga focused on blockchain gaming and economic opportunities for players (Zynga–Forte announcement) and partnerships with game developers (Forte’s 2020 announcement).
Its current positioning is broader. Forte describes applications spanning gaming, token-driven projects, real-world assets, stablecoins, DeFi and institutional use cases. The Sealance acquisition is therefore both a gaming infrastructure story and part of a wider move toward programmable compliance and economic controls for on-chain products. Forte’s site outlines that broader positioning.
What the public information does not establish
- Commercial terms: The purchase price, deal structure and Sealance’s revenue contribution were not disclosed.
- Live adoption: The available sources do not name a game or publisher using the integrated technology in production, or give customer numbers.
- Technical validation: The public material reviewed does not specify the production proof system, independent security audits, smart-contract audit results, performance or transaction-cost data.
- Data and credentials: Supported identity providers, data-retention arrangements, credential revocation and the ability to reuse a credential across applications are not established.
- Availability and pricing: Forte describes the Rules Engine as free and open source on its developer page, while its main site says custom Rules Engine pricing varies and directs prospective customers to contact the company. That does not establish that hosted services, identity checks, integration help or enterprise features are free.
- Legal effect: No regulatory approval or legal opinion is established by the acquisition announcement. A technical policy engine can help enforce controls; it does not determine whether a game, token or business complies with every applicable law.
Check chain support before building
Forte’s documentation is not consistent about supported chains. Its general site lists Ethereum and Polygon and indicates other chains are coming, while the developer page lists a broader set, including Base, Arbitrum One, Harmony, BSC, Avalanche and Optimism. The public pages do not explain whether these differences reflect outdated material, component-specific support or different meanings of compatibility. Confirm the exact network, product component and production support directly with Forte before designing around a chain.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEFix the driver behind crashes, sound loss and screen glitchesFind Drivers →Best Value
The developer page also says the Rules Engine is compatible with most Web3 wallets. That broad statement does not establish support for a particular wallet, account-abstraction setup or the ZK integration on every listed chain.
Questions to ask before adopting a ZK policy system
- Privacy: Who collects and holds raw KYC data? What appears on-chain? Can wallets or proofs be linked across games and transactions?
- Eligibility and recourse: Which provider makes the verification decision? How are sanctions and risk data updated? How can a player challenge a mistaken block or restore access?
- Credential lifecycle: How do expiration and revocation work if a user moves, loses a wallet, becomes restricted or triggers a new risk signal?
- Security and governance: Are the contracts and proof components independently audited? Who can change policy, upgrade contracts or control hosted services, and how are those actions recorded?
- Engineering and operations: Which chains, wallets and identity providers work in production? What are proof-generation latency and verification costs in the intended flow? Can the system be used without Forte-hosted services?
- Commercial and migration terms: Which features are free, which require a contract, and are there per-user, per-verification or transaction fees? Can policies and relevant records be exported if a project later migrates?
These questions matter because privacy and compliance are not opposites, but a proof alone cannot answer who controls the underlying data, how exceptions are handled or whether a particular product meets its legal obligations.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
