In Part 2 of our 3-part article on Interoperability, we explored Consensus Proofs as an emerging trust-minimized way to facilitate bridging between blockchains. In this article we’ll explore Storage Proofs which take the trust-minimized verification concept and extends it to checking transactions

gm teman on-chain 👋

Selamat datang kembali di CyberLetter, rekap dua mingguan - segala hal tentang CyberConnect.

![](https://link3-image.cyberconnect.dev/5ebbb9fa-9d33-4741-a22d-2a7dc4b95c0c/postImageFolder/68f4f2efb2b327fa)Begitu banyak hal yang terjadi di dunia web3 sehingga sulit untuk melacak siapa yang melakukan apa. Sudah lama berlalu, jadi kami pikir kami akan memberi Anda penyegaran tentang CyberConnect dan rangkaian produknya.![](https://link3-image.cyberconnect.dev/5ebbb9fa-9d33-4741-a22d-2a7dc4b95c0c/postImageFolder/e7371974a5bfcd2f)[CyberConnect](https://link3.to/cyberconnect), yang pertama dan terpenting, adalah protokol grafik sosial, seperti grafik sosial Facebook atau Twitter. Sejauh ini unik karena terdesentralisasi, artinya terbuka dan tanpa izin bagi pengguna dan pengembang. Bagi pengguna, ini berarti kami tetap memiliki dan mengendalikan data kami dan dapat memindahkannya dari satu aplikasi ke aplikasi lainnya tanpa terkunci dalam satu ekosistem. Bagi pengembang, ini berarti kami tidak perlu meminta izin kepada siapa pun untuk membangun pengalaman atau aplikasi yang inovatif dan dapat bersaing dengan pihak lain semata-mata atas dasar layanan yang lebih baik.

CyberConnect kompatibel dengan blockchain yang kompatibel dengan EVM. Terdapat berbagai 'klien' pada protokol, seperti Link3, Phaver, dan Mocaverse. [Link3](https://link3.to/link3), [Phaver](https://link3.to/phaver) dan [Mocaverse](https://link3.to/moca) Kami juga memiliki [CyberWallet](https://link3.to/wallet), solusi akun pintar yang kompatibel dengan ERC-4337 yang memungkinkan pengguna mengakses aplikasi web3 di seluruh blockchain dengan antarmuka terpadu dan ramah pengguna.

Ada pertanyaan lain? Terhubung dengan kami di [Twitter/X](https://twitter.com/Cyberconnect_ID) dan beri tahu kami apa yang ingin Anda ketahui!

Sekarang saatnya untuk pembaruan.

![](https://link3-image.cyberconnect.dev/5ebbb9fa-9d33-4741-a22d-2a7dc4b95c0c/postImageFolder/c75d6d0ea7bfe6a3)**1,2 juta+ CyberWallets 🤯**

![](https://link3-image.cyberconnect.dev/5ebbb9fa-9d33-4741-a22d-2a7dc4b95c0c/postImageFolder/eb2afb6ad723a35d)Apakah Anda ingat dalam [pembaruan terakhir kami](https://link3.to/cyberconnect_idn/post/023ad8f0b8fcc812e9c42595ea43a2a8b8f99376ccc01d27077f4d9caf907ab7) (~dua minggu lalu), kami telah menyampaikan bahwa kami baru saja melewati 900 ribu CyberWallet. Ya, itu berita lama! Senang sekali bisa melaporkan bahwa kami akan segera menjangkau 1,3 juta smart account! Haruskah ada pasar prediksi kapan kita akan sampai di sana? 🫣

Anda dapat melihat statistik menarik lainnya seputar Cyberwallet [di sini](https://dune.com/cyberconnecthq/cyberaccount-cyberconnects-4337-smart-account).

**Transfer asset dari Signer Wallet 💳**![](https://link3-image.cyberconnect.dev/5ebbb9fa-9d33-4741-a22d-2a7dc4b95c0c/postImageFolder/680a4f7987ccf93a)Tahukah Anda bahwa kami membuat transfer aset Anda ke CyberWallet menjadi sangat mudah? Setelah masuk ke smart account Anda, tab 'Asset' akan mengarahkan Anda untuk mentransfer aset untuk mulai menggunakan wallet AA Anda.

Cobalah dan beri tahu kami pendapat Anda 🤝

Coba [di sini](https://wallet.cyber.co/assets).

![](https://link3-image.cyberconnect.dev/5ebbb9fa-9d33-4741-a22d-2a7dc4b95c0c/postImageFolder/15ddb3db5a099dee)**Listen 📖**

**Web3 Quest with Diksha Dutta 🎧**

Salah satu pendiri [Ryan Li](https://link3.to/ryan) hadir di podcast Web3 Quest bersama Diksha Dutta di mana mereka membahas lanskap menarik dari platform sosial web3 serta manfaat memiliki identitas dan konten sosial.

Coba dengarkan [di sini](https://www.youtube.com/watch?v=Bo5zrlTqLco).![](https://link3-image.cyberconnect.dev/5ebbb9fa-9d33-4741-a22d-2a7dc4b95c0c/postImageFolder/21713dcfd10c1df6)Biasanya, bagian ini didedikasikan untuk mitra dan kolaborator kami, namun kali ini, kami mengubahnya untuk menyoroti anggota komunitas kami yang berdedikasi di Vietnam 🇻🇳

**CyberConnect Việt Nam ❤️ 🇻🇳**

Kami sangat berterima kasih atas dukungan yang kami terima dari komunitas Vietnam. Hal ini tidak akan mungkin terjadi tanpa upaya tak kenal lelah dari para pemimpin komunitas Vietnam. Sangat menyenangkan melihat komunitas berkembang setiap hari.

CyberConnect Vietnam baru saja melampaui 5 ribu pengikut di Twitter/X!

✌️✌️✌️

Sekian untuk edisi kali ini! Sampai jumpa lagi!

**Ingat: Teman On-Chain Bertahan Selamanya 🔗⭐️🥰**

— Tim CyberConnect Indonesia

*Terima kasih telah tetap bersama kami. Jika Anda menyukai apa yang Anda baca, berlangganan buletin ini dan ikuti kami di [Twitter HQ](https://twitter.com/CyberConnectHQ) & [Twitter ID](https://twitter.com/Cyberconnect_ID). Ingin berkontribusi? Bergabunglah dengan komunitas dinamis kami dengan mengeklik [di sini](https://discord.com/invite/cyberconnecthq) atau pelajari dokumen* developer *kami [di sini](https://docs.cyberconnect.me/).*

[CyberConnect](https://cyberconnect.me/) adalah jaringan sosial web3 yang memungkinkan pengembang membuat aplikasi sosial yang memberdayakan pengguna untuk memiliki identitas digital, konten, koneksi, dan saluran monetisasi. [Messari](https://link3.to/messari), [Rarible](https://link3.to/rarible), [1inch](https://link3.to/1inch), [BNB Chain](https://link3.to/bnbchain), bersama dengan 3.000+ proyek dan 1,2 juta pengguna dan kreator membangun koneksi jangka panjang melalui aplikasi yang dibangun di CyberConnect.

[Website](https://cyberconnect.me/) | [Docs](https://docs.cyberconnect.me/) | [Twitter](https://twitter.com/CyberConnectHQ) | [Twitter ID](https://twitter.com/Cyberconnect_ID) | [Discord](https://discord.gg/cyberconnecthq) | [Telegram](https://t.me/CyberConnect) | [Telegram ID](https://t.me/CyberConnectID)

gm teman on-chain 👋 Selamat datang kembali di CyberLetter, rekap dua mingguan - segala hal tentang CyberConnect. Begitu banyak hal yang terjadi di dunia web3 sehingga sulit untuk melacak siapa yang melakukan apa. Sudah lama berlalu, jadi kami pikir kami akan memberi Anda penyegaran tentang Cybe

CyberLetter #34: CyberConnect Refresher, 1 juta+ CyberWallets dan lainnya🚀

alphagram, a communication application tailored for Web3 users, is thrilled to announce its collaboration with Particle Network, paving the way for a revolutionary social wallet experience within Telegram.  You can use your wallet with just a password on other Particle wallet-compatible platforms. No need to remember multiple recovery phrases or deal with complicated setups. Simply log in with your password and start using your wallet instantly. Furthermore, alphagram has deployed both EVM (Ethereum Virtual Machine) and non-EVM (such as Solana) public chains, offering users a comprehensive range of services for social payments and transactions during communication.

![img](https://link3-image.cyberconnect.dev/5ed098c6-8ace-4425-a0c1-4720ff6ba692/postImageFolder/4cf68fa606172c87)

# **Creating and Customizing Your Social Wallet in alphagram with Particle Network**

Once you have downloaded alphagram, you can easily log in using your Telegram account and instantly create a social wallet powered by Particle Network. You have the flexibility to link your wallet to other social accounts, allowing for seamless integration. You can take advantage of the social recovery feature, which offers an alternative solution to regain access to your account in the event of password loss or account accessibility challenges. Furthermore, to bolster the security of your wallet, you can set a login password for your wallet, ensuring enhanced protection.

## Social Recovery: Regain Access to Your Account through Social Networks

The social recovery feature of the alphagram Social Wallet is designed to assist users in recovering access to their encrypted wallets in case of forgotten passwords or an inability to access their accounts. This feature allows users to verify their identity and regain control of their accounts through their social networks, establishing a connection between their accounts and social networks. Through the social recovery feature, Particle Network provides users with a convenient and secure method to restore access to their accounts. Users can utilize their social networks to verify their identity, eliminating the need to rely solely on traditional password recovery processes.

## Password Management: The Cornerstone of Wallet Account Security

**Master Password for login**

The Master Password of Particle Network is the password used to encrypt your local encryption fragment. It is the most important password, and alphgram & Particle will not save this password, so it does not support any form of recovery after forgetting. Please keep this password properly. When you log in to the new device, you need to enter the Particle Master Password to activate the fragment, otherwise, you will not be able to operate the wallet. Particle provides you with MPC (Multi-Party Computation) - based TSS (Threshold Signatures Scheme) crypto wallet. When a transaction is initiated, the local encryption fragment on your device and the Particle encryption fragment is signed at the same time and sent to the blockchain network. It not only ensures the wallet's security but also has a faster transaction speed than Shamir Secret Sharing Scheme (SSSS). It also reduces the handling fees consumed.

**Payment Password for transaction**

Particle Network's payment password feature enhances transaction security and privacy. It allows users to set separate passwords for authorizing transactions. Before any transaction, users must input the payment password for verification, ensuring only authorized users can proceed. This extra layer of security protects transaction and fund information, even if someone gains access to the login password. Users should keep the payment password confidential and follow best security practices.

## New Airdrop Event 

![img](https://link3-image.cyberconnect.dev/5ed098c6-8ace-4425-a0c1-4720ff6ba692/postImageFolder/916f79706cb2b2f9)

Starting from June 16th, we are launching the onboarding social wallet task where the first 250 users to complete the task will receive an exclusive NFT badge and be eligible for the token-gated verification to join the group and receive a $ROSE airdrop reward. The next 250 users who join the group will receive a commemorative NFT to celebrate the collaboration between alphagram and Particle Network, although they won't be eligible for the $ROSE airdrop reward. Don't miss out on this exciting opportunity to participate in our airdrop campaign and join our growing community! Get rewarded and be a part of our journey with alphagram and Particle Network.

Event link : [https://pse.is/4z9xnq](https://pse.is/4z9xnq)

![img](https://link3-image.cyberconnect.dev/5ed098c6-8ace-4425-a0c1-4720ff6ba692/postImageFolder/2ba76aaf7fe97340)

![img](https://link3-image.cyberconnect.dev/5ed098c6-8ace-4425-a0c1-4720ff6ba692/postImageFolder/1a5adb082417a2b9)

## About alphagram

alphagram is a social wallet designed for Web3 users, leveraging the native Telegram infrastructure. It provides a seamless social platform where users can easily participate in the Web3 community. With integrated social payment solutions, alphagram enables P2P transactions and rewards users for engaging in social interactions. We have established connections with popular wallets like MetaMask and WalletConnect, and deployed alphagram on leading public chains and Layer 2 networks, ensuring widespread accessibility and usability for our users.

## About Particle Network

[Particle Network](https://particle.network/) is a full-stack, data-driven, and composable infrastructure solution for Web3 developers. With its wide range of services, including MPC-based identity authentication, Wallet-as-a-Service, node API services, and NFT services, Particle Network enables seamless development across multiple blockchains and platforms.

## Keep in touch with us through

- Download [Android on Google Play](https://play.google.com/store/apps/details?id=app.alphagram.messenger); iOS is coming soon
- Community chat on alphagram [Telegram group](https://t.me/alphagramgroup)
- [alphagram airdrop official group](https://t.me/alphagramairdrop)
- Following us on [Twitter](https://twitter.com/alphagramapp)
- Check the alphagram [linktree](https://linktr.ee/alphagram) for more information

alphagram, a communication application tailored for Web3 users, is thrilled to announce its collaboration with Particle Network, paving the way for a revolutionary social wallet experience within Telegram.  You can use your wallet with just a password on other Particle wallet-compatible platforms. N

The Essence of social wallet: Convenience, Security, and Safety

***In [Part 2 ](https://link3.to/superscrypt/post/ff0df62dd4a026d8c34dedd33d5d0352ceb60ad1bb9f5f7df6f89cd5a1db2316)of our 3-part article on Interoperability, we explored Consensus Proofs as an emerging trust-minimized way to facilitate bridging between blockchains.***

***In this article we’ll explore Storage Proofs which take the trust-minimized verification concept and extends it to checking transactions in older, historical blocks. Being able to verify past transactions and user activity in this manner unlocks a multitude of cross-chain use cases.***

In [Part II](https://link3.to/superscrypt/post/ff0df62dd4a026d8c34dedd33d5d0352ceb60ad1bb9f5f7df6f89cd5a1db2316) we covered Consensus Proofs, a trust-minimized approach for bridging funds across blockchains. As bridge users typically want to see the transaction happen in the latest moment without delay, consensus proofs are useful as they constantly check the latest state of the blockchain as it moves *forward*.

This concept of trust-minimized bridging can also be applied in the other direction, reaching back into the past and using zero-knowledge proofs to verify transactions and data in older blocks. These ‘Historical Storage Proofs’ enable a different range of cross-chain use cases and in this article we’ll cover what they are, how they work and the players building in this space.

### **Retrieving Historical Data**

Historical blockchain data is useful for a variety of reasons. It can prove asset ownership, user behavior and transaction history which can then be fed into on-chain smart contracts or applications. **As of writing there are over[ 18 million blocks](https://beaconcha.in/) written to Ethereum. Smart contracts can only access the latest 256 blocks (or data in the last ~30 minutes),** so ‘historical data’ refers to anything outside of the last 256 blocks.

To access historical data today, protocols typically query[ archive nodes](https://ethereum.org/en/developers/docs/nodes-and-clients/archive-nodes/) providers, i.e. third parties like Infura, Alchemy or other indexers. This means trusting & relying on them and their data.

![](https://lh6.googleusercontent.com/VqG_bhH8ebupg3drS8GdqnRLrkyG-zY4wZEw0kbjBA2ZxIz6DCLaIXcEhSnM2QaEsZOeTKR3wOkgtnrFHJ9thmRnt7R-1rttxLqfyge3bVtPp9ln1cYOI0wzp2-RXLerirjKdAVucR1DmxYeQxIV87g)

*Exhibit 1. Illustration of Ethereum’s historical data*

This data can, however, be retrieved in a more trust-minimized fashion, through the use of Storage Proofs.

Storage Proofs are zero-knowledge proofs which allow verification of historical data stored on a blockchain. More specifically, Storage Proofs can be used to prove that a specific state existed at a particular block in the past. This method doesn’t require trust in a third party or oracle - instead,[ trust is built into the Storage Proof](https://www.starknet.io/en/posts/developers/what-are-storage-proofs-and-how-can-they-improve-oracles).

How does Storage Proofs help to validate that some data existed in older, historical blocks? This involves verifying two things:

- ***Step 1. Check that the specific block is part of blockchain’s canonical history*** i.e. the block is a valid part of the source chain’s history 
- ***Step 2. Check that the specific data is part of the block*** i.e the piece of information, such as a specific transaction, is part of that block (this can be proven with a [Merkle Inclusion proof](https://ethereum.org/en/developers/tutorials/merkle-proofs-for-offline-data-integrity/))

After receiving and validating the proof, the receiver (e.g. a smart contract on the destination chain) has the confidence in the validity of the data and can execute a corresponding set of instructions. This concept can be extended further: it is possible to run additional off-chain computations with the verified data and then generate *another* zero-knowledge proof to attest to both the data and the computation.

In short, Storage Proofs allow for retrieval of historical on-chain data in a trust-minimized fashion. This is important because as we outlined in Part I, we see web3 becoming more multi-chain and multi-layer in the coming years. The emergence of multiple layer 1s, rollups and appchains means that users’ on-chain activity will likely be split across multiple chains. This puts even greater emphasis on the need for trust-minimized interoperability solutions that maintain the composability of a user’s assets, identity and transaction history across multiple domains. This is something Storage Proofs can help solve.

### **What are some of the use cases?**

A Storage Proof allows a smart contract to check any historical transaction or data as a condition precedent. This provides a lot of flexibility in cross-chain application design.

To begin with, the Storage Proof can attest to any historical data on the source blockchain, e.g.

- Account balances and token ownership
- User transaction activity or inactivity
- Historical prices that assets transacted at over a specified period of time
- Real time asset balances in liquidity pools across different chains

Then, the proofs can be sent to the destination chain to unlock range of cross-chain use cases:

- Enabling users to vote on governance proposals on a lower cost L2
- Allowing NFT holders to access new NFT mints or community benefits on new chains
- Rewarding users (e.g. through airdrops) based on a user’s history & interaction with specific dApps
- Offering loans with interest rates tailored to a user’s aggregated transaction & credit history
- Triggering account recovery for dormant accounts
- Computing a historical TWAP for future swaps
- Computing a more accurate AMM swap price based on liquidity pools on multiple chains

Storage Proofs essentially allow applications to query & port a user’s on-chain activity & history across multiple chains to feed into a smart contract or application on another chain.

![](https://lh3.googleusercontent.com/FXa9DmBDM5leLHo9reNUy9UvFPtsB-K9QAT9RItkldLe_8eUwRQ4Fbrtt0BRDiFgPrGA6oUfp6_KVsXpgnkAlkJM5Bj_bBTrRow2snIK4LEQ4JHxhWEbywvBkLr3IVSKtmX-k7WUPT1EjDHTZnTbLNA)

*Exhibit 2. Use cases of Storage Proofs*

Let’s go through a detailed example of how they work.

### **A detailed example of how Storage Proofs work**

*Let’s consider ‘X’, which is a DeFi protocol with tokens on Ethereum. A governance proposal is coming up and they want to facilitate on-chain voting on a lower-cost destination chain. Users can only vote if they held X tokens on Ethereum at a specific point in time that we’ll call ‘the snapshot’, e.g. block #17,000,000*

***How is this done on-chain currently?***

The current way of doing this would be to query an archive node to obtain the full list of eligible token holders at block #17,000,000. The list is then stored by a DAO administrator in a smart contract on the destination chain to determine who can vote. This approach has some limitations:

- The voter list can be very large & changes every snapshot, which makes it costly to store and update on-chain for every vote proposal;
- There is an implicit trust on the archive node provider and the data they provided; and
- The administrating DAO members have to be trusted to not tamper with the voter list

***How do Storage Proofs solve this?***

As we have explained in Part II, costly computations can be offloaded to an off-chain zero-knowledge prover.

The zk prover will generate a succinct proof that is sent to the destination chain for verification. For the DAO voter eligibility example above:

- The prover generates a zero-knowledge proof that attests to the fact that block #17,000,000 is part of Ethereum's history (***Step 1.** from above*).
- After proving the validity of a block, we can prove that the user held DAO tokens when this block was finalized (***Step 2.** from above*) using Merkle inclusion proofs

![](https://lh4.googleusercontent.com/0m-YrMSh_-fmjp2D0vaLNPHFqOMf1bnvNHiv9E5yKHvg5rqbXuNverEDxzSLXSzX7U8D_hP26qNKX9lo86_6k6L5l7TlCsvkcg0s87Q0rjzMP1dYDV4A8l6H_zE_jdJxqbza7GCRwGCeGQc-xg0OzyM)

*Exhibit 3. Verifying historical data to enable cross-chain voting*

The proof is then sent to the smart contract on the destination chain for verification. If verification succeeds, the smart contract on the L2 allows the user to vote.

This approach achieves a few things. It eliminates the need:

- To trust archive node providers;
- For the protocol to maintain costly on-chain voter lists; and
- For the user to move their assets to the destination chain

### **What is the setup required for a Storage Proof?**

So far, we have abstracted away some of the complexity around Storage Proofs. Using them, however, requires an elaborate initial setup by service providers to ensure that they can be used without trusting the provider. Two things are generated and stored on-chain as part of this process:

- **A zero-knowledge proof of the entire chain (’zk commitment’):** Service providers group all the historical blocks on the source chain into consecutive fixed-size ‘chunks’ (using a Merkle tree) and generate a zero-knowledge proof for each chunk to validate the grouping. These proofs are then recursively combined until they obtain a final zero-knowledge proof which is a **‘zk commitment’ to the entire chain.** This attests that the provider has indexed the entire history of the chain correctly.

![](https://lh4.googleusercontent.com/xMh4VQJ3D3wXXm3rjv-SgG6ZX-TIb30-rnKyqKxanJHx7U8bOoaXW2h87FlKA81A8HwW-4vEQZ6fcTkXC9OxoVGbAheiUPqgVcoRqolijo5r9AwGkHnTKEQLStlsxxlQXgJ_M4AWU0ZYTojLZty59nI)

*Exhibit 4.* Illustration of ‘zk commitment’ to the entire history

- **Merkle Mountain Range:** Providers also store the Keccak Merkle roots of groupings of block hashes (chunks) of the source chain in an on-chain data structure called Merkle Mountain Range (MMR). This data structure is used as it is easy to query and update and enables a provider to prove that a given block exists in the history of a chain efficiently. The MMR is created using Keccak256 hashes, Poseidon hashes or both. Poseidon hashes are more zero-knowledge friendly, which allows computation to be done on historical data, after which both data and computation validity can be proven via zero-knowledge.

![](https://lh5.googleusercontent.com/btopSNzLOGiiSyxMGz9XjJ9uOkRwLoxFs6bxHBmPfyzM1Vjlx_T8657KwIS5gppkywxPSPzVVuKNZPJPpNv6Jdzu5F42yudpQRSQd90RqVgISdJ3DMNjVhbbnK67M1ktBFNIDgqmTZc7mwy15Jropmw)

*Exhibit 5.* Illustration of Merkle Mountain Range

As new blocks are added to the source chain, the service provider updates the ‘zk commitment’ and the MMR periodically (e.g., every hour or day) to keep up with the chain. This is done so that past blocks are always linked to one of the 256 blocks currently accessible from the EVM. This ensures that historical data is linked to one of the blocks currently available from Ethereum.

In the diagram below we set out more detail on how the setup is achieved:

![](https://lh6.googleusercontent.com/v2LY1Xi4PV4FPJYI05ZeTBAv5g74vtSsKeEMHnHjJEHtYJEPVYvTVMWoMb1Yu81TS783ynQE5qki5dcxMbk3KJtJsiDXdotdoMzIrQdvv3T6pF-a71zvhltwHIOZkQNRSck-YndxsHqsLtve9bohOz4)*Exhibit 6. Bringing it all together*

Bringing it all together, here’s how Storage Proofs are used (after the setup is completed) in the context of the DAO voting example we presented earlier:

- The service provider creates and stores the ‘zk commitment’ to the entire chain (i.e. Ethereum’s history) and the MMR on the destination chain
- The provider allows applications to query historical data on-chain or off-chain via an API
- The voting dApp on the destination chain sends a query to the provider smart contract and aims to find out whether a user held DAO tokens on block #17,000,000 on Ethereum
- The provider checks two things:
    - That the queried block is part of Ethereum's canonical history (***Step 1.** from above*); the provider then generates a zero-knowledge proof of block inclusion via Merkle Mountain Range 
    - That the user held DAO tokens in block #17,000,000 (***Step 2.** from above*); the provider then generates another zero-knowledge proof that the user held DAO tokens inside the block 
- The provider aggregates the proofs generated above into a single zero-knowledge proof
- The aggregated ZK proof is then sent back to voting dApp smart contract on destination chain which verifies it and on successful verification, allows the user to vote

### **Teams building in the space**

Several players are building to enable smart contract access to historical on-chain data in a trust-minimized manner.

[Axiom](https://www.axiom.xyz/), now live on Ethereum, aims to provide smart contracts on Ethereum with access to historical Ethereum data via zk-based Storage Proofs. The team is also enhancing capabilities for off-chain computation on top of historical data, and proving the correctness of this data and computation in zero-knowledge.

[Relic Protocol](https://relicprotocol.com/) has a similar technical approach to Axiom and is live on Ethereum and zkSync Era. Relic uses Merkle inclusion proofs to demonstrate data inclusion (as opposed to Axiom's approach of proving Merkle inclusion in zero-knowledge).

[Herodotus](https://www.herodotus.dev/) is channeling its efforts towards the provisioning of Ethereum's historical data for L2s. The testnet implementations are available today on Starknet and zkSync Era. With an OP foundation grant, we think we know where the Herodotus team is heading next.

[Lagrange Labs](https://www.lagrange.dev/) has introduced fully updatable proofs through their recent ZK MapReduce (ZKMR) innovation. It uses a new vector commitment called [Recproofs](https://twitter.com/lagrangedev/status/1694020117724848554), which extends the concept of updatability to computation over data.

![](https://lh6.googleusercontent.com/RiRrPHSBvAYV04xPptv6f_3knRzrKrUZE_U31Gb8OKsuUL7RCTijPOSDtiBYfgE_spLEIGtUTHCS8yAuP1U3Q3sOMkqynHsQRE0CsRfMB6edjdpbnuh7BiYkZxs-m6zxaIFXUwF9a_xZC0N8tB8yfK0)

*Exhibit 7.* Teams working on Storage Proofs

### **Conclusion**

In this part, we covered how Storage Proofs allow verification of historical on-chain data without the need to trust a third party. This makes them a valuable tool for on-chain composition and cross-chain interoperability.

As Total Value Locked continues to migrate from Ethereum to Layer 2 ecosystems, we anticipate the rise of more expressive applications that leverage historical on-chain data through Storage Proofs.

While zero-knowledge technology is becoming faster and cheaper, the cost of generating Storage Proofs constantly to keep up with a chain's state remains a challenge. The profitability of such services will depend on the volume of queries generated by querying applications.

Despite the challenges, the significance of Consensus Proofs and Storage Proofs powered by zero-knowledge technology, cannot be overstated. We are excited to see how these technologies will be used to build a more trust-minimized multi-chain future.

237

0 Comments

No Comments