Brevis (BREVIS)

Preview

Market data not yet available

Overview

Brevis (BREVIS) is a zero-knowledge (ZK) “coprocessor” for blockchains. In simple terms, it lets smart contracts read rich historical data and run heavy computations off-chain, then send back cryptographic proofs that the results are correct. Developers can use Brevis to build data-driven features—like loyalty-based fees, proof-of-activity rewards, or cross‑chain reputation—while keeping on-chain verification fast and affordable. The project describes Brevis as giving smart contracts “memory and compute,” so apps can reason over the past and across chains without trusting a centralized server. (blog.brevis.network)

Brevis supports two complementary modes. A “pure-ZK” path generates a ZK proof for each request. A newer “propose‑challenge” path uses Brevis coChain, an Actively Validated Service (AVS) built on EigenLayer. In this model, results are proposed by a restaked operator set and can be challenged with ZK fraud proofs during a time window; if no challenge occurs, apps can accept the result without paying the full cost of proving. This design reduces cost and latency for many everyday use cases. (blog.brevis.network)

The team also builds ZK proving tech such as “Pico Prism,” a distributed zkVM focused on real‑time Ethereum block proofs. In October 2025, the team reported new performance milestones that push toward Ethereum’s goal of rapid, low‑cost verification. While this is infrastructure under the hood, it matters to Brevis users because cheaper, faster proofs help unlock more practical, data‑rich on‑chain features. (thestreet.com)

History & Team

Brevis was founded by Michael (Mo) Dong, best known as a co‑founder of Celer Network. Dong has a computer science background and long experience in blockchain infrastructure. He serves as Brevis’s co‑founder and CEO, and has publicly discussed Brevis’s mission to provide an “infinite computing layer” for Web3. (blockflow.news)

In November 2024, Brevis announced a $7.5 million seed round co‑led by Polychain Capital and Binance Labs, with participation from IOSG Ventures, Nomad Capital, Bankless Ventures, HashKey and other angels. The round was structured as a token raise and helped fund rollout of the Brevis SDK and coChain AVS. (theblock.co)

Throughout 2024–2025, the project moved from beta to wider adoption with partners across DeFi and infrastructure. Brevis coChain launched as one of the early AVSes on EigenLayer with dozens of operators and large restaking commitments from ecosystem players, strengthening the crypto‑economic security backing its propose‑challenge model. (blog.brevis.network)

Technology & How It Works

ZK coprocessor basics

Blockchains are great at verification but limited in storage and compute. Brevis shifts heavy lifting off‑chain while preserving trust. A developer writes a query and computation—“Has this wallet provided X liquidity over the last 90 days across chains?” or “Compute the fees generated by each LP position last epoch.” Brevis scans the relevant chain data, runs the computation off‑chain, and produces a succinct proof. The on‑chain contract verifies this proof in milliseconds and acts on the result. This lets apps personalize logic, measure long‑term behavior, and coordinate cross‑chain features without revealing private details. (blog.brevis.network)

Two execution paths

• Pure-ZK mode: Every request results in a ZK proof. This is the most trust‑minimized route but can be costlier for frequent or complex workloads. (blog.brevis.network)
• Propose‑challenge mode (Brevis coChain): An AVS built on EigenLayer accepts requests from dApps. Operators produce results, which are posted on‑chain as proposals. Anyone can challenge a bad result during the challenge window with a ZK fraud proof. If no challenge appears, the result stands—bringing big cost and latency savings while keeping a cryptographic backstop. This architecture also enables features like proofs of non‑existence, which are hard or expensive in a pure‑ZK design. (blog.brevis.network)

On day one, Brevis coChain launched with 29 operators from the EigenLayer ecosystem and reported more than a billion dollars in restaking commitments from partners such as Ether.Fi, Renzo, Swell, and Bedrock—helping align honest behavior via slashing risk. (blog.brevis.network)

ZK proving stack and Pico Prism

For proofs to be practical, they must be fast and affordable. Brevis’s Pico Prism zkVM parallelizes proving across multi‑GPU clusters and targets “real‑time proving” benchmarks set in the Ethereum community. In mid‑October 2025, Brevis reported 96.8% real‑time coverage (<10 seconds) and 99.6% coverage under 12 seconds for 45M‑gas Ethereum blocks, with roughly half the hardware cost of previous public results—an advance that improves the economics of proof‑heavy applications and paves the way for broader L1/L2 integrations. (thestreet.com)

Multi‑chain reach and developer tooling

Brevis is designed to read states, transactions, and receipts across chains and time windows, verify proofs on many blockchains, and plug into new ecosystems. The team provides SDKs (including Go) so smart contracts can request and verify results with simple interfaces, making “data‑driven” features easier to ship. (blog.brevis.network)

Tokenomics & Utility

Brevis’s seed round was structured as a token raise, and community materials commonly refer to the native token as BREVIS. As of October 2025, full economic parameters have not been publicly finalized, but the project has outlined a dual‑quorum Proof‑of‑Stake model for Brevis coChain that uses both restaked ETH/LSTs and an additional native token for security and incentives. In practice, this means operators and delegators can be slashed for dishonest behavior under either quorum, and the native asset helps align long‑term participation in the network’s validation process. (theblock.co)

Based on published architecture and common patterns for AVS‑secured networks, the token’s roles are expected to include:

• Securing the coChain AVS: staking and slashing in the native token alongside ETH/LST restaking, following the dual‑quorum design described by the team. (blog.brevis.network)
• Operator incentives: rewarding node operators who correctly process and propose coprocessing results, with penalties for provably incorrect outputs during challenge windows. (blog.brevis.network)
• Governance: guiding parameters like challenge periods, fee schedules between pure‑ZK and propose‑challenge paths, and allow‑lists for supported chains and data sources, consistent with how many AVS ecosystems evolve. (Inference from Brevis’s AVS design.) (blog.brevis.network)

The team has also run a community program called “The Proving Grounds,” where participants earn “Sparks” points tied to a future token generation event (TGE). Sparks are not tokens but act as inputs for future airdrop eligibility and allocation once the token launches. (blog.brevis.network)

Ecosystem & Use Cases

Brevis’s design opens many practical features for dApps:

• Data‑driven DeFi: Partners have explored loyalty‑based fee tiers, dynamic fees using market volatility, and rewards tied to actual fee contribution rather than time staked. These patterns are especially natural with Uniswap v4 hooks and other programmable AMMs. (hookatlas.com)
• Intelligent DEX experiences: THENA on BNB Chain and PancakeSwap Infinity announced plans for Brevis‑powered “Intelligent Plugins” and user‑aware trading UX that adapt fees or perks based on on‑chain behavior, all verified with ZK proofs. (blog.brevis.network)
• Fair and verifiable rewards: With Usual’s stablecoin ecosystem, Brevis helps distribute ongoing “Continuous Protocol Incentivization” rewards that depend on real user actions across multiple venues—claimable on‑chain with ZK‑verified proofs. Beefy likewise integrated Brevis to make yield distributions provable and transparent. (blog.brevis.network)
• Cross‑chain data and storage: Partnerships (for example, with 0G) aim to let smart contracts securely access a wider universe of data while keeping verification on‑chain. (blog.brevis.network)

Developers can also explore identity and reputation, Sybil‑resistant airdrops, and account‑abstraction features like social recovery based on recent transaction graphs—use cases Brevis has highlighted since its early technical write‑ups. (blog.brevis.network)

Advantages & Challenges

Advantages

• Rich, omnichain data in smart contracts: Brevis lets apps reason over histories and behaviors across chains without trusting a centralized indexer. That supports features like loyalty tiers, OG‑status proofs, or retroactive LP rewards. (blog.brevis.network)
• Flexible trust‑cost trade‑offs: The pure‑ZK route maximizes cryptographic guarantees; the propose‑challenge route reduces costs and latency for many workloads while keeping a ZK security backstop. (blog.brevis.network)
• Growing integrations: From DEX UX on BNB Chain to rewards in stablecoin and yield ecosystems, real deployments show how ZK‑verified computations can improve user experience. (coincu.com)
• Performance R&D: Pico Prism advances in proving speed and hardware efficiency help make real‑time verification practical, which benefits any proof‑heavy application. (thestreet.com)

Challenges

• Developer complexity: ZK systems and cross‑chain data pipelines add mental overhead for teams new to proofs or historical state queries. Tooling helps, but there is still a learning curve. (blog.brevis.network)
• Economic design: The propose‑challenge model must balance challenge windows, slashing rules, and operator incentives. Those parameters will evolve with governance and real‑world use. (blog.brevis.network)
• Ecosystem dependencies: Relying on restaking markets and AVS operators ties security to broader Ethereum restaking dynamics. Coordination with EigenLayer participants remains important. (blog.brevis.network)

Where to Buy & Wallets

BREVIS is not publicly tradable as of October 2025. The project has stated that “Sparks” points from The Proving Grounds will help determine eligibility and allocation at the token generation event (TGE). BREVIS is not available on centralized or decentralized exchanges at this time. (blog.brevis.network)

Brevis apps support common EVM wallets. MetaMask, Rabby Wallet, Coinbase Wallet, and WalletConnect can be used to connect to the Brevis Proving Grounds and Brevis‑powered integrations. When the token launches, any ERC‑20–compatible wallet should be able to hold it, subject to official distribution details announced by the project. (blog.brevis.network)

Regulatory & Compliance

Brevis builds developer infrastructure for verifiable compute. The forthcoming token is associated with the network’s security and governance design, including the dual‑quorum AVS model. As with many utility or governance tokens, how regulators classify the asset can vary by jurisdiction and by the token’s final rights and uses at launch. In the United States, analysis often centers on factors like investment intent and managerial efforts; in the European Union, the Markets in Crypto‑assets (MiCA) regime distinguishes categories such as utility tokens and asset‑referenced tokens. These frameworks focus on the token’s design and disclosures rather than the underlying technology alone.

From a faith‑based perspective, Brevis does not publish any official shariah certification. Because the protocol involves staking, slashing, and potential reward mechanisms linked to a network token, many scholars would not view it as conforming to classical Islamic finance principles that avoid speculative elements and interest‑like returns. In practice, Brevis is a technical platform, not a financial product by itself, and there is no indication that it has sought or received halal attestation. As a result, it is generally not considered shariah compliant.

Future Outlook

Brevis’s roadmap points to a wider role for ZK coprocessing across chains and apps. The launch of coChain on EigenLayer gives dApps two lanes—pure‑ZK for maximum assurances and propose‑challenge for everyday affordability—making it easier to match security budgets to real usage. As integrations deepen with DEXs, stablecoin platforms, and yield aggregators, the pattern of “prove then act” could become a normal part of on‑chain UX. (blog.brevis.network)

On the proving side, advances like Pico Prism suggest that real‑time ZK verification will keep getting cheaper and faster. That trend aligns with Ethereum’s longer‑term vision of verifying proofs instead of re‑executing every transaction, opening doors for higher throughput without sacrificing trust. For Brevis, better proving economics can lower costs for developers and users, expand the set of viable use cases, and increase the number of chains and applications that can plug into its coprocessor stack. (thestreet.com)

Community programs such as The Proving Grounds indicate an effort to involve users ahead of the TGE and to connect participation with on‑chain, proof‑backed activity rather than one‑off snapshots. If that model proves out, expect more protocols to adopt continuous, verifiable incentive designs that reward long‑term behavior. (blog.brevis.network)

Summary

Brevis is building a ZK coprocessor that lets blockchains “think with history” and coordinate across chains without trusting centralized data feeds. Its architecture offers developers a choice between pure‑ZK and propose‑challenge modes, pairing cryptographic guarantees with practical costs. Early partners across DeFi are using Brevis to deliver loyalty‑aware fees, verifiable rewards, and other data‑driven features, while the team’s proving stack aims to make real‑time verification widely affordable. The upcoming BREVIS token is tied to a dual‑quorum staking and slashing design for the Brevis coChain AVS, with community “Sparks” set to influence allocation at TGE. As zero‑knowledge proofs spread through the crypto stack, Brevis sits at the intersection of performance, security, and user‑centric design—positioned as an engine for the next wave of smarter, more personalized on‑chain applications. (blog.brevis.network)