Bridge Working Group Update [2021-03-05]

[alexauroradev]

The video of the call is available here
The forum discussion is available here

Agenda

• Status, current goal
• Updates
• Next week
• Discussion

Status, current goal

Release in 10 days: core bridge, ERC20 connector and FE; continuing the work on eth-connector

Planned items:

• AS: upgrades flow, hiring
• MF: testing (upgradability), upgrade testnet deployment
• EK: Bridge 2.0. upgradability PR, fixes of Bridge 1.0
• KA: make eth-connector work (integration test), eth-connector:#21
• PAO: network selection feature, transaction status issues

Done:

• AS: upgrades flow (internal document), one candidate passed all the interviews
• MF: testing (upgradability)
• EK: Upgradability PR, fixes of Bridge 1.0
• KA: working on eth-connectors
• PAO: network selection feature, transaction status issues

Weekly update

Alex Shevchenko

• Hiring
• eth-connector
• Management tasks (see bridge project)
• Checklists for the bridge upgrades

Marcelo Fornet

• Features:
  • Pausing the bridge
  • NEP-141 standard integration (eth-connector:#21)
• Upgradability discussions

Eugene Kapun

• Preparing for the launch
• Still need to add some improvement to AdminControlled:
  • update a part of the storage slot // bitmasked SSTORE.
  • Combined JSON for compilation outputs instead of two files (.full, .abi)

Kirill Abramov

• Small tasks: 2 PR for Trustless NearClient #35 Near2EthProver #36 for rainbow-token-connector
• Upgradability discussions
• NEP-21 -> NEP-141 eth-connector:#21, but the code was submitted by Illia
• Improvements in AdminControlled
• Working on eth-connector: Trustful ETH contract for Near #7 merged, Relay for Near headers into Eth contract #9 created

Pierre-Alain Ouvrard

• Bridge selection dropdown feature (selection of the deployments) merged
• Improvements of the network handling & account change handling
• Fixed the approval issue rainbow-bridge-frontend:#97
• Fixed the issue with checks on Ethereum (network problems)
• Some work on hosting service

Next week

• Alex: test the eth-connector, do the upgrade of the bridge on the testnet, support the release of the mainnet bridge
• Marcelo: finalise NEP-141 migration, finalise interfaces updates with JS relayers, test deployment and upgrade processes
• Eugene: supporting upgrades and deployments of the bridge
• Kirill: finalise NEP-141, supporting upgrades and releasing the mainnet bridge
• Pierre-Alain: finish PR with Ethereum network handling, update the FE to NEP-141

Discussion

• NEP-141 how would mint function work?
  • Attach some tokens every time OR
  • Have a separate function for account creation
  • Have two deposit functions: one is #[payable] and is able to create an accout and the other is not #[payable]
  • Solution: #[payable] registerAccount(tokenAccount, userAccount) function in the Factory + non-payable deposit
  • AI: Check with Wallet team on removing the proxy function above

UPDATE: Checked with Illia and Eugene on the #[payable] functions. Making #[payable] mint will still allow the attachment of 0 yoctoNEAR and thus won't cause the confusion for the user. So, FE will determine whether the account is created and if not, it will attach non-zero deposit. Everything will be done in a single transaction, no need to do batched transactions.