Add another snapshot provider #355
Conversation
✅ Deploy Preview for docs-optimism ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Warning Rate Limit Exceeded@sbvegan has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 26 minutes and 1 seconds before requesting another review. How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. WalkthroughThe documentation update includes a hyperlink to provide easy access to actual snapshots for the mainnet. This enhancement aims to assist node operators by providing a direct link to the necessary snapshots within the tutorial guide. Additionally, a warning about a third-party snapshot provider, FastNode, has been included along with a link to their service. Changes
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configration File (
|
|
TLDR: Fastnode provided an alternative OP mainnet snapshot solution >> https://datapoint.fastnode.io/ Thank you for providing an OP mainnet snapshot. Would like to know if we can have an endpoint that dynamically fetch the latest snapshot file name. |
|
This would be helpful for Sepolia too. Do you run on said network? 🙏🏻 |
|
This is awesome, thank you for providing this service. My only suggestion is around the wording and highlighting that this is a third party provided snapshot. |
|
Look like this archive extract to a folder named op-dir with geth inside. It would be better to extract to only geth folder (no op-dir wrapper) as the official snapshot has this behavior. |
|
@Chomtana I'm having trouble downloading the full file - can you please share what the directory structure looks like? |
|
I'd also like to change this PR so that it changes the snapshots.mdx page instead. I'll modify the tutorial to point to that page. I'm going to make a PR to update the snapshots.mdx page with the correct format so you can add your link(s). |
@felipe-op Like this it's wrapped in an op-dir folder while the correct one should extract directly to the geth folder You should be able to use to extract file Like this |
|
Hey @ynvv would you be able to update the directory structure to address the comment above? Hey @cpengilly and @smartcontracts, what do you guys think about adding a callout for the correct directory structure so we can get this PR in now? I have folks asking for full node snapshots and I'm directing them to this PR instead of the docs. |
|
Hello, guys! We will upload a new snapshot soon, which will contain all the edits that were discussed here. There will also be a permanent link to the latest snapshot |
|
@ynvv Does this snapshot include the activation? I see it is dated 12-16-2023 so just wondering? Thanks for doing this! |
|
Thank you that snapshot worked for me ! |
|
Hello, guys! We have changed the structure of the archive: now only the geth folder is inside the archive (without the op-volume folder) We also added the ability to download the first up-to-date snapshot of all that we have (details on the website above) (@Chomtana for u) |
|
@Sleapy31 which snapshot didn't work for you? |
OP Mainnet (Full Node) despite the checksum being correct. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
|
@Sleapy31 okay thats weird, I imagine it was something else that caused the errors because that snapshot has worked for others spinning up OP Mainnet nodes. If you have questions like this in the future, you can direct them to our forum and we can help you answer them. https://github.com/ethereum-optimism/developers/discussions |
Description
Hello! I am Artem from fastnode.io
We are aware of the community's concerns about the lack of fresh op-geth snapshots - we already have an extensive number of internal snapshots, which we are ready to share with the OP community!
We are ready to update them every week so that community can raise nodes in a few hours, not in a few weeks.
Tests
Please describe any tests you've added. If you've added no tests, or left important behavior untested, please explain why not.
Additional context
Add any other context about the problem you're solving.
Metadata