-
Notifications
You must be signed in to change notification settings - Fork 37
Open
Description
I forgot about some of the parameters for this, so very much a WIP.
Primary target is: reliably & quickly sync Trinity with mainnet. To me, that means a >90% likelihood of executing 100 contiguous blocks from the tip, within a half hour, & maintaining less than 15 minute lag for 2 hours. We're a PR away from hitting this target on a local peer, but a lot remains in order to work with remote peers.
Beyond the basic Beam Sync implementation, that means:
- benchmark against remote peers, bring performance in line
- add some methods to a firehose subprotocol, like: block witness metadata and account proofs in a single request
- finding and connecting to other trinity peers
- backfilling cold state
Secondary goals, in descending priority:
- a standard JSON-RPC API for
eth_*methods (excluding methods that require keys to be hosted by the node) - collect data and author findings about mainnet: how big are witnesses? how hot is the data? what is the read/write ratio? etc
- Work with EIP authors to become the favored prototype mechanism for new Core EIPs
- Clique PoA support
- clean up warnings
Metadata
Metadata
Assignees
Labels
No labels