Open diminator opened 8 years ago
Ok, it seems the transfer immediately expires:
{"id":"https://blue.ilpdemo.org/ledger/transfers/8234ff53-a827-4cbf-8ff4-989584953c0c","ledger":"https://blue.ilpdemo.org/ledger","debits":[{"account":"https://blue.ilpdemo.org/ledger/accounts/connie","amount":"1.2345","authorized":true,"memo":{"source_transfer_ledger":"https://red.ilpdemo.org/ledger","source_transfer_id":"175d0984-23f9-4dec-951d-5fccdc137063"}}],"credits":[{"account":"https://blue.ilpdemo.org/ledger/accounts/bob","amount":"1.2345","memo":{"myKey":"myValue"}}],"state":"rejected","rejection_reason":"expired","execution_condition":"cc:0:3:47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU:0","expires_at":"2016-07-07T12:27:49.000Z","timeline":{"proposed_at":"2016-07-07T12:27:49.000Z","prepared_at":"2016-07-07T12:27:49.000Z","rejected_at":"2016-07-07T12:27:49.000Z"}}
increasing the expiresAt, resolves this
Note that the reason manual transfers appear to come from the connector is that there is no sourceAddress
in ILP. Figuring out the sending account details happens in SPSP at the moment. If you look at the destination transfer's credit memo in a payment sent by the wallet or wallet client you'll see the following information, which is added and used by the wallet:
@diminator Did you figure out the issue with expiries? Is that something that should change on ilp-core
?
If you look at the destination transfer's credit memo in a payment sent by the wallet or wallet client you'll see the following information, which is added and used by the wallet:
Ah, ok. I was only using the node examples from the ilp-core
library and went inspecting on the blue and red wallet GUI.
I assume that there are some specific ilpHeader
fields that facilitate the interpretation of an ILP package. Is this already fleshed out/documented somewhere?
Did you figure out the issue with expiries? Is that something that should change on ilp-core?
Well, I was on a slow connection and the expiry of 4 seconds was too tight. And then I got a log info that the transfer was refused, without telling me why. That was a bit cryptic. Enlarging the expiry to e.g. 10 seconds and/or adding more details in the error would be useful indeed
I assume that there are some specific ilpHeader fields that facilitate the interpretation of an ILP package. Is this already fleshed out/documented somewhere?
No, because they're used by the wallet but they're not part of an "official" protocol on top of ILP (yet)
adding more details in the error would be useful indeed
We have an outstanding TODO to improve the error handling
Most of the times it just rejects the transfers:
One time it came through, but then it listed connie as the sender (see bob @ https://blue.ilpdemo.org/)