rfcs
rfcs copied to clipboard
Specifications for Interledger and related protocols
Explicitly define in the spec what happens if it's truthy or falsey. i.e empty string.
receipts_enabled shared_secret destination_account From @marcoscaceres: Would be nice if the SPSP has an algorithm to hook directly into for validation. And it returned true or false. So... "perform simple payment...
There are [two error codes](https://github.com/interledger/rfcs/blob/main/0023-bilateral-transfer-protocol/0023-bilateral-transfer-protocol.md#error-codes) that refer to `transferId` of packets/requests but in the specification but it seems what is meant is `Request ID`? Also in this context it would...
The [stated motivation of BTP](https://github.com/interledger/rfcs/blob/main/0023-bilateral-transfer-protocol/0023-bilateral-transfer-protocol.md#motivation) is to be a [link-layer protocol](https://github.com/interledger/rfcs/blob/main/0001-interledger-architecture/0001-interledger-architecture.md#protocol-layers) like [ILP-over-HTTP](https://github.com/interledger/rfcs/blob/main/0035-ilp-over-http/0035-ilp-over-http.md) but using WebSockets instead of HTTP POST. I understand BTP has to be more complex than ILP-over-HTTP...
Fixes #588
Documents: Include Deprecation Notes to Prevent Issues and Know User to Prevent Future Problems
This fixes the ILDCP link on the "ILP Addresses" RFC.