Migration to xDAI (APM + Directory) #327
Description
In the ethos of maximal decentralization DAppNode distributes its packages in a blockchain-based registry. Doing that in Ethereum mainnet has become too expensive (started late 2018), so we must migrate to a cheaper chain.
DAppNode will migrate it's package manager + package directory contracts. This contracts track package versions in a decentralized way, and are consumed by all DAppNodes.
Summary
- Re-design and deploy package manager contracts. We will not deploy APM contracts as mainnet, since they don't fullfil all our needs @dappnode/dappnode-team
- Re-design in progress here -> https://github.com/dappnode/dappnode-package-manager
- (Skip, todo later) Re-design and deploy directory contracts. Consider in the future to upgrade to a TCR @dappnode/dappnode-team
- Deploy (or consume) ENS to support above two points @Pol-Lanski
- Move existing versions to xDAI. How to migrate packages not own by DAppNode, maybe add a migration UI? eduadiez
- Add xDAI package eduadiez https://github.com/dappnode/DAppNodePackage-nethermind-xdai
- Change DAPPMANAGER package consumer code to use xDAI dapplion - Track package registries in xDAI DNP_DAPPMANAGER#966
- Change remote repository logic to use xDAI nodes dapplion
- Deploy and mantain an xDAI node for remote repository consumers 3alpha
- Update sdk-publish to support new DPM repo Support publishing to xDAI (ON HOLD) sdk-publish#17
- Update dappnode-sdk logic to support new DPM repo
┆Issue is synchronized with this Basecamp todo by Unito