# Mainnet Buenos Aires Reboot

Due to a mainnet reboot and ledger backtrace to **epoch 10**, all validators need to manually reset and reconnect. Follow this short guide to restore your node and rejoin the X1 network.

***

## ✅ Steps to Get Back on X1

### 1. Stop the Validator

Shut down your validator cleanly:

```bash
tachyon-validator exit -f
```

> Alternatively, check running processes:
>
> ```bash
> ps aux | grep validator
> ```
>
> And terminate with `kill <PID>` if needed.

***

### 2. Remove Old Ledger

Delete the outdated ledger:

```bash
rm -rf ledger
```

***

### 3. Connect to the Correct RPC

Make sure you're using the official X1 mainnet RPC:

```bash
solana config set -u https://rpc.mainnet.x1.xyz/
```

***

### 4. Update Validator Startup Script for Mainnet

Open your validator startup script:

```bash
nano $HOME/bin/validator.sh
```

Replace its contents with:

````bash
### 4. Update Validator Startup Script for Mainnet

Open your validator startup script:

```bash
nano $HOME/bin/validator.sh
````

Replace its contents with:

```bash
#!/bin/bash
export RUST_LOG=solana_metrics=warn,info

exec tachyon-validator \
  --identity $HOME/.config/solana/identity.json \
  --vote-account $HOME/.config/solana/vote.json \
  --entrypoint entrypoint0.mainnet.x1.xyz:8001 \
  --entrypoint entrypoint1.mainnet.x1.xyz:8001 \
  --entrypoint entrypoint2.mainnet.x1.xyz:8001 \
  --entrypoint entrypoint3.mainnet.x1.xyz:8001 \
  --entrypoint entrypoint4.mainnet.x1.xyz:8001 \
  --known-validator 7ufaUVtQKzGu5tpFtii9Cg8kR4jcpjQSXwsF3oVPSMZA \
  --known-validator 5Rzytnub9yGTFHqSmauFLsAbdXFbehMwPBLiuEgKajUN \
  --known-validator 4V2QkkWce8bwTzvvwPiNRNQ4W433ZsGQi9aWU12Q8uBF \
  --known-validator CkMwg4TM6jaSC5rJALQjvLc51XFY5pJ1H9f1Tmu5Qdxs \
  --known-validator 7J5wJaH55ZYjCCmCMt7Gb3QL6FGFmjz5U8b6NcbzfoTy \
  --only-known-rpc \
  --log $HOME/validator.log \
  --ledger $HOME/ledger \
  --rpc-port 8899 \
  --full-rpc-api \
  --dynamic-port-range 8000-8020 \
  --wal-recovery-mode skip_any_corrupted_record \
  --limit-ledger-size 50000000 \
  --enable-rpc-transaction-history \
  --enable-extended-tx-metadata-storage \
  --rpc-pubsub-enable-block-subscription \
  --full-snapshot-interval-slots 5000 \
  --maximum-incremental-snapshots-to-retain 10 \
  --maximum-full-snapshots-to-retain 50

```

Save and exit the editor.

***

### 5. Go to Your Keypair Directory

Navigate to the folder where your Solana keypairs are stored:

```bash
cd ~/.config/solana
```

***

### 6. Set the Correct Signer (Identity Keypair)

Tell Solana CLI to use the correct identity key:

```bash
solana config set -k ~/.config/solana/id.json
```

***

### 7. Start the Validator

From your home directory, start the validator:

```bash
cd $HOME
nohup $HOME/bin/validator.sh &
```

Monitor validator logs to verify it's running:

```bash
tail -f $HOME/validator.log
```

### 8. Check and Manage Stakes

Inspect your stake account:

```bash
solana stake-account stake.json
```

* ✅ If your stake was delegated **before epoch 11**, it remains valid.
* ❌ If delegated **after epoch 11**, you'll need to **re-delegate**.

Use this guide to re-delegate: 👉 <https://docs.x1.xyz/validating/connect-validator-to-x1-mainnet>

***

### 9. Makeup

Do it:\
👉 [Validator Misc Commands](https://docs.x1.xyz/validating/misc-commands)

***

### 10. Confirm You’re Listed

Check validator visibility and status:

* [View on x1val.online](https://mainnet.x1val.online/)
* [View on Fortiblox Explorer](https://explorer.fortiblox.com/)

***

## Notes

* Epoch 10 is the new genesis point after master node reset.
* Stakes initiated prior to epoch 11 should auto-activate, but verify.
* Validators must reset ledger and reconnect to RPC cleanly.

Need help? Ping us in Telegram.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.x1.xyz/validating/mainnet-buenos-aires-reboot.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.