Would Nash DEX avoid issues such as this recent one with Beaxy exchange?

TLDR; an XRP “wallet exploit” led to a coordinated sell-off and trading had to be halted.

But it also sounds like the exploit might have just been a dev oversight:

Curious whether this could be another justification for non-custodial exchanges as the ideal future for secure trading, or if similar exploits could be possible on DEXs?

For Nash: the attack vector may be the same, but the attack surface would be scatered; absorbing impact. (is what I would say at first sight). Technically nash is just a matching engine, so there might be no attack surface at all on Nash side.

Also in this case it was a matter of paying attention to the docs. This ‘exploit’ was documented already a month ago: https://github.com/ripple/ripple-dev-portal/blob/master/content/concepts/payment-types/partial-payments.md#partial-payments-exploit RTFM

I would say YES this is another justification for non-custodial exchanges as the ideal future for (secure) trading. If its secure depends on the key management skills of the user.

1 Like