DNP_DAPPMANAGER
DNP_DAPPMANAGER copied to clipboard
Dappnode package responsible for providing the Dappnode Package Manager
Right now the auto-updates are set to be triggered after a random number of hours between 24h and 48h:  We could add an input in the auto updates page...
The function `getStakerCompatibleVersionsByNetwork` checks if a specific client is compatible with the current version of the dappnode. If there is no minimum version defined, the client should be compatible
It seems this line below was updated in a way that is far too complex, and instead of just going to a single static page at `http://my.dappnode/system/network` it just makes...
Create a test module for shared test utilities across modules such us directories and functions. Also share test envs such as an ethereum RPC url and IPFS url. Do not...
The installer module is still quite complex and should be simplified. Consider removing the ethClient implementation into a separated module. Think fora a better place for `calls`. Depends on https://github.com/dappnode/DNP_DAPPMANAGER/pull/1700
Completely remove `utils` from dappmanager and try to find a place for each utility.
At this moment the module `dappmanager` is in charge of serving the api to the frontend (`admin-ui`) through `socket.io`. All the calls are located under folder `calls`. The calls logic...
Use a single http API client library across the codespace instead of having multiple: `got`, `node-fetch`... Consider using `node-fetch`
Research for core packages hardcoded IPs in the code and switch to docker alias when possible
Create a new metric for mev boost relays to be tracked by ethical metrics. Metrics to collect: - How many relays - Which releays There should be retrieved from mev...