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 Dec 4, 2024. It is now read-only.
OpenEthereum nodes will be deprecated and therefore no new Ethereum hardforks will be supported. As we rely heavily on OpenEthereum nodes for tracing we need to find an alternative.
The current alternative is Erigon, but it is still in beta and there are still some performance considerations to be made.
What value does this bring to our customer and/or our mission? What is the goal?
Erigon is a large project that is supported by many team and it would provide a secure way how to continue using tracing in the long run. Tracing allows us to provide more correct and detailed data that does not rely on events and therefore are more gas efficient.
Testing Erigon for the networks supported by it. With some optimizations for the tx-service syncing process from scratch looks really promissing and might be completed in 15 days.
For Gnosis Chain, not supported yet by Erigon, there are 2 solutions:
Forcing the users to update to a L2 master copy. This would be my preferred option.
Use the other node supporting tracing and Gnosis Chain: Nethermind. Last time it didn't work well for us, it required an archive node and was really slow compared to OpenEthereum.
Rough Scoping & Timeline Risk(s), Key Trade Offs & Decisions
Using a L2 master copy:
Advantages:
Any standard node supporting events (Nethermind) will work
Risks:
- Users not updating and having their UIs broken
- Backend needs some refactoring to support non L2 -> L2 migration
Using Nethermind:
Advantages:
- No need for backend changes
Risks:
- Node not being fast enough
- Nethermind dependency
Alternative solutions & ideas
Open Questions
The text was updated successfully, but these errors were encountered:
Define the problem
What problem are you trying to solve?
OpenEthereum nodes will be deprecated and therefore no new Ethereum hardforks will be supported. As we rely heavily on OpenEthereum nodes for tracing we need to find an alternative.
The current alternative is Erigon, but it is still in beta and there are still some performance considerations to be made.
What value does this bring to our customer and/or our mission? What is the goal?
Erigon is a large project that is supported by many team and it would provide a secure way how to continue using tracing in the long run. Tracing allows us to provide more correct and detailed data that does not rely on events and therefore are more gas efficient.
How do we measure it?
Links:
Solutions
Shaping the problem
Click to expand!
Problem Owner
@Uxio0
Non Goal(s)
Solution
Overview
tx-service
syncing process from scratch looks really promissing and might be completed in 15 days.Nethermind
. Last time it didn't work well for us, it required an archive node and was really slow compared toOpenEthereum
.Rough Scoping & Timeline
Risk(s), Key Trade Offs & Decisions
Using a L2 master copy:
Advantages:
Risks:
- Users not updating and having their UIs broken
- Backend needs some refactoring to support non L2 -> L2 migration
Using Nethermind:
Advantages:
- No need for backend changes
Risks:
- Node not being fast enough
- Nethermind dependency
Alternative solutions & ideas
Open Questions
The text was updated successfully, but these errors were encountered: