Closed SmaugPool closed 1 year ago
Hi, this is something that we also encountered using cardano node version 8.1.2. The underlying issue here is that a transaction is being built with an already spent utxo. For example, if you have the rescan delay too low, the bot will probably build a match using an order that was consumed in the previous iteration.
The weird behavior is the extraneous error instead of the expected BadInputsUTxO
. We opened an issue here about that, but we didn't hear back.
Thank you @Micrograx. My scan delay was indeed set to a low value.
this is something that we also encountered using cardano node version 8.1.2
Does this mean you don't encounter this issue anymore with later versions?
Does this mean you don't encounter this issue anymore with later versions?
I don't think we tried it with a newer version. But transactions that give the weird error on 8.1.2 throw BadInputsUTxO
on earlier node versions according to our testing.
Describe the bug My SOR bot is regularly submitting order matching transactions, but it also logs a lot of
DecoderFailure
DeserialiseFailure 326 "expected word"
errors (286 in 16 hours).I'm not sure yet if those errors come from badly constructed transactions or from the bot.
To Reproduce Steps to reproduce the behavior:
*
match pattern)DecoderFailure
errorsExpected behavior The bot should work without unexpected errors.
Screenshots Log sample at UTC+2 (I can provide more if needed):
Station (please complete the following information):
Additional context SOR version: