Obscuro Labs

• Requirement for fully mature, standardized enterprise compliance attestations today (e.g., SOC/ISO-type certifications)
• Inability to accept any hardware trust dependencies
• Need for immediate, deep liquidity and broad wallet/bridge support

• Reliance on TEEs implies an attack surface and trust assumptions that require ongoing mitigation
• The roadmap indicates several key capabilities are future milestones (for example, public attestation and sequencer decentralization)

• February 2026: mainnet launch and first ecosystem partners going live on mainnet
• March 2026: proof-of-cloud with public node attestation
• April 2026: mainnet optimisation target to 10,000 TPS and decentralised validator nodes
• H2 2026: fully decentralised L2 sequencer (Stage 2) and exploration of hybrid TEE x FHE

Caution: Roadmaps commonly slip. Confirm what was delivered as of March 11, 2026 versus what remains planned.

No independent benchmarking was located in the reviewed sources. Any TPS targets should be treated as aspirational until validated by public performance reports, reproducible test methodology, or third-party benchmarking.

Public documentation and third-party user reviews do not provide extensive detail on integration experience. Typical early-L2 friction should be expected: wallet support variability, bridge UX risks, and tooling gaps.

• Concerns about TEE trust assumptions and hardware supply-chain risk
• Less mature ecosystem compared with dominant L2s (bridges, wallets, liquidity, composability)
• Limited operational track record relative to Optimism/Arbitrum
• Potential regulatory or reputational concerns around privacy technologies in certain jurisdictions and sectors

• Selective confidentiality for EVM-compatible applications ("smart transparency")
• TEE-based encrypted execution to enable private state and logic without zero-knowledge proving overhead
• A focus on MEV mitigation and encrypted processing

• Aztec: cryptographic privacy emphasis and visibility in market coverage
• Optimism/Arbitrum: ecosystem scale, third-party integrations, and production maturity

• Need for privacy/confidentiality within an Ethereum-adjacent execution environment
• Desire for MEV mitigation and encrypted transaction handling
• Preference for a TEE-based model instead of ZK tooling complexity and proving costs, at least in the short term

No detailed, independently verifiable enterprise case studies were located in the reviewed sources.

TEN’s published roadmap mentions early ecosystem partners and applications, including references to ecosystem partners and an AI Poker relaunch.

These appear to be forward-looking statements rather than documented post-deployment case studies. Until detailed post-mortems (time-to-value, costs, security incidents avoided, measurable outcomes) are available, stated outcomes should be treated as unproven.

Most plausible early adopters include:

• Early-stage to mid-market product teams with small to mid-sized engineering teams building privacy-sensitive onchain applications
• Larger enterprises exploring onchain systems, conditional on governance, security assurances, and available support models

• iGaming and gaming studios with hidden-state mechanics
• DeFi builders requiring strategy confidentiality
• AI-agent product teams needing private state and transaction logic
• Onchain marketplaces where order-flow confidentiality matters

Decision makers:

• Head of Engineering / CTO
• Protocol architect / security lead
• Product lead for an onchain application

Technical operators:

• Smart contract engineers
• Infrastructure/SRE staff for node operations
• Security engineers responsible for threat modeling

• The project requires protocol-level confidentiality that cannot be solved by application-layer encryption alone
• The project can accept or mitigate TEE trust assumptions
• The organization is prepared to manage earlier-stage ecosystem tradeoffs