Weekly Sync - 30 July 2024

[github-actions[bot]]

Please add agenda items below and give your weekly update in a comment. Thank you!

Agenda

• @sabineschaller Rafiki work week overview

Discussion

Rafiki Work Week

See the Preliminary Proposal here.

Details

• When: 26- 30 August (Travel dates: 25, 31 August)
• Where: Cluj-Napoca, Romania
• Work: BreakpointIT Office (Strada Andrei Muresanu 19)
• Wind down: Courtyard by Marriott (Avram Iancu Street 23-25)

Schedule

• Work Hours: 9 AM to 5 PM
• Monday: Welcome dinner
• Wednesday: ½ day with an optional team activity at the hotel
• Thursday: Smaller groups going out to dinner
• Friday: Presentations

Work Tracks

1. Multi-Tenant Rafiki
   • Enable multiple banks to use a central Rafiki instance, such as one hosted at a central bank.
   • Ensure Bank A cannot query Bank B’s resources via the Admin APIs.
   • Implement user roles for the Admin API/UI.
   • Establish different base paths for Open Payments and Auth Servers per bank.
   • Create different consent screens for grant authorization based on the user’s bank.
   • Set different rates per bank.
   • etc.
   • Notes: This track will likely be more of a design workshop with JoPACC participants, focusing on the architecture and implementation details for multi-tenant support.
2. Alternatives for Rapyd in Test Wallet
   • Replace Rapyd, which has sandbox rate limits hindering live coding and hackathons, with an alternative.
   • Our current solution involves spinning up multiple instances to bypass rate limits, which is unsustainable.
   • Identify an alternative (e.g., Gatehub/Chimoney sandbox).
   • Test the alternative solution to ensure it can handle multiple users without rate limitations.
   • We had a discussion about whether the solution should be a fully sandboxed ASE or just accessible for playground purposes.
   • Mocking suggestions were made by @matdehaast and @adrianhopebailie
   • @AlexLakatos has asked for an emphasis on integrating the test wallet with something that can easily transition to production.
3. Rafiki Documentation
   • Overhaul the Rafiki documentation.
   • Improve the structure and content of the current docs, which are mainly brain dumps.
   • We need a collaborative effort guided by the tech writers to complete the documentation.
4. PCH Related Case
5. Multi-Hop Payments (If Needed)
   • Implement support for multi-hop payments in Rafiki, reflecting the Interledger network’s design.
   • Figure out routing or check if old code can be reused.
   • Implement necessary routing for multi-hop payments.

Action items

• Form teams
• Define goals
• Define stories and issues
• Follow up discussions with @adrianhopebailie about mocking the Rapyd APIs.

[sabineschaller]

Looked into #2795 but don't think it's a Rafiki bug. @rico191013 is investigating on the test wallet side.

[BlairCurrey]

• added new rate probe metric
• working on integration test blog post
• starting to investigate best way to generate histogram metric for graphql resolvers execution time. bespoke histogram metric? derive from spans?

[njlie]

• Merged in feat(auth): inspect access during token introspection #2788 for Issue Check request access during token introspection #835 .
• GNAP Blog Post
• Working on load test & learning k6 tooling

[JoblersTune]

Submitted a PR for adding additional telemetry metrics
Busy creating better Rafiki Admin docs and adding them to rafiki.dev as well as providing more information about how Kratos is used.