Remove `redux` and `ldk`, refactor using `liquidjs-lib` and electrum websocket endpoint

[louisinger]

This PR removes redux, redux-saga, webext-redux and ldk packages from Marina.

• replace redux based storage by repositories interfaces in src/infrastructure. The repositories classes are using Browser.storage to store and access data from local browser extension storage. Repositories can be used everywhere (including React components).
• src/infrastructure/storage provides react hooks based on Browser.storage.onChanged event listener. It lets to reproduce the behavior of redux useSelector hook.
• most of src/content and src/inject are unchanged. They are just using Repository interfaces instead of redux state.
• Account is now a class able to generate scripts, create confidential addresses and sync the wallet (its a kind of "watch only wallet").
• SignerService is a class letting to sign psetv2 using marina Repository interfaces.
• BlinderService is a class letting to blind psetv2 using marina Repository interfaces.
• background-script.ts is reponsible to update the wallet state using several async services (Subscriber, Updater and TaxiUpdater) listening to Browser.storage.onChanged events

TODO:

• [x] Fix wallet/send flow (psetv2 coin selection bug at choose-fee step).
• [x] Taxi topup support in send flow.
• [x] Custom script Account -> related to #427
• [x] Implement connect/send popup.

@bordalix @tiero please review

[Janaka-Steph]

I am looking at using React-Query (https://tanstack.com/query/latest) to manage Esplora data, but afaik it returns either data or error. If I use ws.batchRequest to get transactions and one of them fails the whole operation fails. What about returning successful data, if any, along with promise rejection error inside ElectrumWS onMessage ? More broadly, what is your strategy when a request fails inside a batchRequest ?

[Janaka-Steph]

I noticed that we have txID, txid, txHash from LiquidJS. Would be nice to harmonize that.

[louisinger]

UPDATE Latest commits add full support of Ionio accounts. Some small breaking changes in marina-provider has been introduced. The docs.vulpem.com update describes them and adds an example related to Ionio account.

It should be enough to test and discuss new APIs @tiero @bordalix

I keep this PR as draft, some required WIP:

• [x] Add tests of the application layer (Account, SignerService and BlinderService).
• [x] Let the user download a restoration file with Ionio account data in settings/accounts.
• [x] Let the user upload restoration files in onboarding/restore.

Test yourself: marina-0.4.14.zip

[louisinger]

marina-0.4.14.zip

The latest version adds Ionio accounts restoration (download a file in settings/accounts and upload it in onboarding/wallet-restore form) + Liquid Taxi support.

[tiero]

By default first start the explorer is set to Custom. Is this wanted?

[tiero]

I would put in the placeholder an example of what we need. ie. https://blockstream.info and wss://vulpem.com

[tiero]

I would add also the base derivation path for each account listed here

[tiero]

If possible I would put the Updating... in the navbar during the restoration/fetching of history

[tiero]

• Reason why these assets have no balance? not even 0

• I know we are lazy loading the timestamp, but we should then cache it. Going back and forth the tx history page, will loose the timestamps already loaded, and seems it starts fetching again.

Alternative would be to move from the date to the type (Inbound, Outbound, Multiple)

• Is there a reason why we have to "refetch" data already store? going back and forth seems we go from epty to state to full state every time, which should not be the case, I assume we have all cached.

https://www.loom.com/share/46550313f0a148a58c7b3668560410b2

[tiero]

Best to write Unconfirmed here, maybe as tag using the red or yellow background

[tiero]

The sending flow has some glitches:

• for some reason was giving to a perfect valid address as not valid. To make it work you need to copy paste second time.
• I dont understand why is taking do much time when selecting l-btc as asset to pay for fees: is needed all of this to do what exactly? coin-selection?
• EVery time you ckick one of these currencies, I assume you lock an utxo as the balance def decreae: if you close the extension and re-open or click and unlick, you forgot to unlock those utxos

https://www.loom.com/share/ab92c4fd7a8e44e6a310f131df51df31

[louisinger]

You can test using manifest v3 with the command yarn start:v3. Same for build yarn build:v3 will build the extension using manifest v3.

[tiero]

nit: overlay background does not cover all extension

[bordalix]

It stays like this forever, i.e., doesn't find out that tx are already confirmed:

Also, (unconfirmed) hides the value of the transaction.

[bordalix]

L-BTC balance (on the assets list) should be '0' and not absent as is now:

[bordalix]

Date area needs to have less width or else value of the tx is wrapped:

[bordalix]

I'm getting blinding errors on mempool and blockstream when seeing a contract creation tx:

https://liquid.network/testnet/tx/0e82f8fca8f968bff3b78c64d7c0f6bb18f94f3d331861c486a770c300143746#blinded=84897,144c654344aa716d6f3abcc1ca90e5641e4e2a7f633bc09fe3baf64585819a49,d6fd0b0dda248b46903ed123a6c0bf7dbb55082f671033289bd3a472434a9bc7,fd1f57f5dfe08560e74c05abd97e3b5635c5831867ace8ed65b920cf2d3cbcf9,21680168,144c654344aa716d6f3abcc1ca90e5641e4e2a7f633bc09fe3baf64585819a49,bfeb9a4d8e1de578bb014e264a21c93715cc6dc4233bc3c948dc2cfcd881e48b,1c923c8f54bd7237274b1a0ae9aead67affb0c4f33c748394e41f8725765ba5c,1100000000,0d86b2f6a8c3b02a8c7c8836b83a081e68b7e2b4bcdfc58981fc5486f59f7518,0000000000000000000000000000000000000000000000000000000000000000,0000000000000000000000000000000000000000000000000000000000000000

[bordalix]

L-BTC list of Tx only shows fee spent:

[bordalix]

1. Create contract
2. Export marina-ionio-restoration.json
3. In marina, restore account
4. Restore with same mnemonic and json file from 2
5. Contracts has status "unknown" (I will check why)
6. When I try to close the contract, I get this error:

[tiero]

Can you please try to "Restore account" from a wallet already initialized? For some reason I always get invalid password that way @louisinger

[tiero]

Can we have to fetch registry to pull assets every time we load the homepage?

Seems it fails to fetch asset, ticker and name first time and it nevers recover

[tiero]

Shall we add a button into either Accounts or in Deep Restore to be able to import the restoration file if needed?

[tiero]

[tiero]

When L-BTC is part of tx and used as fee input to cover the fee output, it should not be shown in the L-BTC history?

[bordalix]

When I try to send all LBTC to myself I get a min relay fee not met, 0 < 134

https://user-images.githubusercontent.com/9318412/225405661-475dbab3-9029-4ef5-8156-6c9a88f86291.mov

Also, Retry button does nothing.

[louisinger]

Can you please try to "Restore account" from a wallet already initialized? For some reason I always get invalid password that way @louisinger

Unable to reproduce this @tiero using manifest v2 & v3 extensions built from sources

[bordalix]

@louisinger not sure if it's the same thing as @tiero reported, but my first login after restoring an account always gives this error:

Clicking on "Log in" again works.

[bordalix]

Log out NEVER works on first click:

https://user-images.githubusercontent.com/9318412/225659918-5084e209-7755-4f6d-be6e-38155e8644cd.mov

[tiero]

Let's merge and continue issue by issue