docs: update content on paymentpointers.org
@melissahenderson 已经在做这个了。
开始于 2025年2月6日。
评估
这个 Issue 还没有评估数据。
描述
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).
- 主要语言
- JavaScript
- 星标
- 53
- 派生
- 6
- 平均合并
- 6 天 3 小时
- 30 天内合并 PR
- 1
贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
interledger/paymentpointers.org 的其他 Issue
-
documentation
interledger/paymentpointers.org#50 · 已指派 1 人 ·
查看 interledger/paymentpointers.org 的全部 Issue
相似的 Issue
-
area/install-update comp/cli comp/desktop P3 sweeper:risk-compatibility type/bug
难度 2/5 1-3 小时 新手友好度 86/100
NousResearch/hermes-agent#122386 · 1 条评论 ·
-
难度 2/5 1-3 小时 新手友好度 74/100
-
security
难度 2/5 1-3 小时 新手友好度 72/100
IBM/node-sdk-core#373 ·
-
docs web/
难度 2/5 1-3 小时 新手友好度 68/100
-
难度 2/5 1-3 小时 新手友好度 65/100