[Cosmos chain onboarding proposal] #3978
kritarth1107
started this conversation in
Gateway
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Website
https://airchains.io/
Github
https://github.com/airchains-network
Blog
https://blog.airchains.io/
Documentation
https://docs.airchains.io/
Community stats
Short Summary
Airchains Network is a cutting-edge ZK-rollup framework that enables developers to build scalable, privacy-preserving, and interoperable decentralized applications (dApps) across multiple blockchain networks. By leveraging zero-knowledge proofs and a modular architecture, Airchains empowers developers to create innovative solutions that prioritize scalability, security, and user privacy.
Why should Wormhole add this chain?
By adding Airchains Network chain, Wormhole can expand its cross-chain capabilities, support privacy-focused use cases, and tap into a growing ecosystem of dApps and users. The lightweight integration process and potential for cross-chain liquidity make Airchains an attractive addition to the Wormhole network.
Expanding Wormhole's Cross-Chain Capabilities:
• Airchains Network is a modular and interoperable ZK-rollup framework that enables scalable and privacy-preserving dApps across multiple blockchains.
• By integrating Airchains, Wormhole can extend its cross-chain messaging and token bridging capabilities to a broader range of blockchains supported by Airchains, such as Ethereum, Cosmos, and Solana.
• This integration would enhance Wormhole's value proposition as a universal interoperability protocol, allowing seamless communication and asset transfer between Airchains-based ZK-rollups and other supported chains.
Enabling Privacy-Focused Use Cases:
• Airchains' ZK-rollup technology offers enhanced privacy features for dApps and transactions.
• Integrating Airchains would enable Wormhole to support privacy-focused use cases, such as confidential token transfers, private voting systems, and secure data sharing across different blockchains.
• This would attract a new set of developers and users who prioritize privacy and confidentiality in their cross-chain interactions.
Lightweight Integration for Guardians:
• Integrating Airchains into Wormhole would be a light lift for Guardians, as they would not be required to run a full node for the Airchains chain.
• Connectivity can be established via a Gateway IBC connection, simplifying the integration process and reducing the operational burden on Guardians.
Growing Ecosystem and Partnerships:
• Airchains has a growing ecosystem of dApps, developers, and users leveraging its ZK-rollup framework.
• Key metrics:
• 2300 dApps deployed on Airchains Switchyard Testnet
• 6900 monthly active users interacting with Airchains-based dApps
• 900000 transactions processed per month on Airchains ZK-rollups
• Airchains have established partnerships with leading blockchain projects and infrastructure providers, such as Eigen, Avail, Espresso, Celestia and Gevulot to foster ecosystem growth and interoperability.
Leveraging Wormhole for Cross-Chain Liquidity:
• Airchains plans to utilize Wormhole's token bridging capabilities to enable seamless liquidity transfer between Airchains-based ZK-rollups and other supported chains.
• This would allow users to efficiently move their assets across different blockchains, unlocking new DeFi opportunities and enhancing the overall liquidity of the Airchains ecosystem.
• Airchains is exploring incentivized liquidity programs to encourage the adoption and usage of Wormhole-wrapped tokens within its ecosystem.
Complementing Existing Bridge Integrations:
• Airchains has already integrated with other popular blockchain bridges, such as IBC and CCIP, demonstrating its commitment to cross-chain interoperability.
• Integrating with Wormhole would complement these existing bridge connections and provide users with more options for cross-chain communication and asset transfer.
Technology and Features
- Cosmos SDK-Based Settlement Layer: Airchains is built on the Cosmos SDK, providing a robust and scalable settlement layer for blockchain applications.
- zk-Rollup Integration: Implements zk-rollup technology to enhance scalability and reduce transaction costs by bundling multiple transactions into a single proof.
- SNARK-Based Proving Mechanism: Utilizes advanced SNARK-based proving mechanisms, including
Groth16
andPlonk
, to ensure efficient and secure transaction validation.- Shared Sequencer and Decentralized Proving Network: Supports a shared sequencer architecture, working closely with the Espresso team, and is implementing Gevulot for a decentralized proving network.
- Interoperability via IBC: Fully supports Inter-Blockchain Communication (IBC), allowing seamless interaction and asset transfers with other chains in the Cosmos ecosystem.
Native token details
1. Total Supply: The native token of Airchains has a total supply of
10 billion AMF
tokens.2. Governance: Token holders can participate in governance decisions, allowing them to vote on protocol upgrades, parameter changes, and other key proposals, ensuring a decentralized and community-driven development process.
3. Transaction Fees: The native token is utilized to pay transaction fees on the network, facilitating smooth and efficient operations while preventing spam and misuse.
4. Staking Rewards: Holders can stake their tokens to contribute to network security and consensus mechanisms, earning rewards for their participation and support.
5. Ecosystem Incentives: The token is used to incentivize various activities within the ecosystem, such as rewarding developers, validators, and users who contribute to the growth and security of the network.
Technical requirements for running a node
None - Airchains will emit messages to Gateway via IBC. Guardians should not have to run anything additional (except for guardians who may run IBC relayers).
IBC Relaying Strategy
We are planning to handle IBC relaying between Wormhole Gateway and our chain by leveraging the services of a specialized IBC relaying provider. Currently, we are in discussions with DAIC, a reputable company known for their expertise in providing reliable and secure IBC relaying services. We are finalizing a service agreement with them that includes comprehensive support and maintenance to ensure seamless relaying operations.
Should this arrangement change or should we decide to engage a Wormhole Guardian for IBC relaying, we will update our onboarding documentation accordingly to reflect the new provider and any relevant service agreements.
Beta Was this translation helpful? Give feedback.
All reactions