Eigen Labs said in a 23 January 2026 blog post that EigenAI is live on mainnet, meaning in production rather than on a test network. The company describes EigenAI as a service that runs large language model (LLM) inference so that results can be reproduced bit for bit. Inference is the process of generating a model's outputs. The post links a whitepaper with the full design.[1]
The company reports 100% reproducibility across 10,000 test runs. It puts the performance overhead under 2%, citing about 1.8% added latency for end-to-end inference. Reproducibility holds only within one GPU architecture. In the company's tests, every run on the same architecture matched and no run across architectures did. Operators and verifiers must therefore use identical GPU models. Eigen Labs attributes the result to controlling every layer of the stack. That includes fixed-seed decoding, which makes the model's random choices repeatable. It also includes custom matrix-multiplication kernels that avoid floating-point atomic operations, whose execution order can change from run to run.[1]
According to the post, verification is optimistic, meaning results are accepted unless someone challenges them. Operators publish encrypted results to EigenDA, the company's data availability layer, which stores published data so that others can retrieve it. Results can be challenged during a dispute window. A challenge sends the request to a committee of verifiers. The committee re-executes it inside trusted execution environments (TEEs), hardware-isolated environments designed to protect the code and data inside them. Because the computation is deterministic, the committee only needs to check whether the bytes match. A mismatch triggers slashing, a penalty taken from the collateral the operator has staked. The post says a single honest verifier can detect fraud.[1]
Eigen Labs authors set out the assumptions behind this design in a paper posted to arXiv on 30 January 2026. The committee decides disputes by vote, which assumes that verifiers holding at least two-thirds of the network's stake behave honestly. Verifiers receive the key that decrypts requests only after their TEEs produce an attestation, a signed record of the code they loaded. The key is secret-shared across several key-management shards, so no single shard holds the whole key.[2]
Sources
Check or correct this page
Verification record
The digest below shows whether the text you are reading matches the published source. It does not show that the reporting is correct. The build computes it from this page's Markdown source and lists it in the site manifest.
3aabd861338a532d475575fce78c66a82fa8ba4b0ca6c3d2aa0336a58762121f
.jpg){kind=link}