![]() ![]() There are three networks supported by Algorand: How do I use Fast Catch-Up?įirst, you have to retrieve the latest check-up point for the network you are running. This process can sync an entire node in minutes. What is Fast Catch-Up?įast Catch-Up is a new feature that rapidly updates a node using catchpoint snapshots. For future syncs, you can catch up to the network more quickly by using the Fast Catch-Up functionality. This means the node will process all the blocks in the blockchain to verify them and ensure the validity of the chain, which may take some time. When a node first starts, it must sync with the network. These are only a few of the endpoints supported by the Algorand algod API, and I suggest you check out the rest of them here. Optionally, this endpoint accepts a timeout parameter that tells the node how many seconds to wait until it shuts down.Ĭurl -X GET "$ALGORAND_DATA"/)/v2/status -H “X-Algo-API-Token: $(cat "$ALGORAND_DATA"/algod.token)" Get the current supply reported by the ledger.Ĭurl -X POST "$ALGORAND_DATA"/)/v2/shutdown -H “X-Algo-API-Token: $(cat "$ALGORAND_DATA"/algod.token)" Given an account public key, this API call will return the account’s status, balance, and spendable amounts.Ĭurl -X GET $ALGORAND_DATA/)/v2/ledger/supply -H “X-Algo-API-Token: $(cat "$ALGORAND_DATA"/algod.token)" The documentation goes into great detail, but here are a few that I find useful:Ĭurl -X GET $ALGORAND_DATA/)/v2/accounts// -H “X-Algo-API-Token: $(cat "$ALGORAND_DATA"/algod.token)" ![]() This can be solved by running the following command:Īnother great way to ensure your node is running correctly is the Algorand algod REST API. This means that your node is not running. If, when checking the status of your node with goal node status, you get an error that says: Run () ĭebugging and Interacting with your Node Common Errors Check the status of your node by running goal node statusĪ script that automates this process is available on GitHub:.Start your node by running goal node start.update.sh -i -c stable -p ~/node -d $ALGORAND_DATA -n When executing for the first time, this may take a little while. Execute the update.sh script to install your node.Ensure that the updater script is executable: chmod 544 update.sh.This script is used to pull down the latest package update from AWS S3 and install it. Install the updater script from Algorand’s GitHub page.Here is the syntax for creating this environment variable: export ALGORAND_DATA=$(pwd)/data Set the environment variable equal to $(pwd)/data. Create an environment variable called ALGORAND_DATA.If you are using Zsh, you can run take node to both create and change to the node directory. Create a new directory called node and change to that directory.cd $HOME, cd ~, or even just cd should do the trick. Using the quick-algo shellscript: Discusses how quick-algo can be used to begin running a fully-customizable Algorand Node in under one minute.Catching up to the Network: Introduces the concept of “Fast Catch-ups” and discusses several ways to keep your node up to date.Debugging and Interacting with your Node: Discusses common errors you may run into and also introduces some useful Algod API endpoints that you can use for debugging and interacting with the Algorand node.Additionally, this section introduces the shell script I wrote that automates the process of running an Algorand Node. Install a Node: Covers the basic steps needed to install an Algorand Node.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |