Rotki allows users to introducethe RPC endpoint of its own ETH node to make the requests instead of using the default Etherscan API, this feature will:
- Ensure user privacy
- Makes requests faster
In the Rootki UI is possible to introduce the RPC endpoint:
Solution 1
Ideally this should be done during the installation process, asking the user to introduce its own RPC eth endpoint. Then modifying the docker image entrypoint: https://github.com/rotki/rotki/blob/6b84e27df5e953162d42a159e6729942bbe1719d/packaging/docker/docker-entrypoint.sh#L3
From --api-cors http://localhost:8080 to the user input (e.g geth endpoint selection)
To achieve this would be necessary a new dappmanager api endpoint to ask which ETH node is the "fullnode" set in the repository source: dappnode/DNP_DAPPMANAGER#824
Solution 2
Instead of create a new dappmanager api endpoint use the existing ones to determine if eth client is present:
geth > openethereum > nethermind > etc
Rotki allows users to introducethe RPC endpoint of its own ETH node to make the requests instead of using the default Etherscan API, this feature will:
In the Rootki UI is possible to introduce the RPC endpoint:
Solution 1
Ideally this should be done during the installation process, asking the user to introduce its own RPC eth endpoint. Then modifying the docker image entrypoint: https://github.com/rotki/rotki/blob/6b84e27df5e953162d42a159e6729942bbe1719d/packaging/docker/docker-entrypoint.sh#L3
From
--api-cors http://localhost:8080to the user input (e.g geth endpoint selection)To achieve this would be necessary a new dappmanager api endpoint to ask which ETH node is the "fullnode" set in the repository source: dappnode/DNP_DAPPMANAGER#824
Solution 2
Instead of create a new dappmanager api endpoint use the existing ones to determine if eth client is present:
geth > openethereum > nethermind > etc