Skip to content
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.

Clarify BTP version #2

Open
michielbdejong opened this issue Jan 11, 2018 · 1 comment
Open

Clarify BTP version #2

michielbdejong opened this issue Jan 11, 2018 · 1 comment

Comments

@michielbdejong
Copy link
Contributor

In the readme, we should explain that this plugin implements BTP/2.0 (if that's what we want to call it), and is incompatible with BTP/1.0.

@michielbdejong
Copy link
Contributor Author

michielbdejong commented Jan 11, 2018

Also, we need to explicitly document (since it's so confusing) that the new Transfer/Response/Error sequence decreases (settles) the sender's unsecuredAmount. This is the opposite of how in BTP/1.0 the Prepare/Fulfill/Reject sequence used to increase (cause) the sender's unsecuredAmount,
see interledger/rfcs#360 (comment). It would be easy to oversee this difference, and think that Transfer/Response/Error is just the unconditional version of Prepare/Fulfill/Reject. Or maybe we should just say "forget everything you think you know about BTP". :)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant