Paul Zupan

Just switched to that validator and svt.one is showing 2.3.6... validator.sh just calls `exec agave-validator`...

`sol 2044689 1049 10.0 249392360 52997000 ? Ssl 20:18 1997:48 agave-validator --identity /home/sol/keys/mainnet-identity.json --vote-account /home/sol/keys/mainnet-vote-account-keypair.json --authorized-voter /home/sol/keys/mainnet-validator-keypair.json --known-validator 7Np41oeYqPefeNQEHSv1UDhYrehxin3NStELsSKCT4K2 --known-validator GdnSyH3YtwcxFvQrVVJMm1JhTS4QVX7MFsX56uJLUfiZ --known-validator DE1bawNcRJB9rVm3buyMVfr8mBEoyyu73NBovf2oXJsJ --known-validator CakcnaRDHka2gXyfbEd2d3xsvkJkqsLw2akB3zsN1D2S --only-known-rpc --log /home/sol/logs/mainnet-validator.log --ledger /mnt/ledger...

`/home/sol/.local/share/solana/install/releases/v2.2.20-jito/bin/agave-validator` I figured out I was building in the 2.2.20 directory every time so when I run --version there I get 2.3.6...

There really isn't another build in the machine to confuse. The only buiild right now is 2.3.6... What method is your application using to determine version? Perhaps it will provide...

`agave-validator 2.3.6 (src:4b702606; feat:3640012085, client:JitoLabs)` I've fixed the script so it will build in a new directory each time now and switch the link. Not sure what to say about...