Hi, I'm Heorhii, and today I'll introduce you to two groundbreaking tools in the Aleo ecosystem: Eclipse and IZAR. These tools are designed to bridge ecosystems, enhance cross-chain interoperability, and ensure privacy-preserving transactions. Let's dive into how they work and their benefits for developers.

1. Eclipse: bridging Aleo and Solana with zkProofs

Overview. Project Eclipse aims to create a two-way bridge between Aleo and Solana by storing zk proofs of Solana votes on the Aleo blockchain. This integration enhances the interoperability between the two networks, leveraging Aleo's privacy-preserving capabilities and Solana's high-performance blockchain.

1) Installation. Eclipse is written in Rust, so you need the Rust toolchain to get started.

1. Install Rust:

   curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh
   

2. Clone the repository:

   git clone https://github.com/eqlabs/eclipse && cd eclipse/service/src/aleo-to-solana
   

3. Build the project:

   cargo build
   

2) Running Aleo-to-Solana:

1. Solana node:

   • Compile and run the Eclipse version of the Solana node:

   ./scripts/cargo-install-all.sh .
   ./bin/solana-test-validator -r --log
   

2. On-chain programs:

   • Compile on-chain programs:

   cd /programs/aleo-verifier
   cargo build-bpf --sdk=<path to solana>/sdk/bpf
   

   • Deploy the programs:

   ./bin/solana program deploy <path-to-the-eclipse_aleo_verifier.so>
   ./bin/solana program deploy <path-to-the-eclipse_uploader.so>
   

3. Eclipse service:

   • Run the Eclipse service:

   ./target/debug/aleo-to-solana \
   --author_keypair <default-path-to-solana-test-verifier-config-keypair> \
   --payer_keypair <default-path-to-solana-test-verifier-config-keypair> \
   verify_proofs \
   --uploader_program_id <eclipse-onchain-uploader-program-id> \
   --verifier_program_id <eclipse-onchain-aleo-verifier-program-id>
   

4. Checking verification:

   • Verify Aleo transactions using the Solana binary:

   ./bin/solana account <account-where-verification-results-stored>
   

2. IZAR: privacy-preserving cross-chain interoperability

Overview. IZAR is a protocol that facilitates privacy-preserving cross-chain communication between Ethereum and Aleo. By utilizing zk cryptography, IZAR ensures fully private transactions and robust user privacy, making it a valuable addition to the Aleo ecosystem.

Features:

• Cross-chain communication. Supports arbitrary message communication between heterogeneous chains.

• Zk cryptography. Ensures privacy and security for cross-chain transactions.

• Governance model. Includes zkSnark multisig verification for enhanced security and trust.

Building IZAR:

1. Clone the repository:

   git clone https://github.com/izar/izar && cd izar
   

2. Compile the program:

   leo build
   

IZAR contracts:

• izar-protocol. Contains cross-chain protocol and governance logic.

• izar-token. Maps tokens across different chains, similar to ERC-1155.

• izar-token-proxy. Manages permissions and binds cross-chain logic.

Conclusion. Eclipse and IZAR are powerful tools that significantly enhance the Aleo ecosystem. Eclipse bridges Aleo and Solana through zk proofs, while IZAR enables secure and private cross-chain transactions between Ethereum and Aleo. These tools not only improve interoperability but also ensure privacy and security, making Aleo a more robust and versatile platform for developers.

You can find more Aleo tools here:

Feel free to explore these tools and contribute to their development. Happy coding!

To know more about Aleo, join now!

• Aleo Twitter

• Aleo Discord

• Aleo Website

• List of Aleo and Leo code and resourses

Prepared by Colliseum