feat: (eng-607), rafiki cards blog #185
Conversation
✅ Deploy Preview for developers-preview ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
koekiebox
changed the title
sabineschaller
left a comment
sabineschaller
left a comment
There was a problem hiding this comment.
I know there are quite a few comments, but generally, I love this! It is a fantastic overview!
|
|
||
| At a high level, an ILP card transaction involves: | ||
|
|
||
| 1. Card (ICC) - EMV-compliant card with an ILP-linked wallet address |
There was a problem hiding this comment.
This would technically be an "Open Payments enabled" wallet address, since that is what makes it discoverable and able to set up payments against.
|
|
||
| ## Starting Point: Should you build a Kernel? | ||
|
|
||
| One of the earliest and most important decisions came out of conversations with our first POS (Point of Sale) manufacturing partner, who provides both the EMV kernel and a significant portion of the overall payment software stack running on the device. |
There was a problem hiding this comment.
Maybe we can quickly define what a kernel is/does
|
|
||
| - POS Manufacturer bespoke software (Android / Symbian / iOS / Windows Phone) | ||
| - POS kernel | ||
| - POS WhiteBox secure storage |
There was a problem hiding this comment.
Let quickly explain what WhiteBox is
| - Assembles transaction data | ||
| - References the card's wallet address (Customer ASE) | ||
| - Signs the request with its ILP key (Merchant ASE) | ||
| - Sends it to the Customer and Merchant ASE |
| - Certifications | ||
| - Key management | ||
|
|
||
| The ASE remains firmly in control. Rafiki Does What It Already Does Well. From here on, Rafiki is on familiar ground. |
There was a problem hiding this comment.
| The ASE remains firmly in control. Rafiki Does What It Already Does Well. From here on, Rafiki is on familiar ground. | |
| The ASE remains firmly in control. Rafiki does what it already does well. From here on, Rafiki is on familiar ground. |
|
|
||
| It: | ||
|
|
||
| - Creates incoming and outgoing payments |
There was a problem hiding this comment.
Need to add here that it processes the ILP payment
| - Small, focused services are easier to reason about than monoliths | ||
| - Interledger fits best when it is complementary, not dominant | ||
|
|
||
| ## Conclusion, Where This Leaves Us |
There was a problem hiding this comment.
More of a suggestion, but might be also nice to add what the following steps are for the cards team in a simple list?
PR Checklist
Fixes #eng-607). See: https://linear.app/interledger/issue/ENG-607/technical-blog-on-rafiki-and-cardsbun run formatto ensure code is properly formattedbun run lintpasses without errorsSummary
Please see the preview: https://deploy-preview-185--developers-preview.netlify.app/developers/blog/rafiki-card-integration/