Witness Chain
  • Introduction to Witness Chain
  • Infinity Watch
    • Proof of Location (Mainnet)
      • Introduction
      • Process flow
      • Architecture
      • Run a watchtower!
        • For Partner node runners
          • Running on Akash Cloud
          • Running on SuperNoderz
        • EigenLayer operators
          • Running a PoL Watchtower
          • Witness Chain AVS opt-in guide
        • At-home watchtowers
        • For DePIN/Validator Node provider
      • Demos
      • PoL Research
    • APIs
      • Campaign APIs
        • Key Terminologies
        • Authentication
        • Create Campaign
        • Edit campaign
        • Get Photo feed from campaign
        • Get Campaigns
      • Challenge APIs
        • Overview
        • Getting Started
  • Resources
    • Blogs
      • How Proof of Location Works
      • Redefining Geolocation Compliance: Witness Chain & Predicate
    • 🗞️Research
    • 🎙️Talks and Podcasts
    • 🤝Community
    • ⚖️Smart Contracts
    • File a bug
  • Archive
    • Introduction
    • Proof of Diligence Watchtower Protocol
      • How it works
      • Diligence Watchtower Roadmap
      • Watchtower Architecture
      • Chains watched
      • Smart Contracts
      • Quick Links
      • FAQs
    • For the node operators
      • Node requirements
      • Watchtower setup
        • [ARCHIVE] Mainnet Setup
          • L2 Archive Node Setup guide
        • Holesky Setup
          • L2 Archive Node Setup guide
        • Migration from archive to full node
      • Monitoring
    • Research
    • Keys Management
    • Proof of Bandwidth
      • Introduction
      • Architecture
      • For the node operators
        • Running a PoB Challenger Client
        • Running a PoB Prover Client
      • Demos
      • Research
    • 🤝Watchtower Protocol (Architecture v1)
      • 🗼How it works
      • 📅Watchtower Roadmap
      • 🏦Watchtower Architecture
      • 🔗Chains supported
Powered by GitBook
On this page
  1. Archive
  2. For the node operators
  3. Watchtower setup

Migration from archive to full node

Describes the steps involved to migrate from archive to full node

Rollup node operators can reduce storage cost by changing the type of rollup node. An archive node stores the full state history for each block since genesis block. In contrast, a full node stores the state only for the recent 128 blocks. Therefore, moving from archive node to full node will significantly reduces the storage needs for running rollup nodes.

To migrate the rollup node from archive node to full node, take the following steps:

  1. Stop the current rollup node. Change current working directory to the root of setup-rollup repository.

cd setup-rollup
docker compose down
  1. In geth.yml, change --gcmode from archive to full node.

--gcmode=full
  1. Resume the rollup node

docker compose up -d

Your rollup node should be up now. It will garbage collect the states older than 128 blocks.

PreviousL2 Archive Node Setup guideNextMonitoring

Last updated 7 months ago