near / near-one-project-tracking

A repository for tracking work items that NEAR One is working on.

0 stars 0 forks source link

[ProjectTracking]: Rainbow bridge / Aurora engine split #52

Open akhi3030 opened 8 months ago

akhi3030 commented 8 months ago

Goals

Currently, the EVM / engine contract implements the ETH connector which represents the native ETH token on Near.

The goal of this project is to split the EVM and the engine contracts to make them independent of each other. This will help with minimising the security risk of the engine and minimise the potential of unintended consequences in the engine when changes are made to the EVM.

Links to external documentations and discussions

https://github.com/aurora-is-near/AIPs/pull/5 https://github.com/Near-One/aurora-eth-connector

Estimated effort

Assumptions

Pre-requisites

Out of scope

### Tasks
- [ ] https://github.com/Near-One/omni-bridge-private/issues/3

karim-en commented 8 months ago

March 13th update: This project was postponed due to more priority tasks. What is left:

Reimplement the migration process and migration tool
Test the migration on testnet

karim-en commented 7 months ago

April 1th update: The new migration logic has been implemented and is now being reviewed. Also, we realised that we need to add extra pause logic to pause the ft-transfer in the Aurora engine.

karim-en commented 6 months ago

April 29 update: All the related PRs have been merged except this one We are planning to merge it during this week and ask the auditors to review the changes. FYI @vzctl

karim-en commented 3 months ago

Jul 29 Update: The bridge and aurora engine teams have successfully migrated the eth-connector on Testnet.

The ETH token address on Near is now eth.sepolia.testnet instead of aurora
All the on-chain calls are redirected from aurora contract to the new eth.sepolia.testnet for backward compatibility.
All view calls made by the off-chain services are broken, e.g., ft_balance_of , is_used_proof, etc.
The Mainnet migration is scheduled for mid-August; until then, we need to test everything and notify our partners.

Todo: Deploy and migrate on Mainnet. The Mainnet migration was planned on mid of Aug, but we found a couple of issues, so it could be postponed to firs of september.

karim-en commented 2 months ago

The migration is planned for Sep 10th