GNAP dynamic client registration

[jeremiahlee]

Today, the extension contains wallet provider-specific workarounds to dynamically register itself as a GNAP client (ie adding a public encryption key). This approach was chosen as the quickest solution

We need to define the ideal method we would like wallet providers to implement so that the Web Monetization extension can have a secure, stable, and universal way to programmatically interact with wallet providers.

The initial discussion for this is captured here: https://docs.google.com/document/d/1Uj4lXY2PW0tAMdQyqUD2pLoH6q0S-LCfPAGCAoxIivo/edit?tab=t.0

[sidvishnoi]

Related past discussions: interledger/rafiki#3126 (interledger/rafiki#2803, #311).

[sidvishnoi]

This should be discussed at Open Payments level though. Extension will follow the approach defined there. Not up to the extension to define for what wallet are to do that is, as there can be more clients than extension.

[jeremiahlee]

Not up to the extension to define for what wallet are to do that is, as there can be more clients than extension.

I disagree. Web Monetization is the primary use case of Open Payments today. The developers of Web Monetization are the most qualified users of the Open Payments API to define the expected behavior. We are justified in expecting Open Payments to meet our requirements.