comit-network / ambrosia

UI for trading in the COMIT network
Apache License 2.0
4 stars 3 forks source link

Mainnet App Release Plan #5

Closed yosriady closed 4 years ago

yosriady commented 4 years ago

We've worked on the app but have yet to test it with users. We want to ship the app to the mainnet and test with users to get feedback. However before we can do that, we need to implement the following:

1. External Provider Support in SDK https://github.com/comit-network/app/issues/9

Related SDK issue: https://github.com/comit-network/comit-js-sdk/issues/154

The current BitcoinWallet and EthereumWallet provided by the SDK doesn't let us use the Ledger.

Other cross-chain libraries support external wallets using the Provider standard. More details: https://github.com/liquality/chainabstractionlayer

This is still open, early research. I'm not yet certain what needs to be done here, but I think following the Provider standard should give us a modular and extensible wallet support.

2. Fix Electron build pipeline https://github.com/comit-network/app/issues/19

We use Electron to build desktop apps. There's currently a native modules issue that's breaking the build pipeline. Until this is fixed, we can't generate cross-platform application executables.

3. Mainnet Node Infrastructure

The app uses local nodes for testing, but we can't use comit-scripts for production. Before we can package our desktop app, we need to figure out the mainnet node infrastructure:

As a start, we can first allow users to have the create-comit-app example run on mainnet.

4. Deploy and Host Maker backend

Blocker: Mainnet Node infrastructure must be complete before we can deploy a Maker service.

The fixed maker service needs to be deployed and hosted somewhere. This is fairly straightforward.

We should also split the Maker service and the Taker app to separate repos at this point https://github.com/comit-network/app/issues/37

yosriady commented 4 years ago

@D4nte @bonomat