You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 12, 2022. It is now read-only.
Currently, eth-contract-watcher can use the minimal set of standard eth JSON-RPC endpoints exposed by an instance of the ipfs-blockchain-watcher to function in the same exact way as it functions with a geth node. This still requires and anchors data to headers synced by eth-header-sync.
Optionally (and preferably) we should anchor all of the transformed eth-contract-data directly to the eth.headers_cids from ipfs-blockchain-watcher (which themselves are fk linked to the rest of the ethereum data on ipfs). This is the final step to foreign key linking all of the contract data processed by eth-contract-watcher to readily provable data structures.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Currently, eth-contract-watcher can use the minimal set of standard eth JSON-RPC endpoints exposed by an instance of the ipfs-blockchain-watcher to function in the same exact way as it functions with a geth node. This still requires and anchors data to headers synced by eth-header-sync.
Optionally (and preferably) we should anchor all of the transformed eth-contract-data directly to the eth.headers_cids from ipfs-blockchain-watcher (which themselves are fk linked to the rest of the ethereum data on ipfs). This is the final step to foreign key linking all of the contract data processed by eth-contract-watcher to readily provable data structures.
The text was updated successfully, but these errors were encountered: