L1 -> L2 deposit

[zamrokk]

MOTIVATION: send Tz or Ctez to a Layer 2 rollup address

SCENARII:

Feature: rollups

  Scenario: Deposit Tz
    Given user U is connected
    Given user U has balance of 3.5 Tz
    Given Qty is 2 Tz
    Given rollup R is tru1AAAAAAAAAA
    Given L2 address is tru2EEEEEEEEEEEE   
    When user U clicks on "Deposit" button
    Then L1 address storage is 1.5 Tz
    Then L2 address storage is 2 Tz

DETAILED DESIGN:

• we can access to this page either by having a colum ACTION on each row of rollup from the home page table, or either have a button on the banner "DEPOSIT". We have to be logged with L1 Layer to be able to do any interaction with deposit. It means that the "Deposit" button is "connect wallet" button if user is not logged
• Once user is connected, The L1 address should appear on the left box with Tz and ctez balances
• rollups should be a combobox prefilled. The title of L2 box is updated with same info
• Layer 2 input should be an input field with Tezos address mask. The title of the L2 box is updated with same info
• Qty should be a positive number
• Qty type should be Tz or Ctez
• if user clicks on one of its balance on left box, then Qty is filled with user balance and Qty type is the balance type
• once user has clicked on deposit, we wait with an icon and lock the screen until Tezos tx is not confirmed. Once done, popup success message and update L2 storage content, otherwise popup an error message with details

[zamrokk]

• [X] generate l2 address
• [X] adapt code from deku to toru
• [X] Deposit
• [X] Fecth ticket hash from block results
• [ ] Get l2 balance (issue with rollup node locally)
• [ ] withdraw (idem)

[zamrokk]

dead lock :

• on jakartanet, I can go until deposit but rollup cannot connect to tezos node
• on nextnet, I cannot go until the deposit (BeaconSDK : "proto.013-PtJakart.contract.non_existing_contract") but the contract is really deployed, and the rollup node works correctly with the Tz node.

CLI on jakarta cannot see the smart contract whereas it deployed it correctly with nextnet endpoint (like it is not recognized as a smart contract .... weird). This confirms the error jakartanet/nextnet I can have with the BeaconSDK

Let's wait for release of Jakarta next week on mainnet to ckeck if issues are gone

[zamrokk]

done