interledger / interledger/rfcs
Confusion between transferId and Request ID in BTP error codes?
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 513
- Forks
- 107
- PR merge metrics
- No merged PRs in 30d
Description
There are two 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 make sense to rename error F03 from TransferNotFound to RequestNotFound
Other error codes refer to fulfillment, such as:
The transfer cannot be fulfilled because it has already been rejected or expired.
Even though BTP transfers don't seem to have a condition.
Do the transferId and conditions in these error codes refer to ILP-level transfers?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read the error-code and transfer sections in 0023-bilateral-transfer-protocol.md, especially the references to transferId, Request ID, fulfillment, and F03. Determine which protocol-level concepts those terms describe, then update the specification so the identifiers, conditions, and error name are consistent and unambiguous.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100