So, it is not so much an attack on the oracle as it is the exploitation of a naive counter party. The sucker accepted an unknown, variable price, which turns out could, under the terms, be set by the other contract participant. Oops. Not the oracle's fault.
Conversation
The answer is no
2
7
Depends on the circumstances. If there was an actual malfunction, yes. But if the markets are just inefficient because some large prop firm randomly shut down, and you think thereβs such a sweet arb opportunity lying around, why complain to kraken? Go ahead and take it
2
11
The exchange is not responsible for the price whatsoever. The exchange's responsibility is to match orders. The "price" (bid, ask, last trade, whatever) is set by the market participants, not the exchange. So, if the tech is working properly, the exchange is never responsible.
1
1
12
if all orders are matched properly, why should kraken be liable?
2
3
So you're arguing for circuit breakers or limitations on order management to prevent a price from moving despite intent of the market participants? How do you know when your market is out of sync vs leading? How long do you wait to find out and who gets blamed when you're wrong?
Max order size, max percent limit away from mid, enter auction mode (allows arbers time to prepare capital to arbitrage the flow). Many such concepts can be taken from trad mkts (esp FX, equities)
I agree there are always tradeoffs and new problems would then arise potentially
3
21
Yeah, ultimately the answer is more liquidity with time. In some cases people are glad you liquidated them instantly, in others mad that you didn't wait longer. Someone will always end up holding the bag. It's very hard with 24/7 continuous, loosely connected global markets.
1
1
8
Show replies
Circuit breakers are obviously much better than what happened on Kraken ETH/USD in spring 2017!




