Comments (6)
This is a bit of a closer call than #74, but I would still say:
Receivers SHOULD reject the incoming transfer with the error "condition mismatch". Reason here is more around - there is probably something fishy going on if the ILP packet doesn't match the transfer. Again, "SHOULD" in case they know more than we do.
from rfcs.
If they do fulfill one of these which would it be?
Also, do we recommend that if they can fulfill both that they SHOULD?
Is there a protocol where a payment could be split over multiple routes?
from rfcs.
If the receiver tries to fulfill a condition that matches the ILP packet but not any local transfers, then their ledger will just reject the fulfillment.
from rfcs.
If the receiver tries to fulfill a condition that matches the ILP packet but not any local transfers, then their ledger will just reject the fulfillment.
Good point, so it's either both or just the one from the transfer.
from rfcs.
@bensharaf is right. That also means there's no point fulfilling both because the one from the packet would be rejected by the ledger. So it should be the receiver either fulfills neither or only the one in the transfer.
from rfcs.
Conclusion is to remove condition from packet. Receiver will only ever get a single condition
from rfcs.
Related Issues (20)
- Formalize the use of the `peer.` address space (define some addressing best practice) HOT 15
- RFC-0033: Diagrams should be more connected to explanations HOT 1
- Delegated / pull payments HOT 29
- Cleanup naming of RFC 0000
- Rename RFC-0014 to "0014-paid-http-apis"
- RFC0035: Request header for Host not defined
- Change description of F04 error? HOT 3
- docs(0028): add CORS info HOT 1
- 0028: dynamic meta tags security issues HOT 7
- 0027 refers to spec 0025 which is deprecated.
- STREAM RFC: codify the conditions for a ConnectionAssetDetails frame being returned from a receiver. HOT 3
- Tracking: RFC Breaking Changes for STREAM V2 HOT 3
- Create PR for the README to propose new Spec process HOT 2
- Expiry on STREAM credentials HOT 9
- Submit Ping Protocol as an RFC Proposal HOT 1
- Add STREAM Receipts HOT 5
- Remove legacy ASN.1 definitions HOT 8
- Add ConnectionAssetDetailsRequestFrame HOT 1
- Enforce Boolean on SPSP receipts_enabled HOT 1
- Add Validation mechanism for SPSP HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rfcs.