Rafał Malinowski
Rafał Malinowski
Seems it is already fixed
Hi! Thanks! As you've probably noticed, this project is not maintained anymore (as it caused no real interest). If you want, you can develop it on your own. Good luck!
Does not looks like a core bug. This commits adds a big tests for this case: https://github.com/stellar/stellar-core/commit/be3e662885e77a3521ceded825ab0200d0a85cb8 So maybe it is horizon bug? Should we reopen?
Just thinking: https://github.com/stellar/horizon/blob/master/src/github.com/stellar/horizon/simplepath/order_book.go#L57 In that case source is equal to destination, so maybe this condition is not right, as it would yield to `true` both for source and for destination,...
Looks like it could be a stellar-core bug after all. Similar issues were found for different path payements that resulted in op_over_source_max even when there was enough of assets on...
@cesarmak your example should get executed if only P and Q signed this transaction.
Yes, that is the proper way.
Do you mean DataEntry values from Stellar-ledger-entries.x (added with ManageData?). These are held by LedgerEntry structure that contains lastModifiedLedgerSeq number, and this looks like the "field revision id" you need....