Closed ojura closed 2 years ago
It looks like when parsing the cons list of hex numbers in the aggregated offer, multiple hex numbers somehow get improperly concatenated: SyntaxError: invalid hex at 1: 0xa402643c844ad9048d4a6f9c724077254fa5e1355b7afb06088de4f92ad489a6e9045811e8797a49157ca20510bac62f3e985c5f94fbbfd3d8fbed99886750820000000000008a840xf94821c0703b8484dcfba68b1a678002efbe97dc058b8ffb9f26723d34c449b5e9045811e8797a49157ca20510bac62f3e985c5f94fbbfd3d8fbed99886750820000000000008aac0x305b....
What happened?
I have an aggregated offer with net zero arbitrage amounts. However, converting it to a valid spend bundle gives an "invalid hex" error.
Happens in GUI as well, after pressing the button to accept the other party's offer (don't have a screenshot, but the error is the same as in the Python log below).
Original offer:
Aggregated with counteroffer:
Version
1.5.1, 1.6 pre-release
What platform are you using?
Linux
What ui mode are you using?
GUI
Relevant log output