Brevis, emerging as a beacon of innovation in the blockchain space, introduces its “Smart ZK Coprocessor”, which represents a significant step forward for Defi and Web3. In a rapidly evolving ecosystem, this development provides a mechanism for smart contracts to seamlessly interact with and calculate historical on-chain data across any blockchain, without relying on trust assumptions.
The latest AMA provided a forum for the minds behind Brevis and their collaboration with EigenLayer to discuss how this technology not only improves blockchain security but also broadens the scope for developer adoption and data-driven applications.
For those interested in delving into the details and discussions, below are the highlights of the AMA:
Links:
X Spaces: AVS Deep Dive with Brevis YouTube: AVS Deep Dive with Brevis Spotify: AVS Deep Deive with Brevis
Speakers:
Index:
“Burbis is a smart ZK coprocessor that can utilize the full on-chain data and run the computations without any additional trust assumptions. Burbis can trustlessly read the states, the transactions, and the receipts of any time frame. It can run the computation on data of any size. Also, Brevis can verify the zero-knowledge proof on any blockchain. It can empower the data-rich use cases, including the data-driven Defi, the ZK Bridges, the ZK DID, and other fancy features built on based on Blockchain Data.”
“So, one of the major challenges that Brevis can solve for the blockchain ecosystem is to allow smart contracts to access and compute data from any block and from any blockchain. This is because smart contracts deployed on a spinel blockchain are living in the context of the blockchain virtual machines, but can only access the data from other smart contracts that are made public via view functions”
“So in that case, the Web3 applications simply have no way to access the vast majority of the data stored in blockchains in a trust-free manner. But with Brevis, we can have this issue well solved. So that we can build various data-driven features for decentralized applications, such as the VIP Trader programs for DAXs”
“So basically, Brevis is like, you’re building for data-driven Defi, you can build secure bridges, right? You create these like financial connections between, I guess, users and protocols. You also have privacy features I’m assuming. And then this is all trustless if I’m understanding correctly.”
“Yeah, that is a correct understanding.”
“Maybe I can just give you an example that we just recently built the VIPTrader fee discount hook, which is also kind of the VIPTrader program together with Uniswap Foundation for the Uniswap v4. So we have been accessing and calculating the user's previous transaction data for the past month. Based on this data and the volume, and then we generate a zero-knowledge proof, and then it will be verified in the Uniswap v4 hook smart contracts. In that case, it would determine the user's WIP tier. Based on this tier, the hook smart contracts can just You know, just grant a kind of fee discount for this user and everything for what I mentioned just now is in the smart contract level. “
“Brevis is already production-ready. And in fact, that there's already a lot of developers and partners integrating Brevis into their protocols.”
“Well, EigenLayer is one of our key partners and they're doing great. Well, also like EigenLayer restaking and also their expansion will contribute to the security in Brevis, especially the co-chain”
“But how can we ensure that most of the stakers or validators, you know, they don't have any kind of malicious behaviors? In that case, that we would like to have more like high-value stakers in our network, in our brevis co-chain. So by leveraging EigenLayer, we can have more security level for our co-chain, which means that it will ensure the correctness of our ZK co-processing results.”
“The Brevis Co-Chain and also the developers who are using Brevis can share the same level of security of Ethereum. So this is very important to our whole infrastructure. So it will ensure or improve the security level for our Co-Chain. “
“So recently we have launched the other Brevis V2. With that, developers can just build their DApps using Brevis within three simple steps. The first is to identify and gather data required to run the business logic. The second step is just based on those data access specifications, developers can now build their application circuits to run the business logic. Once the verification is successful, the brevis contract can call the callback function to the application contract. And then it will handle the results. So that's it.”
“We have been Putting a lot of effort into the developments of our SDK to make it developer-friendly and high-performance and to developers who want to build the data-driven features using Brevis.”
“So we're partnering with some of the biggest DeFi protocols today. To enable a new data-driven DeFi user experience. For instance, the YPTrader fee discount hook for Uniswap v4, as I mentioned, has already been launched and released. Also, Another new use case, which is about the ZKML-powered UX personalization infra, which is also with another well-known project.”
“Just like I mentioned, there's a lot of very smart and data-driven features in centralized exchange, but it's quite missing in decentralized exchange. And for now, all of the features in the Decentralized Exchange or in DeFi are quite limited. So we're trying to work with our partners to make this happen. “
“So actually we are building the infra. So we are mostly facing the developers and builders. That's why all of the big names that I just mentioned are the, you know, the projects, the DeFi projects, or the other project teams that are focusing on the infra. So basically we're... As I mentioned, facing developers and builders who are building different protocols or can be something like gaming projects also, because we can also support a kind of data-driven live ops features for gaming projects and also for others”
“We're looking forward to working with more partners like EigenLayer, like the You know, the big DeFi projects. And we're just trying to build more and more data-driven use cases because we would like to make this more adopted and more well-known for the users and developers.”