Matthew Darwin
Matthew Darwin
I'm not sure that failing back to RPC from firehose is the correct solution.
Also support downloading from S3 bucket, which would require AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY
Also support zstd and lz4 compression. Different snapshot providers use different compression algorithms. (They probably also use different directory layouts, additional challenge)
I am also getting the "not found" dialog box with ``` [unified_alerting] enabled = false ```
CC @YaroShkvorets on cli requirements
Probably not resolved. Erigon3-beta2 should be out soon, might fix some things.
FWIW I could (and have) run rpc-poller on chains that support full blocks. (We have a few today we're converting to full blocks, but initially were set up with RPC...
IMO kinda hidden environment variables that change graph-node behaviour for specific chains are hard to understand when a node operator is setting up new chains. Forcing them to think about...
Asside: As I brought up during recent off-site, I would ideally like to get away from forcing graph-node restart to add/remove/change a chain configuration. There are 100s of new chains...
Related issue: https://github.com/streamingfast/firehose-ethereum/issues/92