https://github.com/JakubNer/overhide-ethereum/blob/77e54ebefdd19d23425d1b401308a98ee6f99cdb/main/js/lib/eth-chain.js#L3
Consider advantages--if any--of running own Ethereum client node for the purposes of overhide-ethereum.
It's easy enough to add a geth client as a docker container into our swarm, but it would make more sense if our client node would cache transaction to/from/timestamp information: something standard geth/web3.js seems not to be built for (hence our use of etherscan.io).
This was the original approach but changed to using etherscan.io for time being; see commit: https://github.com/JakubNer/overhide-ethereum/blob/384cdae3b8c5d3963f864665e6d47b490bd8316c/package.json#L49
https://github.com/JakubNer/overhide-ethereum/blob/77e54ebefdd19d23425d1b401308a98ee6f99cdb/main/js/lib/eth-chain.js#L3
Consider advantages--if any--of running own Ethereum client node for the purposes of overhide-ethereum.
It's easy enough to add a geth client as a docker container into our swarm, but it would make more sense if our client node would cache transaction to/from/timestamp information: something standard geth/web3.js seems not to be built for (hence our use of etherscan.io).
This was the original approach but changed to using etherscan.io for time being; see commit: https://github.com/JakubNer/overhide-ethereum/blob/384cdae3b8c5d3963f864665e6d47b490bd8316c/package.json#L49