|
About the Protocol Design category
|
2
|
February 6, 2019
|
|
Wallets and Hosted Accounts
|
3
|
July 19, 2019
|
|
ILP Addressing - Private Money Infrastructure
|
4
|
July 16, 2019
|
|
Protocol on the Wire
|
4
|
July 10, 2019
|
|
Authorized Payments using SPSP and STREAM
|
11
|
July 9, 2019
|
|
Proposals for Secure Interledger Routing
|
5
|
July 8, 2019
|
|
SPSP Invoices RFC Questions
|
2
|
May 29, 2019
|
|
Deprecate the Echo Protocol and Replace with One-way Ping?
|
10
|
May 29, 2019
|
|
ILP-over-HTTP Authentication
|
3
|
May 22, 2019
|
|
Pull Payments
|
46
|
May 17, 2019
|
|
Push Payments and Invoices
|
25
|
May 10, 2019
|
|
Rsocket
|
1
|
May 7, 2019
|
|
Auto-Peering, Easy Peering, and Open Signup
|
8
|
May 1, 2019
|
|
Auto-Peering
|
7
|
April 29, 2019
|
|
Connector Auth Model
|
4
|
April 25, 2019
|
|
Document the ping protocol
|
13
|
April 17, 2019
|
|
DDoS on the Interledger
|
6
|
March 6, 2019
|
|
Payment Privacy
|
3
|
March 1, 2019
|
|
How does an SPSP client verify they are communicating with the intended SPSP server?
|
3
|
February 28, 2019
|
|
Formalize the use of the `peer.` address space (define some addressing best practice)
|
15
|
February 28, 2019
|
|
HTTP(s) questions
|
4
|
February 22, 2019
|
|
Ping Protocol: Discussion, Necessity, and Design
|
2
|
February 12, 2019
|
|
W3C Web Payments API integration
|
3
|
February 7, 2019
|
