T2 docs

src/pages/guide/node/network-upgrades.mdx

@@ -15,6 +15,8 @@ For detailed release notes and binaries, see the [Changelog](/changelog).
 
 | Release | Date | Network | Description | Priority |
 |---------|------|---------|-------------|----------|
+| [v1.5.0](https://github.com/tempoxyz/tempo/releases/tag/v1.5.0) | Mar 26, 2026 | Moderato + Mainnet | Required for T2; implements compound transfer policies (TIP-1015), permit support for TIP-20 (TIP-1004), ValidatorConfig V2 (TIP-1017), and 14 audit-driven bug fixes (TIP-1036) | <Badge variant="red">Required</Badge> |
+| [v1.4.3](https://github.com/tempoxyz/tempo/releases/tag/v1.4.3) | Mar 18, 2026 | Moderato + Mainnet | Fixes gas price oracle poisoning that caused inflated fee estimates for wallet transactions | <Badge variant="yellow">Recommended</Badge> |
 | [v1.4.2](https://github.com/tempoxyz/tempo/releases/tag/v1.4.2) | Mar 16, 2026 | Moderato + Mainnet | Strict payment calldata validation in the transaction pool and block builder, rejecting malformed payment transactions earlier | <Badge variant="yellow">Recommended</Badge> |
 | [v1.4.1](https://github.com/tempoxyz/tempo/releases/tag/v1.4.1) | Mar 12, 2026 | Moderato + Mainnet | Transaction pool DoS-hardening, consensus resilience improvements (DKG recovery), hardfork-aware gas estimation, and payload builder enhancements | <Badge variant="yellow">Recommended</Badge> |
 | [v1.4.0](https://github.com/tempoxyz/tempo/releases/tag/v1.4.0) | Mar 5, 2026 | Moderato + Mainnet | Required for T1C; introduces keychain signature migration so only V2 signatures and hashes are accepted after activation | <Badge variant="red">Required</Badge> |
@@ -23,6 +25,19 @@ For detailed release notes and binaries, see the [Changelog](/changelog).
 
 ---
 
+## T2
+
+| | |
+|---|---|
+| **Scope** | Compound transfer policies, ValidatorConfig V2, and audit-driven bug fixes |
+| **TIPs** | [TIP-1015: Compound Transfer Policies](/protocol/tips/tip-1015), [TIP-1004: Permit for TIP-20](/protocol/tips/tip-1004), [TIP-1017: Validator Config V2](/protocol/tips/tip-1017), [TIP-1036: T2 Hardfork Bug Fixes](/protocol/tips/tip-1036) |
+| **Release** | v1.5.0 |
+| **Testnet** | Moderato: Mar 26, 2026 16:00 CET (unix: 1774537200) |
+| **Mainnet** | Mar 31, 2026 16:00 CEST (unix: 1774965600) |
+| **Priority** | <Badge variant="red">Required</Badge> |
+
+---
+
 ## T1C
 
 | | |

src/pages/guide/node/operate-validator.mdx

@@ -1,51 +1,20 @@
 ---
 title: Operate your validator node
-description: Day-to-day operations for Tempo validators. Node lifecycle, upgrades, key rotation, monitoring, and troubleshooting.
+description: Day-to-day operations for Tempo validators. Node lifecycle, monitoring, metrics, log management, and Grafana dashboards.
 ---
 
 # Operate your validator
 
 This guide covers day-to-day operations for running a Tempo validator in production.
 
-## Validator states
+Validator management differs depending on which ValidatorConfig version is active:
 
-Your validator moves through different states during operation. The transitions will happen only once on your validator's creation. Every state transition will happen on epoch boundaries in the happy case.
+- **[ValidatorConfig V2](/guide/node/validator-config-v2)** (post-T2) — self-service key rotation, IP updates, and ownership transfers
+- **[ValidatorConfig V1](/guide/node/validator-config-v1)** (pre-T2, legacy) — all management operations require coordinating with the Tempo team
 
-```mermaid
-flowchart TD
-    A[Inactive] -->|epoch ends| B["Syncer<br/>The validator starts syncing"]
-    B -->|+1 epoch| C["Syncer and Player"]
-    C -->|"+1 epoch, receives share"| D["Syncer<br/>Player<br/>Dealer"]
-    D -->|"once fully synced"| E["Voter ↔ Proposer"]
+For validator states and lifecycle transitions, see the respective V1 and V2 pages.
 
-    click A "#not-a-participant-e"
-    click B "#syncer-epoch-e1"
-    click C "#player-epoch-e2"
-    click D "#dealer-epoch-e3"
-    click E "#dealer-epoch-e3"
-```
-
-Currently, on mainnet and testnet, the epoch length is around 3 hours, which means that your validator will transition through these states approximately every 3 hours. If the epoch length ever changes, the transition times will also change.
-
-#### Not a participant (E)
-
-Epoch E marks the addition of your validator to the on-chain validator configuration smart contract. Your validator isn't considered a peer by validators yet. This is because the validator hasn't been refreshed in the current epoch yet. It is normal that no height metrics progress during this period, your node has to be considered
-a syncer to receive blocks.
-
-#### Syncer (epoch E+1)
-
-Your validator is now considered a peer by validators. It's syncing with the network and will be considered a player in the next epoch.
-
-#### Player (epoch E+2)
-
-Your validator is receiving consensus signing shares from dealers during the ceremony.
-
-#### Dealer (epoch E+3)
-
-Your validator is distributing consensus signing shares to other validators during the ceremony. Once your node is fully synced up, it will also
-be able to propose blocks and vote for other validators' proposed blocks.
-
-#### Checking your validator's state
+## Checking your validator's state
 
 Monitor these metrics to track your validator's state:
 
@@ -140,47 +109,14 @@ The node will finish processing the current block before shutting down. Avoid us
 **You cannot reset a validator's data and continue with the same identity.** Doing so risks inconsistent voting, which can cause irrecoverable network safety failures.
 :::
 
-If you need to reset your validator's data, you must rotate to a new validator identity. This requires coordinating with the Tempo team to deactivate your old identity and register a new one.
+If you need to reset your validator's data, you must rotate to a new validator identity. See key rotation under [ValidatorConfig V2](/guide/node/validator-config-v2#rotate-validator-identity) or [ValidatorConfig V1](/guide/node/validator-config-v1#signing-key-rotation).
 
 ## Key Management
 
-### Signing Key Rotation
-
-To rotate your validator's signing key:
-
-1. Generate a new keypair:
-
-```bash
-tempo consensus generate-private-key --output <new-key-path>
-tempo consensus calculate-public-key --private-key <new-key-path>
-```
-
-2. Contact the Tempo team to update your validator's public key on-chain
-
-3. Once confirmed, update your node configuration to use the new key and restart. Once the node is running, your validator will go through the [validator lifecycle](/guide/node/operate-validator#validator-states).
-
-:::warning
-The old validator identity must be deactivated before the new one is activated
-:::
-
-### Signing Share Recovery
+For signing key rotation, IP address updates, signing share recovery, and ownership transfers, see:
 
-:::danger
-**You cannot reset a validator's data and continue with the same identity.** Doing so risks inconsistent voting, which can cause irrecoverable network safety failures. 
-:::
-
-If you lose your signing share (stored on the database in `<datadir>/consensus/`), you will need to rotate to a new validator identity. This requires coordinating with the Tempo team to deactivate your old identity and register a new one.
-We're planning to release a high-availability feature that allows storing consensus data in an external database, which will enable signing share recovery without the need for key rotation.
-
-### Deleting Signing Shares
-
-:::warning[Breaking Change in v1.1.0]
-`--delete-signing-share` now requires the `--force` flag to prevent accidental deletion of validator signing keys. **Update any automation scripts that manage validator key lifecycle.**
-:::
-
-```bash
-tempo consensus --delete-signing-share --force
-```
+- **[ValidatorConfig V2](/guide/node/validator-config-v2)** (post-T2) — self-service operations
+- **[ValidatorConfig V1](/guide/node/validator-config-v1#key-management)** (pre-T2) — coordinated through the Tempo team
 
 ## Log Management
 

src/pages/guide/node/validator-config-v1.mdx

@@ -0,0 +1,75 @@
+---
+title: ValidatorConfig V1 (Legacy)
+description: Legacy validator management via ValidatorConfig V1. Key rotation, IP updates, and signing share recovery pre-T2.
+---
+
+# ValidatorConfig V1 (Legacy)
+
+:::warning
+This page documents ValidatorConfig V1 behavior, which applies **before the T2 hardfork**. Once T2 is active and migration from V1 to V2 is complete, use [ValidatorConfig V2](/guide/node/validator-config-v2) instead. You can [check if V2 is initialized](/guide/node/validator-config-v2#check-if-v2-is-active) to confirm the migration is complete.
+:::
+
+ValidatorConfig V1 is the original precompile for managing consensus participants. All management operations are permissioned and require coordinating with the Tempo team.
+
+## Validator states
+
+Under V1, your validator goes through the following states after being added on-chain. Each transition happens on epoch boundaries.
+
+```mermaid
+flowchart TD
+    A[Inactive] -->|epoch ends| B["Syncer<br/>The validator starts syncing"]
+    B -->|+1 epoch| C["Syncer and Player"]
+    C -->|"+1 epoch, receives share"| D["Syncer<br/>Player<br/>Dealer"]
+    D -->|"once fully synced"| E["Voter ↔ Proposer"]
+
+    click A "#not-a-participant-e"
+    click B "#syncer-epoch-e1"
+    click C "#player-epoch-e2"
+    click D "#dealer-epoch-e3"
+    click E "#dealer-epoch-e3"
+```
+
+Currently, on mainnet and testnet, the epoch length is around 3 hours, which means that your validator will transition through these states approximately every 3 hours.
+
+#### Not a participant (E)
+
+Epoch E marks the addition of your validator to the on-chain validator configuration smart contract. Your validator isn't considered a peer by validators yet. This is because the validator hasn't been refreshed in the current epoch yet. It is normal that no height metrics progress during this period, your node has to be considered a syncer to receive blocks.
+
+#### Syncer (epoch E+1)
+
+Your validator is now considered a peer by validators. It's syncing with the network and will be considered a player in the next epoch.
+
+#### Player (epoch E+2)
+
+Your validator is receiving consensus signing shares from dealers during the ceremony.
+
+#### Dealer (epoch E+3)
+
+Your validator is distributing consensus signing shares to other validators during the ceremony. Once your node is fully synced up, it will also be able to propose blocks and vote for other validators' proposed blocks.
+
+## Key Management
+
+### Signing Key Rotation
+
+1. Generate a new keypair:
+
+```bash
+tempo consensus generate-private-key --output <new-key-path>
+tempo consensus calculate-public-key --private-key <new-key-path>
+```
+
+2. Contact the Tempo team to update your validator's public key on-chain
+
+3. Once confirmed, update your node configuration to use the new key and restart. Once the node is running, your validator will go through the [validator states](#validator-states) again.
+
+:::warning
+The old validator identity must be deactivated before the new one is activated.
+:::
+
+### Signing Share Recovery
+
+If you lose your signing share, coordinate with the Tempo team to deactivate your old identity and register a new one.
+
+### Update IP Addresses
+
+Contact the Tempo team to update your validator's ingress and egress addresses on-chain.