Bitroot FAQ

1. Project basics

What is Bitroot?

Bitroot is a Layer 1 public blockchain infrastructure project. Its underlying technical approach is a high-performance parallel EVM, and it is built with a particular focus on AI + Web3 use cases.

The project aims to provide base infrastructure for high-concurrency transactions and AI applications through parallel transaction execution, Pipeline BFT consensus, AI compute infrastructure, hybrid on-chain/off-chain computing, and distributed training and inference networks.

What is Bitroot's core positioning?

Bitroot's core positioning can be summed up as: high-performance parallel EVM + AI-native infrastructure + a base network for Web3 applications.

Traditional blockchains mainly handle decentralized bookkeeping, asset ownership and smart contract execution. Bitroot goes further and brings AI compute, AI agents, AI data and model assets into the design of the public chain's infrastructure.

Why is Bitroot combining AI and blockchain?

AI and blockchain solve different problems, but they complement each other well.

• AI is better at processing information, running model computation and automating real-world tasks;
• Blockchain is better at establishing asset ownership, keeping trusted records, managing permissions and settling value.

Bitroot's technical approach is to use blockchain to address problems in AI scenarios: data ownership, turning models into assets, verifying computation, distributing incentives, and trusted interaction between AI agents and smart contracts.

How is Bitroot different from an ordinary EVM chain?

Bitroot does not simply copy the traditional EVM execution model. On top of EVM compatibility, it adds transaction dependency prediction, parallel execution, dynamic transaction grouping and dedicated AI compute capabilities.

The core goal is to keep the EVM development environment and compatibility with the Solidity ecosystem while improving execution efficiency under high concurrency.

Is Bitroot compatible with Solidity and the EVM?

Yes. Bitroot's technical approach is built on EVM compatibility and supports smart contract development in Solidity.

This means developers from the Ethereum ecosystem can migrate and build using the Solidity, wallets and smart contract workflows they already know, which lowers the barrier to building in the ecosystem.

2. Core technology

What is Bitroot's core technology?

Bitroot's current technology stack mainly includes:

1. A parallel EVM execution architecture
2. Dynamic Transaction Grouping Algorithm (D-TGA)
3. Pipeline BFT consensus
4. A hybrid PoS + PoUW consensus approach
5. Dedicated AI instructions and compute capabilities
6. Hybrid on-chain/off-chain computing
7. A distributed AI training and inference network
8. A security framework for AI agents and smart contracts
9. AI data and model asset management
10. Security and privacy technologies such as ZKP, MPC and TEE

What is Bitroot's parallel EVM?

When a traditional EVM executes transactions, many of them have to run in sequence.

Bitroot's parallel EVM analyzes the dependencies between transactions and groups those with no conflicts so they can be processed in parallel, making better use of CPU, compute and network resources.

Put simply: the traditional model is like a single-lane road where cars pass one by one. A parallel EVM looks at where each car is heading and how the cars relate to each other, then assigns cars that can travel at the same time to different lanes.

What is D-TGA?

D-TGA stands for Dynamic Transaction Grouping Algorithm.

Its core job is to analyze the dependencies between transactions and dynamically group the ones that can run in parallel, enabling more efficient instruction-level parallel execution.

It is an important part of Bitroot's parallel EVM architecture.

What is Bitroot's Pipeline BFT?

Pipeline BFT is one of the consensus mechanisms in Bitroot's technology stack.

Its basic flow is: PROPOSE → PREVOTE → PRECOMMIT → COMMIT

Compared with traditional consensus, Pipeline BFT is designed so that processing across multiple block heights forms a pipeline, which reduces consensus waiting time and improves the network's overall throughput.

Parameters given in the technical materials include a 400ms block interval and a 200ms Prevote timeout.

Does Bitroot use PoS?

Bitroot's technical materials propose a hybrid PoS + PoUW consensus approach.

PoS mainly relates to network security, node participation and the staking mechanism. PoUW aims to tie part of the network's useful computing power to AI compute tasks.

The final mainnet parameters and economic model are subject to the official rules published at launch.

What is PoUW?

PoUW stands for Proof of Useful Work.

Traditional proof of work focuses on the computation itself. Bitroot's technical approach aims to go further and explore putting compute resources to work on tasks with real-world use, such as AI training and inference.

The design direction of PoUW, then, is for the network's compute resources not only to maintain consensus but also to serve real computing demand.

3. AI infrastructure

Why does Bitroot emphasize being "AI-native"?

Bitroot is not just deploying a few AI applications on a public chain. It considers AI use cases starting from the base architecture.

This covers:

• AI compute;
• AI models;
• AI data;
• AI agents;
• Distributed training;
• Distributed inference;
• Verification of AI computation;
• Interaction between AI and smart contracts.

The project's direction is therefore to build Web3 infrastructure that can carry AI applications.

How does Bitroot support AI compute?

The technical approach is mainly: the chain handles trusted verification and state management, and heavy computation happens off-chain.

Compute tasks such as AI model training and inference can be completed by a distributed compute network, while the chain records task information, verification results and related state.

This avoids running every large AI computation directly on the blockchain.

What is hybrid on-chain/off-chain computing?

Put simply: complex computation happens off-chain, and high-value results are verified on-chain.

For example, when an AI agent starts a compute task:

1. A smart contract creates the task;
2. The task is sent to the off-chain AI compute network;
3. Nodes complete the computation;
4. The result and verification data are returned;
5. The chain verifies them;
6. Once verified, the corresponding smart contract logic runs.

This approach balances the trustworthiness of blockchain with the efficiency of AI computation.

Can Bitroot support AI agents?

Yes.

Bitroot's technical design takes into account the interaction between AI agents and smart contracts, including:

• Agent identity;
• Permission control;
• Verification of compute results;
• TEE;
• Cross-verification across multiple nodes;
• Consensus among multiple agents;
• Standard smart contract interfaces.

The goal is for AI agents to be more than chat tools: intelligent actors that can be verified, granted permissions, and interact with on-chain assets and contracts.

How does Bitroot address data and copyright issues for AI models?

The project's technical approach proposes turning AI into assets.

This includes:

• Data as assets;
• Models as assets;
• Records of model ownership;
• Data licensing;
• Model invocation;
• Revenue distribution;
• On-chain auditing.

In short, the aim is to give AI data, models and how they are used clearer on-chain records and permission management.

How does Bitroot protect AI models?

The technical materials propose an approach that includes MPC, TEE, model sharding, threshold keys and zero-knowledge proofs.

For example, model weights can be split using secret sharing, with different nodes holding different shares, so they can take part in computation without exposing the full model parameters directly.

The goal is to address model privacy, computational security and result verification at the same time.

4. Performance and TPS

What is Bitroot's TPS?

The project's technical materials put forward a 100,000+ TPS target / performance figure, and separate technical test materials give results under different test environments.

So in public communication it needs to be clear that 100,000+ TPS is a project performance figure and cannot simply be equated with the mainnet's actual TPS at any given moment.

Public chain performance should be broken down into:

1. Theoretical architectural capacity;
2. Lab / stress test results;
3. Measured results on specific hardware;
4. The mainnet's current actual TPS.

Why can't you go by a single TPS number?

Because TPS is affected by many factors.

These include:

• Hardware environment;
• Number of nodes;
• Number of shards;
• Transaction types;
• Block gas limit;
• Block utilization;
• Network load;
• Test methodology.

So when comparing public chain performance, the question is not "whose TPS number is bigger" but how much each can actually process under the same test conditions.

What data do Bitroot's technical tests show?

Existing technical materials give test results on AWS c6i.32xlarge instances:

• About 3,200 TPS on a single shard
• About 25,600 TPS on 8 shards
• Confirmation latency of about 1.2 seconds

The project materials also put forward an overall performance figure of 100,000+ TPS.

These figures come from different test environments and technical stages, and marketing staff should not treat them as a single test result.

Why do project materials mention 0.3 seconds, 1.2 seconds and 100,000+ TPS at the same time?

Because these metrics measure different things.

• 0.3 seconds: the block production / confirmation speed figure in the project materials;
• 1.2 seconds: the confirmation latency measured in a specific AWS test environment;
• 100,000+ TPS: the overall performance figure put forward by the project.

The most professional way to answer is not to blend the three numbers into one figure, but to state the test environment, test method and metric definition for each.

After the official mainnet launch, the official unified performance report and actual on-chain data should be the final reference.

Monad also uses parallel execution, so why might its observed TPS be far below 10,000?

That is exactly why network architecture performance and actual network load need to be kept apart.

Take the Monad mainnet measurements currently available:

• Block time is about 240ms;
• A sample of consecutive blocks averages about 12.4 transactions per block;
• Converted using block speed, the sample's actual throughput is on the order of a few dozen TPS.

This does not show that Monad's parallel execution capability does not exist. It shows that the mainnet's current actual TPS depends on real transaction demand and block utilization.

For the same reason, Bitroot should publish both stress test data and actual mainnet load data in the future, not just its peak TPS.

Why might Scroll's TPS also be low?

Scroll is not positioned quite the same way as Bitroot or Monad.

Scroll's core approach is a zkEVM Layer 2, focused on zero-knowledge proofs, Ethereum scaling and EVM compatibility.

In the Scroll mainnet data currently available, when actual transaction volume is low, the converted TPS can also be very low.

This further shows that "current mainnet TPS" and "theoretical network capacity" are two different metrics.

So how should Bitroot be compared with Monad and Scroll?

Comparing a single TPS number is not recommended. They can be compared along these dimensions:

• Bitroot: network type is Layer 1; EVM compatible; core direction is parallel EVM + AI; execution follows a parallel execution approach; AI infrastructure is a core direction; key metrics are parallel execution, AI compute and scalability, and actual TPS should be read alongside mainnet load.
• Monad: network type is Layer 1; EVM compatible; core direction is parallel execution; execution is parallel; AI infrastructure is not a core focus; the key metric is high-performance execution, and actual TPS should be read alongside mainnet load.
• Scroll: network type is Ethereum Layer 2; uses a zkEVM; core direction is ZK scaling; execution happens on L2; AI infrastructure is not a core focus; key metrics are ZK proving and Ethereum scaling, and actual TPS should be read alongside mainnet load.

What Bitroot really needs to prove, then, is not just "a bigger number" but that its architecture, testing, mainnet load and ecosystem applications form a complete, closed loop of data.

If someone says "this chain's actual TPS is only a few dozen, so its 10,000 TPS is fake", how should you respond?

You can say:

"You need to separate theoretical network performance, stress test performance and the mainnet's current actual load. Current mainnet TPS reflects the network's actual transaction demand right now, while a stress test reflects what the network can handle under specific conditions. The two are not equivalent. A meaningful comparison needs the same hardware, transaction types, block utilization and test methodology."

The same standard applies to Bitroot.

5. Testnet

What is Bitroot's current testnet called?

The test network is called: Bitroot Devnet

What is the Bitroot Devnet Chain ID?

Chain ID: 15881

What is the testnet RPC?

Official testnet RPC: https://dev-rpc.bitroot.co

Does the testnet have a faucet?

Yes.

Testnet faucet: https://devnet.bitroot.co/faucet

Under the current test rules, each address can claim test BRT once every 24 hours, 0.1 BRT per claim.

Where is the testnet explorer?

Bitroot Devnet Explorer: https://devnet.bitroot.co/

You can use it to look up wallet balances, transaction history, transaction hashes and other information.

What can you do on the testnet?

The testnet currently supports:

• Connecting a wallet;
• Claiming test BRT;
• Transferring BRT;
• Looking up blocks and transactions;
• DEX swaps;
• Adding / removing liquidity;
• Testing the cross-chain bridge;
• Cross-chain asset tests between Bitroot and the BSC testnet.

Is there a DEX on the testnet?

Yes.

Testnet DEX: https://crus.finance/#/home

You can currently swap between BRT and test assets and test liquidity features.

Is there a cross-chain bridge on the testnet?

Yes.

Testnet bridge: https://dev-bridge.bitroot.co

It is currently used mainly to test cross-chain asset transfers between the Bitroot test network and the BSC test network.

What is ETK on the testnet?

ETK is an asset in the test environment, used for DEX, liquidity and cross-chain testing.

ETK contract on the Bitroot chain: 0xada4b7fe868d334c92eb8bdaec555685905c5fa5

ETK contract on BSC: 0xe1F62a5615E51B80e1d83f4E4d51a3F969fa2589

What is the testnet TTA contract?

0x4446FB54FC94F78e1589EA07E20EF6AE8a771Ce8

Contract addresses in the test environment are subject to the latest official testnet documentation.

6. Mainnet

What stage is the Bitroot mainnet at?

Bitroot has been continuously building and testing its mainnet architecture, parallel EVM, consensus, AI infrastructure and ecosystem applications.

For the official mainnet launch date, final network parameters and official operating status, Bitroot's latest official announcements are the final reference.

What will the mainnet mainly address after its official launch?

The main goals include:

• Improving execution efficiency for high-concurrency transactions;
• Providing a compatible environment for EVM developers;
• Supporting AI applications;
• Supporting hybrid on-chain/off-chain computing;
• Supporting AI data and model assets;
• Building node and compute networks;
• Hosting Web3 applications such as DeFi, AI and payments.

Why does Bitroot need its own Layer 1?

Because the project wants to address performance, AI compute and Web3 application infrastructure at the level of the base network.

Relying entirely on another chain would mean AI compute, the execution model, node incentives and the underlying network architecture are all constrained by that chain's design.

Building its own Layer 1 lets Bitroot design the consensus, execution, storage and compute layers as a whole.

7. The BRT token

What is BRT?

BRT is the core token of the Bitroot network ecosystem.

Its functions are designed mainly around:

• Network gas;
• Node participation;
• Staking;
• Ecosystem incentives;
• Community incentives;
• AI / compute ecosystem incentives;
• Network governance and future ecosystem applications.

The final mainnet tokenomics are subject to the official release.

What is the total supply of BRT?

Existing project materials show a total BRT supply of 200 million tokens.

Specific allocation, lock-ups, burns and actual circulating supply are subject to the latest official tokenomics data.

Why do different circulating supply figures for BRT appear in the market?

Because materials from different stages of the project cover node lock-ups, staking, burns and circulation statistics taken at different points in time.

So in public communication, it is not advisable to treat any single historical figure as a permanent circulating supply.

The latest official tokenomics and verifiable on-chain data are the final reference.

How can you obtain BRT?

Under the current ecosystem design, the main ways to obtain BRT include:

• Legal and compliant channels such as secondary markets / OTC;
• Ecosystem campaigns;
• Node participation;
• Community and ecosystem incentives;
• Future rewards for contributing to the network.

The available channels may change from stage to stage; the latest official announcements take precedence.

8. Staking

Why does Bitroot have a staking mechanism?

The staking mechanism is mainly used to:

• Increase engagement among ecosystem users;
• Encourage long-term lock-ups;
• Build a mechanism for community contribution;
• Build up participants for the future node ecosystem;
• Link token holding with ecosystem contribution.

Does Bitroot currently have staking campaigns?

There are ecosystem staking and points campaigns.

The current entry point is the official campaign page: campaign.bitroot.co

What do you mainly get from staking?

The staking system currently rewards participants mainly through points / power scores, ecosystem rewards and campaign benefits.

Rules may be adjusted between campaign stages, so the reward parameters of any one stage should not be read as permanent rules.

How do staking periods usually work?

The staking system currently offers a choice of terms. The general logic is that the longer the lock-up, the higher the points weighting usually is.

Specific terms, multipliers and reward rules are as shown on the current campaign page.

Does staking pay a fixed return?

No.

Points, rewards, rankings and ecosystem benefits in staking campaigns are all specific campaign rules and should not be read as a fixed return or a promise of returns.

Can you exit early during staking?

Rules differ between staking products and campaign stages. Exiting early may mean points stop accruing, rewards are reduced, or rules apply to your principal.

So before taking part, check the specific rules on the current campaign page.

9. Nodes

Why does Bitroot need nodes?

Nodes are an essential part of any public chain's infrastructure.

Bitroot's node system handles network validation, and over time it is also intended to connect with these ecosystem directions:

• AI compute;
• Distributed training;
• Distributed inference;
• Edge computing;
• Physical AI hardware.

Where do Bitroot node rewards come from?

The node incentive sources proposed in the project materials include:

• Network fees;
• Block rewards;
• Ecosystem incentives;
• Compute contributions, among others.

Actual rewards depend on how the mainnet actually runs, the node rules, network transaction volume and how the ecosystem develops.

Do nodes earn a fixed monthly income?

Node rewards should not be read as fixed income.

The project materials include reward estimates based on specific conditions, but those figures are model-based or stage-specific projections, not guaranteed returns.

Once the mainnet is officially running, actual on-chain revenue and the official node economic model take precedence.

What is the core value of running a node?

The core value of a node is not only the rewards; more importantly, it is taking part in Bitroot's network infrastructure.

As ecosystems such as AI compute, edge computing and physical AI develop, nodes have the opportunity to become key infrastructure linking "network validation + compute resources + the AI ecosystem".

10. Ecosystem

Which ecosystem directions is Bitroot focusing on?

The current ecosystem directions mainly include:

1. AI applications;
2. DeFi;
3. AI agents;
4. AI data and model assets;
5. Tokenization of real-world assets such as gold;
6. Distributed storage;
7. On-chain payments;
8. Distributed computing;
9. Physical AI;
10. Edge computing.

Why does Bitroot care about physical AI?

The next stage of AI will not only happen on computers and phones. It will also move into robots, smart devices, autonomous driving and real physical spaces.

These scenarios need:

• Large amounts of real physical data;
• Low-latency edge computing;
• Distributed computing power;
• Hardware nodes;
• Incentives for contributing data.

Bitroot hopes to connect these real-world resources through Web3 node and incentive mechanisms.

What is Bitroot's distributed edge computing?

Simply put, it means placing compute resources as close as possible to where they are actually used.

For example:

• Smart hardware;
• Robots;
• Charging equipment;
• AI compute boxes;
• Other edge computing devices.

In the future these devices could become network nodes, providing low-latency compute for AI and physical devices.

What is the relationship between Allindoge and Bitroot?

Allindoge AI is one of the AI application directions in the Bitroot ecosystem.

Bitroot leans toward base infrastructure, while applications such as Allindoge AI can serve as use cases on top of it, offering users actual AI products and services.

You can think of it this way: Bitroot provides the base network, and ecosystem applications handle specific products and user scenarios.

11. Team

What is the technical background of the Bitroot team?

Project materials show that Bitroot's technical R&D team has a background in the BCH ecosystem, and has also brought in AI, blockchain, security and other R&D staff.

R&D has continued since earlier stages and has gradually produced a technology stack including the parallel EVM, Pipeline BFT and AI compute.

Who is on Bitroot's core management team?

Existing project materials disclose:

• CEO: Juan
• COO: Stephen

Team members come from different regions, and the project is also building overseas community, developer and ecosystem partnerships.

For team members' specific backgrounds and public information, the latest official disclosures take precedence.

Why does Bitroot emphasize being global?

Public chains are global by nature.

Bitroot's current ecosystem building spans:

• Asia;
• Europe;
• The Americas;
• Africa;
• Developers and communities worldwide.

Competition among public chains in the future will not only be about technology, but also about developers, applications, communities, nodes and real-world industry resources.

12. Security and risk

How can you spot fake BRT?

This is something the market currently needs to watch closely.

Users should not judge whether a token is genuine based only on:

• The token name;
• The logo;
• Group chats;
• Private messages;
• An address supplied by an OTC counterparty.

For contract addresses, trading channels and official campaigns, verify through Bitroot's official channels first.

Could fake Bitroot tokens appear?

Any popular blockchain project can attract counterfeit tokens.

So seeing "BRT" does not necessarily mean it is genuine Bitroot BRT.

Always check the official contract address and official channels.

Why does OTC trading exist in the market today?

At different stages of a project, token liquidity and trading channels may differ.

OTC trades are transactions between participants. You need to judge the counterparty and the authenticity of the asset yourself and bear the associated risk.

The project will not guarantee anyone's trading profits because of an OTC trade.

Will Bitroot guarantee the BRT price?

No.

The market price of BRT is determined by many factors, including supply and demand, liquidity, ecosystem development, network usage and the overall market environment.

No individual or community member should guarantee a future price.

Will Bitroot guarantee node rewards?

No.

Node rewards depend on how the network actually runs, fee revenue, block rewards, the number of nodes, ecosystem contributions and other factors.

No fixed reward figure should be read as an official promise of returns.

13. Questions the market asks most

What is Bitroot's biggest technical highlight?

In one sentence: Bitroot's core technical direction is to use a parallel EVM as the base execution architecture and to bring AI compute, AI agents, AI data and model assets into public chain infrastructure.

What is Bitroot's biggest ecosystem direction?

The core direction is AI + Web3 + physical AI.

That means extending from AI applications in the digital world to data, compute, models, smart devices and real physical spaces.

Why build a public chain instead of just an AI app?

A single AI app mainly serves one specific user scenario, while a public chain solves more fundamental problems.

Bitroot aims to provide compute infrastructure + asset infrastructure + data infrastructure + AI agent infrastructure.

In the future, different teams can build their own AI and Web3 applications on the base network.

How is Bitroot different from Solana?

Both prioritize high performance, but their technical approaches and ecosystem focus differ.

Solana focuses on a high-performance Layer 1 and its application ecosystem; Bitroot's core technical direction is parallel EVM + AI infrastructure.

For developers, one important feature of Bitroot is that it stays EVM / Solidity compatible.

What is Bitroot's relationship with Ethereum?

Bitroot is not an Ethereum Layer 2. It is an independent Layer 1 public chain.

But Bitroot stays EVM / Solidity compatible at the level of execution environment and development language, which lowers the barrier for Ethereum developers to move to Bitroot.

How is Bitroot different from Monad?

Both Monad and Bitroot involve a high-performance EVM and a parallel execution approach.

The difference: Monad focuses on being a high-performance EVM Layer 1, while Bitroot goes further and makes AI compute, AI agents, AI data and model assets its core ecosystem directions.

So the two can be compared on base execution performance, but they should not be treated as the same kind of project.

How is Bitroot different from Scroll?

The two are positioned differently as networks.

• Bitroot: an independent Layer 1, parallel EVM + AI infrastructure;
• Scroll: an Ethereum Layer 2 whose core technical direction is zkEVM and zero-knowledge proof scaling.

So beyond EVM compatibility, their underlying architectures and target scenarios differ clearly.

14. Ecosystem incentives and community

Why does Bitroot have a community ambassador program?

Building a public chain ecosystem takes technical developers, application developers, node operators, content creators and community members working together.

The community ambassador program mainly covers:

• Community building;
• Educating new users;
• Spreading content;
• Product testing;
• Ecosystem campaigns;
• Expanding into overseas markets.

What is the value of community contributions?

Bitroot's ecosystem incentives are not only about funding and tokens. The aim is to gradually bring different kinds of contribution into the ecosystem: users, content, development, testing, nodes, hardware and compute resources.

So community members will be able to take part in building the ecosystem in different ways.

Why does the testnet also have tasks and incentives?

The testnet's core purpose is to help the project find problems, test features and gather real usage data.

So the testnet is not just "click once and you're done". It is an important stage where developers and the community test the network together.

15. Mystery boxes and campaigns

Why does Bitroot have mystery boxes?

Mystery boxes are part of the ecosystem campaigns and incentive mechanisms, used mainly to increase community participation and ecosystem interaction.

Depending on the stage, they may contain:

• BRT;
• Points;
• USDT;
• NFTs;
• Physical rewards;
• Campaign eligibility;
• Ecosystem benefits, among others.

Specific rewards and rules are as shown on the current campaign page.

Are mystery boxes an investment return?

No.

Mystery boxes are an ecosystem incentive campaign and should not be read as a fixed-return product.

16. Standard answers to common criticisms

If someone says "Bitroot is just a slide deck with no technology", how should you respond?

Don't argue. You can simply say:

"Bitroot's technical approach is more than a concept. It already has technical designs for the parallel EVM, D-TGA, Pipeline BFT, AI compute and hybrid on-chain/off-chain computing, and it is testing the network, a DEX, cross-chain transfers and other features on Devnet. For any public chain project, the final judgment should still come down to code, test data, mainnet operation and real ecosystem applications."

If someone says "100,000 TPS is an exaggeration", how should you respond?

You can say:

"100,000+ TPS is a performance figure the project has put forward, but looking at public chain performance professionally means not relying on a single number. We care more about the test environment, transaction types, number of shards, block utilization and actual load after mainnet launch. Bitroot should also verify this performance figure with ongoing public testing and mainnet data."

This answer is more professional than simply insisting "we do 100,000 TPS".

If someone points to Monad's few dozen TPS to question every high-performance chain, how should you respond?

You can say:

"Actual TPS reflects the network's current load, not its theoretical ceiling. If a highway has only a few dozen cars on it right now, that does not mean it can only carry a few dozen cars. What matters is how many transactions it can process under unified test conditions, and whether the mainnet runs stably once real demand arrives."

What if someone asks "When will Bitroot definitely succeed?"

No guarantee can be given. You can say:

"A public chain's ultimate value depends on whether its technology is delivered, whether the mainnet runs stably, whether developers keep arriving, whether applications create real demand, and whether the ecosystem forms a positive cycle. Bitroot's current focus is delivering its technology and ecosystem step by step."

What if someone asks "What will BRT be worth later?"

Standard answer:

"Neither the project nor the community can determine BRT's future price in advance. We care more about the network technology, mainnet operation, ecosystem applications, real users and on-chain usage."

What if someone asks "Is now the best time to buy BRT?"

Do not make buy calls for individuals. You can say:

"Whether to participate depends on your own risk tolerance, your understanding of the project's technology and ecosystem, and your own financial situation. What the project can offer is public information about its technology, products, ecosystem and network data."

17. Core talking points

How do you introduce Bitroot in 30 seconds?

Bitroot is a Layer 1 public chain whose underlying technical approach is a high-performance parallel EVM, with AI + Web3 as its core direction. Through parallel transaction execution, Pipeline BFT, AI compute, hybrid on-chain/off-chain computing, and distributed training and inference, the project aims to address infrastructure for high-concurrency transactions and AI applications. Bitroot is also expanding into AI agents, AI data assets, physical AI and distributed edge computing, with the goal of building base infrastructure for the next stage of Web3 and AI applications.

How do you introduce Bitroot in one sentence?

Bitroot = parallel EVM Layer 1 + AI-native infrastructure + a Web3 application ecosystem.

What should the market remember most about Bitroot?

Not just "100,000 TPS", but three keywords: parallel EVM, AI infrastructure, real ecosystem delivery.

Performance is the foundation, AI is the direction, and ecosystem applications and mainnet data are the final proof.

18. Principles for marketing staff

What is the most important principle when promoting Bitroot?

Stick to four principles:

1. Don't exaggerate. Don't present project plans as already completed.
2. Don't promise. No promises on price, fixed returns or fixed node rewards.
3. Use data. For TPS, mainnet, nodes, circulating supply and similar topics, state the data source and test environment wherever possible.
4. Think long term. Don't only talk about short-term price; talk about technology, mainnet, developers, applications and real users.

What is Bitroot's core value proposition?

It can be summed up as one complete chain:

• Parallel EVM → higher execution efficiency;
• AI infrastructure → carrying AI applications;
• Distributed computing → supplying compute;
• AI data / models as assets → a digital asset system;
• AI agents → linking intelligent applications with smart contracts;
• Physical AI → entering the real world;
• Nodes and ecosystem incentives → a mechanism for network participation.

The end goal is for Bitroot to be more than a "transaction chain": base infrastructure for AI and Web3 applications.

19. Official entry points

What are the Bitroot testnet entry points?

• Devnet RPC: https://dev-rpc.bitroot.co
• Faucet: https://devnet.bitroot.co/faucet
• Explorer: https://devnet.bitroot.co/
• DEX: https://crus.finance/#/home
• Bridge: https://dev-bridge.bitroot.co

Where is the staking campaign entry point?

The current official staking campaign entry point: campaign.bitroot.co

Specific staking terms, points, rewards and campaign rules are as shown in real time on the current page.

What should you do if you run into problems with BRT, the testnet or a campaign?

Verify through Bitroot's official channels first, and do not trust:

• Private "customer support";
• Unofficial group admins;
• Contracts sent in private messages;
• Unconfirmed airdrop links;
• Unconfirmed OTC addresses;
• Websites impersonating the official site.

When handling assets, double-check contract addresses and website domains in particular.

20. The standard market summary

So what exactly is Bitroot?

Bitroot is a Layer 1 public chain infrastructure project with a parallel EVM as its core technical approach and AI + Web3 as its main direction.

Why is Bitroot worth watching?

What makes Bitroot worth watching is not a single TPS number, but its attempt to combine a high-performance EVM, AI compute, AI agents, AI data and model assets, distributed computing and physical AI into a complete technical and ecosystem roadmap that runs from the base public chain up to AI applications.

Will Bitroot ultimately succeed?

Every public chain project ultimately has to prove itself through real network operation, developer numbers, application numbers, user activity, on-chain transactions, node participation and commercial adoption.

Bitroot's core task right now is to keep completing technical validation, mainnet construction and ecosystem delivery.

How should the market view Bitroot's 100,000+ TPS?

100,000+ TPS is a high-performance figure the project has put forward. Judging public chain performance professionally means looking at architectural design, stress tests, hardware conditions, transaction types, block utilization and actual mainnet data together. What will really be convincing from Bitroot is not just stating a TPS number, but continually proving the network's actual capacity with public testing and mainnet data.

What is Bitroot ultimately trying to build?

Bitroot's long-term direction is to use a parallel EVM Layer 1 as the foundation and connect AI compute, AI agents, AI data and model assets, distributed compute and physical AI, building base infrastructure for the next stage of Web3 and AI applications.

Where should a newcomer start with Bitroot?

Newcomers don't need to learn every technical detail up front. They can get to know Bitroot step by step in this order: "learn about the project → try the testnet → get familiar with the ecosystem → learn about BRT → get more deeply involved". Try it first, then judge: that is a sensible way to participate.

How can an ordinary newcomer take part in Bitroot?

Ordinary users can take part by trying the testnet, trying ecosystem products, joining community campaigns, contributing content and completing ecosystem tasks. Bitroot does not require everyone to have technical skills; users can choose the kind of participation that suits their interests and abilities.

Do newcomers have to buy BRT to take part?

No. Basic ways of taking part, such as learning about the project, joining the community and trying the testnet, do not require newcomers to buy BRT first. For users who are new to Bitroot, it is better to learn and try things out first, then decide whether to get more deeply involved.

Can someone with no blockchain knowledge at all take part in Bitroot?

Yes. Newcomers can start by learning basic concepts such as wallets, public chains, gas, DApps and smart contracts, then gradually learn about Bitroot's technology and ecosystem. Participation in the Bitroot ecosystem is not only for developers.

What can newcomers do once they are on the testnet?

Newcomers can try connecting a wallet, transferring test BRT, the block explorer, the DEX, the cross-chain bridge and other testnet applications, and learn how the Bitroot network basically works through hands-on use.

21. Getting started and ways to take part

What can ordinary users mainly do with Bitroot?

Ordinary users can try the testnet and ecosystem products, help build the community, create content, complete campaign tasks and use ecosystem applications. For newcomers, the point is not simply to finish tasks, but to gradually understand Bitroot's technology and ecosystem by taking part.

How can people with technical skills take part in Bitroot?

Technical users can focus on areas such as Solidity, the EVM, DApps, smart contracts, AI agents, AI model invocation and on-chain data, and take part in building the Bitroot ecosystem by developing and deploying real applications.

Can people with GPUs or compute resources take part?

They can look closely at Bitroot's distributed computing and AI compute direction. Bitroot's technical approach involves distributed training, distributed inference and an AI compute network. Whether compute resources will see sustained demand in the future still needs to be verified through actual network usage.

Besides chatting, what else can community members do?

Truly valuable community contributions go beyond chatting. Members can help educate newcomers, create content, test products, organize events, connect developer resources, promote ecosystem projects and build the community.

In what order should newcomers get involved with Bitroot?

Put simply: first learn about the project, then try the testnet, then get familiar with the ecosystem. Once you genuinely understand the project, choose a deeper form of participation that fits your abilities, such as community, development, nodes or compute.

Is taking part in Bitroot just buying BRT and waiting for it to go up?

That is not the right way to see it. What matters more for Bitroot's long-term development is the network, users, developers, applications and real transaction demand. BRT is an important part of the ecosystem's economic system, but the value of the project itself still has to be proven through real network usage.

22. BRT and market perception

What role does BRT play in the Bitroot ecosystem?

BRT is one of the core tokens in the Bitroot network's economic system. Its uses and forms of participation cover network gas, nodes, staking, ecosystem incentives and other network application scenarios. Specific use cases will keep being refined as the mainnet and ecosystem develop.

What should you mainly look at when judging BRT's value?

Beyond the market price, look more at whether the Bitroot network sees real usage, including user numbers, transaction volume, developer numbers, DApps, nodes, compute and ecosystem applications. In the long run, real network demand is an important basis for understanding BRT's value.

Why shouldn't newcomers look only at BRT's price?

Because the token price is only one part of market performance. For a public chain project, it matters more whether the technology, users, developers, applications, transactions and ecosystem keep developing. Only as these factors gradually build network effects does the project's long-term value case become clearer.

Will BRT definitely go up in the future?

No one can guarantee a future price. A more reasonable approach is to keep watching Bitroot's mainnet, users, ecosystem, applications, transaction volume and the actual network demand for BRT.

Why does the market pay attention to Bitroot's BRT?

The core reason the market pays attention to BRT is its link to the development of the Bitroot network and ecosystem. As users, applications, nodes, compute and on-chain activity grow, the market will keep watching the actual demand for BRT within the network's overall economic system.

23. Market expectations for Bitroot's future

Where do the market's expectations for Bitroot's future mainly come from?

The market's long-term expectations for Bitroot come mainly from its technical approach and room for ecosystem growth, including the parallel EVM, AI-native capabilities, AI agents, AI data and model assets, distributed compute and physical AI. Whether those expectations are ultimately met has to be continually verified through real users, developers, applications and network data.

Where is Bitroot's biggest long-term potential?

Bitroot's core potential is not just building a high-performance public chain, but trying to connect blockchain, AI, compute, data, models and AI agents. If these directions create real demand, Bitroot's infrastructure value and ecosystem have room to grow further.

Why is Bitroot focusing on AI?

AI is creating new demand for compute, data, models and intelligent agents. Through technical directions such as the parallel EVM, AI-native capabilities, distributed computing and AI agents, Bitroot hopes to provide blockchain infrastructure better suited to future AI applications.

What is Bitroot's long-term development logic?

Bitroot's long-term logic can be summed up as "technology → users → ecosystem → network value". First validate the underlying technical capability, then attract developers and users, then build real applications and network usage, and finally prove the project's long-term value through sustained ecosystem demand.

How should the market judge whether Bitroot has long-term room to grow?

Watch five things: whether the technology is stable, whether users are growing, whether developers keep arriving, whether applications are actually delivered, and whether the network generates sustained real demand. These indicators are more meaningful than market hype alone.

If Bitroot develops well, what will the market focus on?

The market is likely to focus more on mainnet stability, active users, on-chain transactions, developer numbers, DApp quality, AI applications, compute scale, ecosystem funding and actual demand for BRT. In the end, the project has to prove its network value through this real data.

24. Common newcomer questions

Do newcomers need to watch the BRT price every day?

No. For newcomers to Bitroot, it is more important to first understand the project's technology, ecosystem and progress. Price is market performance, while the project's technology and ecosystem building are the longer-term things to watch.

Which data should newcomers focus on?

Focus on how the mainnet is running, real transaction volume, active addresses, developer numbers, the number of DApps, node count, compute scale and how much ecosystem applications are used. Use data to understand how the project is developing, not just community sentiment.

Why do some people in the community say BRT will definitely rise a lot?

Community members can have their own market views, but a personal view is not an official project promise. Newcomers should distinguish between project facts, personal opinions, market expectations and investment decisions, and should not take anyone's personal prediction as a certain outcome.

Someone says they have inside information about Bitroot. Should you believe them?

For important information about BRT, airdrops, nodes, private sales, exchanges or campaigns, verify through official channels first. So-called "inside information" that has not been officially confirmed should not be the basis for any important decision.

Why do some people end up buying fake BRT?

The crypto industry can have tokens with the same name, fake websites and fake contracts. So before trading, always check the officially published contract address, network and block explorer information. Do not judge authenticity from the token name, logo or unfamiliar links alone.

How can newcomers avoid being scammed?

Most importantly: never give anyone your seed phrase or private key, don't connect to unfamiliar websites, don't approve unknown contracts, and don't believe in so-called guaranteed returns or inside information. When moving funds, confirm the information through official channels.

Does taking part in the testnet guarantee future rewards?

That is not the right way to see it. The testnet's core purpose is to test the network, try products, find problems and take part in building the ecosystem. Any points, rewards or later benefits are subject to the official rules the project ultimately publishes.

Is staking a fixed-income product?

It should not be seen as a fixed-income product. Staking involves project rules, network development, token price, the market environment and other factors. The specific mechanism and rewards are subject to the current official rules.

Is running a node a sure profit?

No. Running a node involves token lock-ups, network operation, operating costs, market volatility and protocol rules. No node reward should be seen as risk-free or fixed income.

25. Understanding Bitroot's technology as a newcomer

Why does Bitroot emphasize the parallel EVM?

Transaction execution in a traditional EVM involves a lot of serial processing. The core idea of a parallel EVM is to identify the dependencies between transactions and process those without conflicts in parallel, improving the network's overall execution efficiency.

What is the relationship between AI and Bitroot?

Bitroot wants AI to be more than an application on a blockchain: it wants AI to reach into the underlying layers of execution, compute, data, models and intelligent agents, creating a deeper integration of AI and blockchain infrastructure.

Why do AI agents need a blockchain?

If an AI agent needs to use assets, execute transactions, access data and interact with other smart contracts on its own, it needs trusted identity, permissions, asset settlement and an execution environment. Bitroot hopes to provide these capabilities to AI agents through blockchain infrastructure.

Why can AI data and models become on-chain assets?

AI's core resources are not only the models themselves, but also training data, model weights, access rights and the revenue they generate. Bitroot's technical approach aims to give data and models clearer digital asset properties through on-chain ownership, licensing, verification and settlement.

26. How the market should understand Bitroot's performance

How should Bitroot's 100,000+ TPS be understood?

100,000+ TPS is a high-performance figure the project has put forward. It should not be read as the mainnet running continuously at 100,000 TPS at all times. Judging public chain performance professionally requires looking at the test environment, hardware configuration, transaction types, concurrency conditions, block utilization and actual mainnet data together.

Why do some chains advertise very high TPS while their actual TPS is much lower?

Because theoretical performance, lab benchmarks, testnet stress tests, peak mainnet TPS and average mainnet TPS are different concepts. When judging performance, the test environment and test method need to be stated; a single TPS number cannot simply be equated with everyday mainnet usage.

If Bitroot achieves high performance, what would that really mean?

High performance on its own is only a baseline capability. What it really means is being able to carry more users and more complex applications. If use cases such as AI agents, DeFi, high-frequency trading, AI data and compute generate large amounts of on-chain interaction, the value of high-performance infrastructure will become more apparent.

Why can't different chains be compared on TPS alone?

Because different chains may differ in architecture, hardware, transaction types, consensus mechanisms and test methods. A professional comparison should consider TPS, block time, finality, cost, concurrency, block utilization and real mainnet load together.

27. Community communication for newcomers

What should newcomers pay attention to after joining the Bitroot community?

Focus on official announcements, technical progress, mainnet progress, testnet updates, ecosystem applications, developer events and on-chain data. Newcomers should gradually build their own ability to assess information instead of relying only on second-hand information from group chats.

What is the simplest one-sentence way for a newcomer to introduce Bitroot?

Bitroot is a Layer 1 project that has a parallel EVM as its core technical approach and AI + Web3 as its main direction, and is trying to build AI-native blockchain infrastructure.

How do you explain Bitroot to someone who knows nothing about blockchain?

Put simply: Bitroot wants to build blockchain infrastructure for the AI era, so that blockchains can handle not only assets and transactions but also serve applications such as AI agents, AI data, models and distributed computing.

What community content is actually valuable?

Truly valuable content centers on technical progress, product experience, ecosystem applications, developer building, user education and real data, rather than simply creating price expectations or spreading unverified information.

28. The final market answers

What does Bitroot ultimately need to prove?

What Bitroot ultimately needs to prove is not just "whether it can reach high TPS", but whether it can turn a high-performance EVM, AI-native capabilities and distributed computing into steadily growing real users, real applications and real network demand.

How do Bitroot's technology, AI and ecosystem relate to each other?

Put simply: the parallel EVM is the underlying technical foundation, AI is the core direction, AI agents are the application form, data and models are a new direction for digital assets, distributed compute provides the computing resources, and ecosystem applications are the real-world scenarios that ultimately reach users.

What is Bitroot's long-term market logic?

Bitroot's long-term market logic can be summed up as: the parallel EVM provides base performance, AI-native capabilities provide differentiation, AI agents, data, models, compute and applications build the ecosystem, and real users and network usage ultimately prove the project's value.

What should newcomers remember most about taking part in Bitroot?

Don't rush to believe, and don't rush to dismiss. Learn the technology first, then try the products, then watch the data, and finally form your own judgment. For any project, real usage and long-term building are the most important proof.

What is the Bitroot marketing team's core message in one line?

Technology is the foundation, the ecosystem is the process, and real usage is the final proof.

What should Bitroot ultimately convey to the market?

Bitroot is not just chasing a higher TPS number. It aims to use a parallel EVM as the foundation to connect AI, AI agents, data, models, distributed compute and Web3 applications, gradually building a new kind of blockchain infrastructure for the AI era.

29. Supplement: positioning and official channels

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/) 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.

Is Bitroot related to other projects with a similar name?

Several unrelated projects use a similar name, for example Bitroots (bitroots.io), BitRoot home Bitcoin miners, and tokens listed under the ticker BTR. They are separate from Bitroot Network, the Layer 1 described on this site. The network's native token is BRT and its official site is bitroot.co. Before you trust a listing, a price page or a download link, check that it says Bitroot Network, uses the BRT ticker and is linked from bitroot.co.

30. Supplement: 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.

31. Supplement: how parallel execution works

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.

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. A Glossary of Performance Metrics defines each one and lists what any benchmark should disclose.

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.

32. Supplement: AI-native features

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.

33. Supplement: building on Bitroot

How do I connect to the network?

Add it as a custom network in an EVM wallet using the network name, Chain ID and RPC given in the "Testnet" section above, with https://devnet.bitroot.co/ as the explorer URL. Parameters may change with version upgrades, so check them against the latest official testnet documentation before connecting. The Developer Guide walks through MetaMask step by step.

Are testnet and mainnet the same network?

No. RPC URL and Chain ID differ between environments, so check on the block explorer 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 the block explorer so others can read the contract and call its view functions from the explorer.

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.

34. Supplement: how nodes and staking work

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 node 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.

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.

35. Supplement: 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.

36. Supplement: 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.