Network upgradesValidators · Developers1 min read
Tachyon v3.1.14 cleared for mainnet
Accounts index moves fully into memory, three flags are deprecated, malformed RPC filters now fail.
X1 Labs · X1 Labs ·
Tachyon v3.1.14 was the X1 validator release that carried the network through the summer, before v4.0.3. It brought X1 onto Agave's 3.1 line, and the change operators felt most was memory.
What changed
The upstream Agave 3.1 changelog lists the changes that matter for X1 operators:
- The accounts index now lives entirely in memory by default. That is faster, but a machine short on RAM struggles. It is why X1's recommended validator spec is now 192 GB.
- Three flags were deprecated: --disable-accounts-disk-index, --monitor on agave-validator exit (run the separate monitor command afterwards instead) and --dev-halt-at-slot.
- getProgramAccounts now returns an error for malformed filters. Before, it quietly ignored them and ran an unfiltered query, which could return the wrong data or overload a node.
Why it was good for X1
Keeping the client close to upstream is how X1 gets Solana's performance and security fixes without writing them itself. The getProgramAccounts change protects RPC providers and apps: a typo in a filter now fails loudly instead of returning everything.
What it meant for operators
- Check RAM before upgrading. Machines that ran fine on v2.2 could hit memory limits.
- Remove the deprecated flags from start scripts. They are gone entirely in v4.0.
- v3.1.14 is no longer current. Validators should be on v4.0.3, which the Foundation delegation program now requires.
Sources
- Agave 3.1 changelog on the Tachyon release branch: https://github.com/x1-labs/tachyon/blob/release/v3.1.14/CHANGELOG.md
- X1 docs, hardware requirements: https://docs.x1.xyz/validating/performance/hardware-requirements