[ 3 / biz / cgl / ck / diy / fa / ic / jp / lit / sci / vr / vt ] [ index / top / reports ] [ become a patron ] [ status ]
2023-11: Warosu is now out of extended maintenance.

/biz/ - Business & Finance


View post   

File: 444 KB, 1440x2960, Screenshot_20190625-102059.png [View same] [iqdb] [saucenao] [google]
14348227 No.14348227 [Reply] [Original]

https://blog.synthetix.io/response-to-oracle-incident/

>> No.14348259
File: 415 KB, 1440x2960, Screenshot_20190625-102157.png [View same] [iqdb] [saucenao] [google]
14348259

>> No.14348274
File: 66 KB, 799x457, _orckal.jpg [View same] [iqdb] [saucenao] [google]
14348274

>>14348227
>tfw OP doesn't know about the real oracle incident when Sergey forgot usb stick with his sibos presentation

>> No.14348286

>>14348259
>>14348227
Chainlink will save crypto.

>> No.14349093

IMO this is a bigger deal than the giant let down we're going to get from cloudexpo

>> No.14349133

>>14348286
how does chainlink prevent oracles from lying?

>> No.14349149

>>14349133
First of all by making sure there are more than one independent oracles.

>> No.14349191

>>14349133
Oracles crosschecking eachother

>> No.14349199
File: 282 KB, 1080x1920, Screenshot_20190625-063817.png [View same] [iqdb] [saucenao] [google]
14349199

>>14348227
Oracle too

>> No.14349215

>>14348227
>agreed to reverse the trades

was this some hacker showcasing their vulnerability or did they just start pulling out fingernails?

>> No.14349281

>>14349215
This was an arbitrage bot that just happened to trigger in the small time window when the oracle was crapping out.

>> No.14349435

The trader agreed to return the $1bn in profit in exchange for a bug bounty

>> No.14349500

>>14349435
Should’ve taken the 1 B and go buy his own island

>> No.14349525

>>14349133
Staking you dumbass

>> No.14349544

>>14349525
Is a couple bucks gonna stop someone from lying?

>> No.14349634
File: 319 KB, 802x1331, Nuo Network.jpg [View same] [iqdb] [saucenao] [google]
14349634

>>14348227

>> No.14349902

>>14349634
>we are currently talking to chainlink team to implement a price oracle with them
you just win.

>> No.14350142

it wasn't the oracle just randomly crapping out. it was most of the APIs being not reachable due to a regional internet outage and 1 of the only 2 APIs left was crapping out, so the average price between the two got crapped out. If there were 3, the crapped out price would be ignored because it deviated above a certain treshold from the others.

Chainlink node operators and smart contracts that query should learn from this and consider what happened here when they figure out how API calls via chainlink nodes should be performed. Chainlink nodes are NOT immune to this problem. If the oracle was coded differently, the problem could have been averted.

>> No.14350223
File: 109 KB, 769x697, 1559175746444.jpg [View same] [iqdb] [saucenao] [google]
14350223

>>14349634
>we are currently talking to chainlink team to implement a price oracle with them
KEK