Open seniorjoinu opened 6 months ago
Read the rationale first, then read the specification itself. Reference implementation is available here.
I realized, that for some people it may be hard to see, how the specification (which is about a postMessage-based protocol) could lead us to the future, which I described in the Perfect Scenario
section of the rationale (which is about business models and non-technical stuff).
This is why we already implemented ICRC-35 in MSQ. Every project out there now can integrate with MSQ to receive payments - there is no need in implementing this functionality in-house anymore. The same goes for the authorization - you don't have to handle the authorization of users by yourself, you can just integrate with MSQ using the ICRC-35 protocol (or you could integrate with the Internet Identity, which uses something we might call "non-standard ICRC-35").
This specification is an idea: "what if instead of integrating through canister calls, we would integrate through postMessage calls?". And it seems like this way of integrating allows a much more flexible and secure use-cases to appear.
This is a tracking issue for this pull request. Use it as a platfrom for discussing the ICRC-35 and related topics.