Karl Ranna

Is there a reason why this hasn't been pulled into master yet?

@juliomenendez I'm going to pitch in and contribute by writing a documentation paragraph or two this weekend.

My concern here is that the user has to be 100% aware that there will be fees associated with this. We'd have to make that super clear.

Just curious - do you also have indra cloned/previously running locally?

> Yeap it is vector. Most likely this case can be reproduced when updating old version of xud (without vector) to a new one. Think it's caused by the mismatch...

Conclusion from the call: 1 call for generic events. Just type and description.

These logs are super interesting. Thanks for the additional info. I'm trying to figure out what happened.

So, what happened here was: - one side created bunch of orders - other side created 1 order that matched them all in quantity Result: => all the concurrent transfers...

This issue can be separated into 2: - my above comment about what happened (TBD on how to handle these scenarios) - xud should not crash after a failed swap...

Lowering the priority of this since it's not causing xud to crash any more and we need to discuss on how to solve this.