1. What Bitroot is
What is Bitroot?
Bitroot is a Layer 1 blockchain that runs EVM transactions in parallel. It keeps the EVM bytecode and Ethereum tooling, and adds an AI inference interface that contracts can call directly. Its published headline figures are 100,000+ TPS and about 0.3 seconds to finality. Those are the project's own numbers, and the site does not attach full test conditions to them; the question on TPS below explains how to read them.
Is Bitroot a Layer 1 or a Layer 2?
A Layer 1. It runs its own consensus and validator set instead of settling on another chain. The consequence is that security rests on Bitroot's validators and is not inherited from Ethereum. The benefit is that execution and settlement share one domain, with no bridge hop by default. Positioning Bitroot lays out what this choice solves and what it leaves open.
What problem is it built for?
The EVM executes a block's transactions one at a time, in a fixed order. A single execution thread caps throughput however many cores the node has, which The EVM Single-Thread Bottleneck traces back to the Yellow Paper. AI agents and distributed compute jobs make that cap more visible, because they generate many small, frequent transactions that need to be cheap and checkable. Bitroot's answer has two parts: parallel execution with pipelined consensus for throughput, and an AI-native extension with verifiable auditing for the AI side.
What are the three engines?
The homepage describes three components. The parallel execution engine analyzes transaction dependencies and runs conflict-free transactions concurrently. The AI-native EVM module exposes an interface that lets a contract call model inference. Zero-knowledge verifiable auditing lets a third party check an AI result without access to the model.
Where are the official channels?
The block explorer is BRTSCAN (https://devnet.bitroot.co/overview) and the protocol code is at https://github.com/brt-chain/bitroot. Community channels are X (@Bitroot_), Telegram (bitroot_official) and Discord. Treat anything not linked from bitroot.co or these channels as unofficial. People and governance are covered on the About Us and Team pages.
2. Parallel execution and performance
What does parallel EVM mean?
A standard EVM processes a block's transactions strictly in sequence. A parallel EVM runs many of them at once and still ends in exactly the state that sequential execution would have produced. The hard case is two transactions that touch the same account or storage slot. Three Paths to Parallel Execution compares the main designs.
Which parallelism approach does Bitroot use?
Optimistic concurrency control (OCC). Consensus fixes the transaction order first. Transactions then run speculatively in parallel while their read and write sets are recorded. If two overlap, only the affected transactions run again, so the result matches sequential execution. The other two common designs need something Bitroot chose to avoid: deterministic scheduling (Sealevel style) makes developers declare access lists in advance, and object models (Sui style) replace the EVM data model. See the OCC primer and Bitroot's optimistic parallelization.
What happens when two transactions conflict?
The runtime detects the overlapping read/write sets, keeps the outcome consistent with the original order, and re-executes only the transactions that were affected. Multi-stage conflict detection and dynamic grouping limit how much work a failed bet wastes, so one conflict does not discard a whole batch. State that everyone touches, such as a single popular AMM pool, still limits the speedup. Conflict Hotspots and Workloads shows how much.
What is Pipeline BFT?
It is Bitroot's consensus protocol. Classic BFT runs propose, vote and commit as sequential phases. Pipeline BFT overlaps those phases across block heights, so ordering does not wait for the previous round to finish. Leader rotation and signature aggregation keep message cost in check as validators are added. Consensus is also decoupled from execution: order is fixed first, and execution catches up to the state root for that order. Details are in Pipeline BFT and Execution Decoupling.
How should I read the 100,000+ TPS and 0.3 s figures?
As claims that depend on conditions. "TPS" can mean a laboratory peak, a sustained rate under a latency limit, or the rate observed over a time window. Those can differ by orders of magnitude, and they are often printed as a single number. For a parallel EVM the conflict rate of the test workload matters as much as the hardware. Bitroot publishes the headline figures without the full conditions, so independent measurement on the public network is the right check. A Glossary of Performance Metrics lists what any benchmark should disclose.
How do TPS, BPS, latency and finality differ?
TPS is transactions per second. BPS is blocks per second, the block production rate. Confirmation latency is the time until a transaction is included in a block. Finality is the point after which the protocol will not reverse it. A chain can raise BPS and still feel slow if conflicts pile up re-execution, so the four need to be reported separately. The glossary article defines each.
Does parallel execution speed up every application?
No. Workloads that touch mostly independent state, such as payments between unrelated users or separate mints, parallelize well. Workloads where many users hit the same contract state gain less. A transfer benchmark and a lending or AMM workload on the same chain can differ by a large factor.
How is this different from Layer 2 scaling or sharding?
They address different parts of scaling. Scaling splits into consensus, data availability, execution and settlement, and L2s, sharding, standalone DA layers and L1 parallelism each target a different part. Bitroot works on L1 execution and consensus. Mapping Blockchain Scaling places each approach on that map.
3. EVM compatibility
How compatible with Ethereum is Bitroot?
Bitroot is built to run standard EVM bytecode with standard Ethereum tooling. The phrase "EVM compatible" covers four separate layers, and migration cost depends on each: bytecode semantics, the precompile set, JSON-RPC behavior, and whether Foundry and Hardhat work unchanged. What EVM Compatibility Actually Means goes through them and explains why parallelism makes compatibility harder to keep.
Can I deploy an existing Solidity contract unchanged?
Usually. Standard Solidity contracts compile and deploy without edits unless they depend on Ethereum-specific precompile addresses. Run your own test suite on the Bitroot testnet before relying on it. The Developer Guide has the details.
Do I have to declare read/write sets or access lists?
No. Dependencies are discovered at runtime, so you write Solidity as you already do. Chains that schedule deterministically need the declaration up front.
Which wallets and tools work?
Anything that supports a custom EVM network over standard JSON-RPC: MetaMask, Rabby, OKX Wallet, Hardhat, Foundry, Remix, ethers.js and viem. The Developer Guide includes configuration for each.
What do transactions cost?
The homepage shows an average gas fee of about $0.00007, far below Ethereum mainnet. The site does not state the period or workload behind that average, so use it as an indication and estimate gas for your own batch operations.
4. AI-native features
What does AI-native mean here?
It refers to specific, checkable capabilities: optional instruction or precompile extensions through which a contract calls AI inference, hybrid execution paths, distributed compute scheduling, and a clear boundary between the settlement layer and trusted computing. What an AI-Native Blockchain Actually Needs separates engineering targets from mainnet promises.
Can a smart contract call an AI model?
That is what the AI-native EVM module is for. Conceptually it is an inference precompile that Solidity can call, with no separate oracle or off-chain relay. The interface, precompile addresses and ABI live in the protocol repository (https://github.com/brt-chain/bitroot) and are not copied onto web pages where they would go stale.
How is an AI result verified?
Through zero-knowledge verifiable auditing, which lets a third party check the computation and its output without seeing model weights. ZK proofs, trusted execution environments (TEE) and multi-party computation (MPC) each prove or assume different things and cost different amounts, and a real system combines them. Trusted Computing Framework compares them.
Does verifiable auditing replace a contract audit?
No. It shows that a computation and its result can be trusted. It says nothing about whether your own contract logic has a bug.
Do I need the AI features to build on Bitroot?
No. They are an optional extension. A standard DeFi or NFT application can use only ordinary EVM features.
Where does GPU compute fit?
The chain records jobs and payments, and the GPU work happens in a distributed compute network. Distributed GPU and Edge Compute Networks covers how such networks split and schedule work and recover from failed jobs, and what a chain should avoid promising about compute.
5. Building on Bitroot
How do I connect to the network?
Add it as a custom network in an EVM wallet using the network name, RPC URL, Chain ID, currency symbol and explorer URL shown on BRTSCAN (https://devnet.bitroot.co/overview). The Developer Guide walks through MetaMask step by step.
Why doesn't the site list the RPC URL and Chain ID?
Testnet parameters can change between upgrades, and a stale value is more likely to send you to the wrong network than to help. BRTSCAN is the authoritative source for the current values.
How do I get testnet tokens?
Submit your wallet address at the faucet, https://devnet.bitroot.co/faucet. At the average fee quoted above, one claim should cover a lot of development activity.
Are testnet and mainnet the same network?
No. RPC URL and Chain ID differ between environments, so check on BRTSCAN which one you are connected to.
How do I deploy with Hardhat, Foundry or Remix?
Point the network configuration at Bitroot and deploy as on any EVM chain. The Developer Guide has config snippets for Hardhat and Foundry and the Remix "Injected Provider" flow. After deploying, verify the source on BRTSCAN so others can read the contract and call its view functions from the explorer.
Is there a bridge?
Yes, at https://bridge.bitroot.co/.
Where should I start learning?
The Study section covers fundamentals. For parallel execution specifically, Who Should Read About Parallel EVM gives separate reading paths for contract developers, client engineers and researchers.
6. Nodes and staking
What kinds of nodes are there?
Two. Validator nodes take part in consensus, block production and verification, and need stable uptime. Compute nodes supply GPU capacity for distributed AI training and inference, and need hardware that fits the tasks they take. One operator can run either or both. See Nodes.
How does staking work?
Both roles stake BRT as collateral. A validator that double-signs or a compute node that returns bad results can lose part or all of its stake, in proportion to the violation. Nodes that behave build reputation, which affects how often they are selected and what they earn. Minimum stake, lock-up period and reward formula are in the protocol repository and official announcements, and are not hardcoded here.
Can my idle GPU join?
Yes. Home, enterprise and idle mining GPUs can take part at the capacity tier they fit. That is a stated goal of the compute node network.
How are compute tasks assigned and checked?
Assignment uses a verifiable random function (VRF), so nobody can choose who gets a task. For critical tasks the same job goes to several independent nodes, and the result is accepted only when they agree.
Can staked tokens be slashed arbitrarily?
No. Slashing applies to verifiable misbehavior, such as double-signing or returning incorrect results. Ordinary participation and occasional network problems do not trigger it.
7. Ecosystem and Foundation
What kinds of projects fit on Bitroot?
DeFi and financial infrastructure, developer tooling, AI agents and compute applications, and consumer and social apps. See Ecosystem.
How does the Bitroot Foundation support projects?
Several teams each run a grant program for one vertical, so no single body decides everything. Support covers funding, technical guidance, visibility and introductions. Current programs and application windows are on the Foundation page.
Is there a minimum bar to join the ecosystem?
There is no single gate. Being deployed on Bitroot or integrated with the protocol is generally enough, and grant eligibility varies by team and vertical.
Which projects are live?
The ecosystem page lists only projects that can be verified and updates as they launch. Partnerships that are not confirmed are left off.
8. Reading and citing this site
Where is the technical documentation?
In the Whitepaper, the Research section and the Blog. The blog has the technical series on EVM internals, parallel execution, consensus and trusted computing.
Can AI tools and crawlers read the site?
Yes. Every article is also served as plain Markdown, without navigation text, at /{locale}/blog/{slug}.md, and /llms.txt lists the main pages per language. The site is available in English, Simplified Chinese, Traditional Chinese, Japanese, Korean, Spanish and French.
How is content selected and corrected?
The Editorial Standards page describes how technical and research content is chosen, written, reviewed and corrected.
How do I reach Bitroot for press?
Use the Media Contact page. Logos and brand guidelines are on Brand Assets.
Is any of this investment advice?
No. The content is general information, not financial, investment, legal or tax advice. Performance figures are the project's stated targets or results under conditions that may not match yours.