Auromony sets out to be a trustless asset bridge between Harmony and Aurora (EVM environment on NEAR Protocol).
The scope of this proposal covers the research and development of a trustless bridge between Harmony and Aurora ultimately powered by ZK. The current MVP supports bridging of USDC on mainnets with limited initial liquidity ($10 on Aurora and Harmony respectively) powered by HTLCs.
The current MVP is a custom build of Connext that enables trustless briding based on Hash Time Locked Contracts (HTLCs). Given the immaturity of ZK light clients at the time of starting the project, the MVP was deliberately chosen to adopt local verifiactions instead to maintain the trustless status of a usable prototype that can be developed within a limited timeframe.
The architecture of the current MVP involves the components listed below. If you are interested in more details, you may refer to the demonstration video linked in the last section of this proposal or the documentations within the corresponding repositories.
Monorepo containing the source code of Contracts, Subgraphs and Router, as well as Docker Compose configurations for running the Router and NATS messaging server.
NATS server facilitating off-chain messaging (i.e. auctioning and bidding) between frontend users and backend routers.
Local node hosting The Graph subgraphs.
Subgraphs caching server that provides APIs for the frontend to read subgraphs.
Frontend for user interactions with the bridging service.
List of chains and assets. For sourcing cross-chain assets in frontend.
Starting with one of the most liquid cryptoassets, Auromony will provide users a secure solution when transferring and using their beloved cryptoassets across both chains for payments, trades, bids, etc.
As gas on Aurora is denominated in ETH, bridging ETH from other means through Harmony could be an economical solution to fund an Aurora wallet versus e.g. bridging from Ethereum with future support of ETH bridging on Auromony.
Light client based version, currently in development:
Harmony’s “official” bridge. Support for bridging to Aurora is neither available nor announced.
Bridging to Aurora using Horizon’s mint-burn model would also create Aurora versions of Ethereum assets on Harmony that could deteriorate users’ experience.
Aurora’s light client based “official” bridge. Support for bridging to Harmony is neither available nor announced.
Bridging to Harmony using Rainbow Bridge’s mint-burn model would also create Harmony versions of Ethereum assets on Aurora that could deteriorate users’ experience.
cBridge supports trustless bridging between Harmony and Aurora of USDC only at the time of writing this proposal. Accessing the majority of liquidity on cBridge also requires honesty assumption of its State Guardians.
Allbridge supports bridging between Harmony and Aurora of its protocol token ABR only at the time of writing this proposal. The bridging process also requires honesty assumption of its external validators.
Multichain supports bridging between Harmony / Aurora and other chains, but not directly between Harmony and Aurora at the time of writing this proposal. The bridging process also requires honesty assumption of its external validators.
Further Auromony research and development is anticipated to cover:
- A Harmony ZK light client in Solidity
- An Aurora ZK light client in Solidity
- A ZK bridge MVP between Harmony and Aurora with support of limited assets
- A production-ready ZK bridge between Harmony and Aurora with support of more assets
As such, a $15k/year stable basic income is requested to take care of initial R&D, welfare and operations costs.
This ask will be lined up with the following milestones:
- launching a feature-complete product on our testnet
- forming a DAO with 5-out-of-9 multisig with our DAOs
- launching on our mainnet with audit
- attracting 1k daily active users (with launch video, full PR promotion)
- attracting 10k daily active users (with a detailed roadmap, governance process)
Given the heavy R&D described above, the anticipated completion dates for objectives up to milestone 3 are very preliminary estimations that could likely vary as time progresses.
|Testnet Launch||30 Apr 2022||Completed|
|DAO Initialization||30 Jun 2022||Pending|
|Harmony ZK light client Testnet Launch||30 Sep 2022||Pending|
|Aurora ZK Light Client Testnet Launch||30 Nov 2022||Pending|
|ZK Auromony Testnet Launch||15 Jan 2023||Pending|
|Beta Testing||28 Feb 2023||Pending|
|Smart Contract Audit||30 Apr 2023||Pending|
|Mainnet Launch||30 Jun 2023||Pending|
- Auromony on Mainnet (Frontend error popups, if any, can be safely ignored.)
- Transaction Examples