-
Notifications
You must be signed in to change notification settings - Fork 451
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Evaluate Running a Passport ETH Archive Node #2793
Comments
erichfi
changed the title
Spike: Passport Eth Archive node
Evaluate Running a Passport ETH Archive Node
Aug 31, 2024
Let's see if we still need a centralized transaction data cache in case we run an Archive Node: #2829 |
Ethereum Node RequirementsMainnet NodesRETH Mainnet
GETH Mainnet
Layer 2 SolutionsOptimism / OP Stack
Arbitrum
Polygon
AWS Configurations for Polygon NodesBasic Node (single to double-digit RPC requests/s)
High-Performance Node (hundreds of RPC requests/s)
Maximum Performance Node (up to 1000 RPC requests/s)
Ethereum Node Testing and Deployment SummaryLocal TestingHardware Specifications
Equipment
Node Synchronization
Performance Test
Data Query Performance
Running Additional Nodes
ISP Requirements
Pricing ConsiderationsLatitude (Suggested by RETH)
AWS
Kammerdeiner
Individual Network Pricing
Other Considerations
Saving on Costs
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
User Story:
As the Passport team,
I want to have unlimited and cost-effective access to Ethereum transaction data,
So that we can efficiently run analyses and query the blockchain without incurring high third-party costs.
Acceptance Critiria
GIVEN the need for detailed blockchain data analysis,
WHEN evaluating different options for hosting an Ethereum archive node,
THEN we should decide on the most cost-effective and efficient setup for Passport.
Exploration Goals
Product & Design Links:
Tech Details:
Open Questions:
Notes/Assumptions:
The text was updated successfully, but these errors were encountered: