FNet Docs
Build your own FNet algod
FNet runs on a rolling nightly algod release. Each lifetime instance of FNet will use a fixed version.
After each network reset, the binary may be upgraded to a later release, depending on whether it provides added value in testing the future protocol.
If you intend to build your own algod for a custom architecture, you need to keep the binary updated to avoid unexpected behavior. Network resets and binary updates will be announced on discord.
1. Get the latest FNet commit
To build your own FNet algod, the first thing you will need is the commit hash corresponding to our current nightly release.
https://fnet.algorand.green/static/version.txt
The commit=93e1f826 line will refer to the git commit you need to build from the go-algorand repo.
2. Build algod
i. Clone the go-algorand repo locally and check out commit hash you retrieved from the previous step (currently 93e1f826.)
ii. Follow the "Building from source" instructions that correspond to your environment.
Important: Stay up to date
Remain up to date with network resets and binary updates to avoid unexpected behavior.
An easy option to do so is to join the FNet channel on our discord , where these will be announced.
Alternatively, you can scrape/watch the version.txt file mention in section 1 and monitor it for changes.
3. Resetting? Wipe data directory
In case you are building a newer version after an FNet network reset, you need to delete the previous FNet network data directory.
This is located under $ALGORAND_DATA/fnet-v1 - e.g. /var/lib/algorand/fnet-v1
4. Configure your node
Visit the next section for information on how to configure your node