Introduction
Tensora is an AI-focused Layer 2 (L2) built on BNB Chain using the OP Stack. It turns machine intelligence into a first-class onchain primitive by creating incentive markets—subnets—where model providers (miners) serve inference and data services, evaluators (validators) score quality, and rewards flow transparently in TORA. Tensora keeps full EVM compatibility, settles to BSC for security and finality, and uses BSC calldata for data availability.
At a glance:
OP Stack rollup on BNB Chain with EVM equivalence and native bridge support
AI subnets for inference, embeddings, analytics, and other intelligence tasks
Economic alignment via staking, delegation, emissions, and slashing
BNB as native gas, with ERC-4337 Paymaster so users can pay fees in TORA
Upgradeable protocol using OpenZeppelin UUPS and timelocked governance
Why Tensora
Most L2s only scale transactions. Tensora scales intelligence. By combining a performant rollup with markets for AI work, Tensora lets builders deploy applications that reason, classify, summarize, embed, and predict—without trusting a single centralized API. Quality is measured onchain through validator scoring and Yuma-style commit-reveal consensus, so rewards follow verifiable performance.
In spirit: Bittensor’s open intelligence economy, implemented for the EVM and anchored to BNB Chain.
How Tensora works
Subnets Independent, onchain-registered markets specialized for tasks such as LLM inference, embeddings, vision, time-series prediction, or data labeling. Each subnet defines parameters (tempo, commit/reveal windows, stake minima, fees, reward weights) governed by TORA holders.
Participants
Miners serve model outputs (e.g., inference, embeddings).
Validators query miners, evaluate outputs, submit scores onchain.
Delegators stake TORA behind validators to amplify accurate scoring.
Consensus & rewards Validators commit and later reveal their scores in Yuma-style consensus. Aggregated scores determine per-epoch emissions, split among miners, validators, and delegators. Misbehavior is penalized via slashing.
Gas model The protocol executes with BNB as native gas (OP Stack convention on BSC). A TORA Paymaster lets users pay fees in TORA; the Paymaster settles BNB under the hood for seamless UX.
Governance & upgrades All core contracts are UUPS-upgradeable behind a Timelock + Governor. Storage layout checks and upgrade tests are enforced in CI.
High-level architecture
Copy
flowchart LR
User -->|Tx or UserOp| Sequencer
subgraph Tensora L2
Sequencer --> L2Exec[(EVM)]
L2Exec --> Subnets
Subnets -->|scores| Consensus[Yuma Commit/Reveal]
Paymaster --> L2Exec
end
Sequencer --> Batcher
Batcher -->|calldata batches| BSC[(BNB Chain L1)]
L2Exec <-->|bridge msgs| Bridge[L1/L2 Standard Bridge]Who should use Tensora
Dapp teams that need onchain access to inference or embeddings without relying on a single vendor
AI providers who want to monetize model serving in an open, verifiable market
DeFi/infra builders integrating predictive or classification signals onchain
Researchers testing incentive mechanisms for ML quality and robustness
Key properties
EVM-native: Solidity, Foundry, Hardhat, wagmi/viem, ERC-4337
Production-minded: UUPS upgrades, timelock governance, storage-layout guardrails
Composability: Use subnets like any onchain service, bridge assets with standard OP contracts
Transparency: Emissions, scores, and rewards are onchain and auditable
Quick start
Connect Add Tensora to your wallet using the RPC and chain ID above.
Bridge Wrap your underlying token to WTORA on BSC, then bridge WTORA to Tensora using the Standard Bridge.
Build
Call subnets from smart contracts or through SDKs.
Register a miner or validator and join a subnet.
Use the Paymaster to pay fees in TORA.
Govern Stake, delegate, and vote to evolve parameters, add subnets, or upgrade modules.
Design notes
BNB remains the protocol’s native gas for compatibility and reliability.
TORA is the network’s economic unit for staking, rewards, governance, and optional gas via the Paymaster.
WTORA on BSC is the canonical L1 token to ensure bridge safety even if the original token has transfer restrictions.
Alt-DA paths are intentionally left open; initial DA is BSC calldata for simplicity.
Continue to Features for a capability walkthrough, or jump to Getting Started to connect, bridge, and deploy your first contracts on Tensora.
Last updated