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
To avoid the rate limiting issues we are experiencing by proceeding through the go-ethereum RPC server interfaces (e.g. EOFs) we should have an option to write statediffs directly to Postgres, directly analogous to cerc-io/go-ethereum#30
We should be able to operate it in two modes:
Load the desired ranges from the .toml params, index statediffs from LevelDB directly into Postgres for the blocks in those ranges, and exit
Service runs indefinitely, awaiting RPC calls which tell it which historical blocks for which to index statediffs from LevelDB directly into Postgres
The text was updated successfully, but these errors were encountered:
To avoid the rate limiting issues we are experiencing by proceeding through the go-ethereum RPC server interfaces (e.g. EOFs) we should have an option to write statediffs directly to Postgres, directly analogous to cerc-io/go-ethereum#30
We should be able to operate it in two modes:
The text was updated successfully, but these errors were encountered: