> ## Documentation Index
> Fetch the complete documentation index at: https://docs.monad.xyz/llms.txt
> Use this file to discover all available pages before exploring further.

# Soft Reset Instructions

A soft reset is typically required when node is (re-)joining the network and the node tip is close to the network tip. Soft reset utilizes [statesync](/monad-arch/consensus/statesync) to
determine the difference between the current state and the chain tip and to skip ahead.

<Note title="Automated Remote Configuration Fetching (v0.12.1+)">
  In v0.12.1+, the node will automatically attempt to fetch remote configuration files on startup if env variables are defined:

  * `forkpoint.toml`: Changes every round
  * `validators.toml`: Changes every epoch

  This simplifies node operations by automating configuration updates. The remote fetching includes threshold logic to determine when remote configs should be used.

  **Note**: For automatic remote config fetching (v0.12.1+), ensure `REMOTE_VALIDATORS_URL` and `REMOTE_FORKPOINT_URL` are defined in `/home/monad/.env` file. See [Full Node Installation](/node-ops/full-node-installation#remote-configuration-fetching-v0121) for configuration details.
</Note>

## Automated Soft Reset (v0.12.1+)

Starting with v0.12.1, soft resets are largely automated if the appropriate variables are defined in `.env`:

1. SSH into the node as `root` user
2. Restart monad-related services (`monad-bft` will auto-fetch configs on startup):
   ```bash theme={null}
   systemctl restart monad-bft monad-execution monad-rpc
   ```
3. Verify the systemd services are running:
   ```bash theme={null}
   systemctl list-units --type=service monad-bft.service monad-execution.service monad-rpc.service
   UNIT                    LOAD   ACTIVE SUB     DESCRIPTION
   monad-bft.service       loaded active running "Service file for Monad BFT"
   monad-execution.service loaded active running "Service file for Monad Execution"
   monad-rpc.service       loaded active running "Service file for Monad RPC"

   # Check logs for a specific process to verify config fetching
   journalctl -u monad-bft
   ```

## Manual Soft Reset

To disable the automated fetching, remove any existing definitions (and remove from `/home/monad/.env` if desired)

```bash theme={null}
unset REMOTE_VALIDATORS_URL
unset REMOTE_FORKPOINT_URL
```

1. SSH into the node as `root` user

2. Stop monad-related services
   ```bash theme={null}
   systemctl stop monad-bft monad-execution monad-rpc
   ```

3. Fetch new `forkpoint.toml` and `validators.toml`.

   <Tabs>
     <Tab title="Mainnet">
       ```bash theme={null}
       MF_BUCKET=https://bucket.monadinfra.com
       VALIDATORS_FILE=/home/monad/monad-bft/config/validators/validators.toml

       curl -sSL $MF_BUCKET/scripts/mainnet/download-forkpoint.sh | bash
       curl $MF_BUCKET/validators/mainnet/validators.toml -o $VALIDATORS_FILE
       chown monad:monad $VALIDATORS_FILE
       ```
     </Tab>

     <Tab title="Testnet">
       ```bash theme={null}
       MF_BUCKET=https://bucket.monadinfra.com
       VALIDATORS_FILE=/home/monad/monad-bft/config/validators/validators.toml

       curl -sSL $MF_BUCKET/scripts/testnet/download-forkpoint.sh | bash
       curl $MF_BUCKET/validators/testnet/validators.toml -o $VALIDATORS_FILE
       chown monad:monad $VALIDATORS_FILE
       ```
     </Tab>
   </Tabs>

   You may see the following log message:

   ```bash theme={null}
   failed to fetch remote configs, using local forkpoint and validators config
   ```

4. Start monad-related services
   ```bash theme={null}
   systemctl start monad-bft monad-execution monad-rpc
   ```

5. Verify the systemd services are running:
   ```bash theme={null}
   systemctl list-units --type=service monad-bft.service monad-execution.service monad-rpc.service
   UNIT                    LOAD   ACTIVE SUB     DESCRIPTION
   monad-bft.service       loaded active running "Service file for Monad BFT"
   monad-execution.service loaded active running "Service file for Monad Execution"
   monad-rpc.service       loaded active running "Service file for Monad RPC"

   # Check logs for a specific process, e.g. bft
   journalctl -u monad-bft
   ```

## Configuration Details

### Forkpoint Serialization

Starting with v0.12.1, forkpoints are serialized in both TOML and RLP formats:

* **RLP format**: Source of truth
* **TOML format**: Maintained for backward compatibility
* If TOML serialization fails, the node will no longer panic
* Nodes can start from either format for operational backwards compatibility