TigerBeetle is a distributed financial accounting database designed for mission critical safety and performance. Since Rafiki implements the Interledger Protocol, which splits payments into packets, we need a high performing and safe database to store all that payment data. For detailed information on TigerBeetle, including its consensus mechanism and its limitations, visit the official TigerBeetle documentation and blog.
Rafiki uses a combination of liquidity and settlement accounts to perform double-entry accounting. These accounts correspond to TigerBeetle credit and debit accounts, respectively. For more information on Rafiki’s accounting, refer to Accounts and Transfers. Note that TigerBeetle only holds balance data and not any other additional metadata included in ILP packets.
Changing TigerBeetle Version within Rafiki
Updating the node client
# latest pnpm --filter backend up tigerbeetle-node --latest # specific version pnpm --filter backend up firstname.lastname@example.org
Production Environment - Helm charts
To use the desired version of TigerBeetle within the production environment, change the tag in the helm
To use the desired version of TigerBeetle within the local environment, change the tag in the tigerbeetle
To use the desired version of TigerBeetle within the Rafiki tests, change the tag in the tigerbeetle test setup.