docs: update content on paymentpointers.org
@melissahenderson ci sta già lavorando.
Dal 6/2/2025.
Valutazione
Questa issue non è ancora stata valutata.
Descrizione
Revise the paymentpointers.org documentation so that it accurately reflects the relation between payment pointers, wallet addresses, ILP/SPSP, and Open Payments.
Background:
Payment pointers were originally introduced as an Interledger RFC: https://github.com/interledger/rfcs/tree/main/0026-payment-pointers
The RFC became its own website: http://paymentpointers.org/. The sidenav in the Interledger Developers site links to paymentpointers.org.
Other than a tool to convert a payment pointer to a URL, the content remained largely the same as what was in the original RFC until 2020. Then, Adrian made a number of updates to work in Open Payments. Max pointed out that the site doesn’t mention anything about Interledger/the protocol and all references lead to Open Payments.
A URL can be both a payment pointer and a wallet address. Payment pointers are Interledger-only. Currently, wallet addresses (Open Payments) are also payment pointers because Open Payments only works with ILP. If/when Open Payments works with more than ILP, you could have a wallet address that doesn’t support Interledger (and as such, is not a payment pointer).
There’s also the issue of terminology. For example, Chimoney and GateHub call the URL a payment pointer. Fynbos calls it a wallet address.
Payment pointers are technically built on SPSP and wallet addresses on Open Payments, but the two are competing application layer protocols in the ILP stack. If you query a URL that’s both, you call with SPSP to get a payment pointer response and with application+json to get a wallet address response.
Other info: The site states, “A Payment Pointer resolves to a URL (with the https scheme) that can be used to discover the Open Payments endpoints for interacting with the account. Using the Open Payments protocol the counter-party can initiate a payment to or from the owner of the Payment Pointer.” This could be construed to mean that payment pointers are definitively tied to Open Payments, except someone could choose to use payment pointers in some other way (e.g., Interledger/SPSP).
- Lingua principale
- JavaScript
- Stelle
- 53
- Fork
- 6
- Merge medio
- 6g 3h
- PR unite (30g)
- 1
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di interledger/paymentpointers.org
-
documentation
interledger/paymentpointers.org#50 · 1 assegnatario ·
Tutte le issue di interledger/paymentpointers.org
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 65/100
-
Theme loads third-party resources on every page (jsdelivr web font, cdnjs Font Awesome) – GDPR Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
docToolchain/docToolchain#1705 ·
-
Timezone select lists one option per character; duplicate "Failed" reason; shared tracker popover id Apertabug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
nightscout/nocturne#1414 ·
-
bug v2
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
modelcontextprotocol/inspector#2458 · 1 commento ·
-
Mend: dependency security vulnerability status: needs triage 🕵️♀️
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
carbon-design-system/ibm-products#9907 ·