arc-testnet: Add snapshot-init service (defc6046) #30

Closed
claude wants to merge 1 commits from issue-848 into main
Collaborator

Summary

Arc testnet pruned node on de-32 was ~17k blocks behind due to stale bootstrap snapshot + public RPC rate limits. Added snapshot-init service that auto-downloads latest Arc testnet pruned snapshot on container startup.

Asset changes

  • rpc/arc/scripts/snapshot-init.sh — shell wrapper around arc-snapshots download with optional env var overrides
  • rpc/arc/arc-snapshot-init.Dockerfile — debian + arc-snapshots binary

Verification

  • Regenerated arc-testnet-reth-pruned-trace.yml includes arc-testnet-snapshot-init service only for testnet+pruned profile
  • Consensus init waits on snapshot-init completing
  • Will redeploy to de-32 and verify sync reaches head

Vibe-node issue #848 (source PR pending on vibe-node repo)

## Summary Arc testnet pruned node on de-32 was ~17k blocks behind due to stale bootstrap snapshot + public RPC rate limits. Added snapshot-init service that auto-downloads latest Arc testnet pruned snapshot on container startup. ## Asset changes - `rpc/arc/scripts/snapshot-init.sh` — shell wrapper around `arc-snapshots download` with optional env var overrides - `rpc/arc/arc-snapshot-init.Dockerfile` — debian + arc-snapshots binary ## Verification - Regenerated `arc-testnet-reth-pruned-trace.yml` includes `arc-testnet-snapshot-init` service only for testnet+pruned profile - Consensus init waits on snapshot-init completing - Will redeploy to de-32 and verify sync reaches head Vibe-node issue #848 (source PR pending on vibe-node repo)
claude added 1 commit 2026-07-04 06:17:42 +00:00
Shell entrypoint wraps arc-snapshots so compose can optionally override EL/CL
snapshot URLs via ARC_SNAPSHOT_* env vars while defaulting to latest from
snapshots.arc.network on fresh volumes.
Owner

never initialize nodes as part of the compose file or Dockerfile ... let that be done by the onsite agent on de-32 (the bench) to then create a backup that can be restored elsewhere

never initialize nodes as part of the compose file or Dockerfile ... let that be done by the onsite agent on de-32 (the bench) to then create a backup that can be restored elsewhere
sebastian closed this pull request 2026-07-04 09:00:01 +00:00

Pull request closed

Sign in to join this conversation.
No Reviewers
No Label
2 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: StakeSquid/ethereum-rpc-docker#30