Welcome to the first installment of Rafiki updates for 2025! We look forward to a productive year with Rafiki, and will continue sharing monthly updates here.
Multi-Tenancy
Since the beta release of Rafiki in December, the team has been hard at work on implementing a new feature: multi-tenancy.
This feature will allow a single deployment of Rafiki to support multiple Account Servicing Entities (ASEs). This is very useful in environments like clearinghouses, where different members of these organizations can onboard onto an existing Rafiki instance without having to manage their own infrastructure. This helps different ASEs quickly join the Interledger network and seamlessly participate with other ASEs running Rafiki.
In our implementation, each deployment will have an "operator", which will oversee all of the different ASEs (tenants), and depending on the configuration, the operator will be able to help onboard new tenants, and in cases where it's necessary, do different actions on their behalf. At the same time, each tenant retains full control over their own setup: being able to configure peering relationships, managing assets, and creating wallet addresses, just like in a standalone Rafiki instance.
Finishing this feature is our main priority for the short term, and even though most of the changes are done in the backend, soon we'll be able to share a demo of what the Admin UI will look like for different tenants using this feature.
Content Updates
At the beginning of the month, our engineer Nathan Lie wrote a blog post about how we use ILP in Rafiki. The Lifecycle of an Interledger Packet describes the in-depth process of how Rafiki orchestrates payments with ILP, as well as how ILP works in tandem with Open Payments to move funds between accounts.
In case you missed it, another one of our engineers, Jason Bruwer, wrote a post about how Rafiki is integrated with the TigerBeetle accounting database, a crucial element of the software.
As always, if you have any questions/comments/feedback, please join our Rafiki community calls bi-weekly on Tuesdays at 1530 UTC.
Top comments (0)