Enable flows that don't involve a central server.
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 607
- Forks
- 166
- Avg merge
- 2d 7h
- Merged PRs (30d)
- 7
Description
The current specification has a couple places where an external URL is required (incomingPayment and paymentPointer). While in theory a URL could be something other than HTTP (e.g., file://, bitcoin://, etc.), the spec's wording seems to strongly imply that it will always be something that can be fetched, and the paymentPointer is defined as an Open Payments API entry which I believe requires a server component.
I'm not exactly sure how to resolve this, but it feels like leaning into digital currencies peer to peer nature and decentralization would be beneficial.
Use case: Website hosted on S3/IPFS with no server infrastructure wants to provide an enhanced experience to users who make a donation with a digital currency, and it may utilize the browser's built-in wallet for payment verification.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the specification's treatment of incomingPayment and paymentPointer, especially its assumptions about external URLs, fetchability, and an Open Payments API server. Define what a serverless flow would require for an S3/IPFS site and browser wallet, then update the specification with an agreed model and examples.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100