Augur fixes chainlink

devpost.com/software/chainlink-u2661-augur-9wsdou
>Chainlink oracles can theoretically be affected by 3rd parties incentivized to manipulate API data.
>Since we are prediction market nuts and want to be able to get external API data in a trusted way, we thought of a workaround by marrying Chainlink and Augur to have the best of both worlds: faster resolutions and a robust fallback oracle.
OH NO NO NO

Attached: gallery.jpg (695x494, 106K)

Other urls found in this thread:

docs.chain.link/docs/big-query-chainlink-testnet
twitter.com/chainlink/status/1164133358101831680
twitter.com/AnonBabble

All in HOT

Chainlink just adds complication here actually.

V2 Augur has a short path of resolution that's about 24 hours. If you're getting data from an API for automated smart contract execution you want to be absolutely certain it has the data at the time you pull it anyway so you can't get "instant" resolution.

It is funny that people are trying to find ways to make Chainlink not an absolutely useless project though.

this. any programmer knew Chainlink was useless but the fact that no one is using it after 1 year testnet and 2 months mainnet should be enough to prove it to the non-technical people who don't understand the tech.

Chainlink is supposed to be highly modular.
All of its contract system (reputation, aggregation, and order matching contracts), as well as stuff like KYC and SGX methods, are all meant to be provided by third-party listing services.
This is all laid down in the white paper.
Adding a "secondary dispute layer" is very much part of this.

>If you're getting data from an API for automated smart contract execution you want to be absolutely certain it has the data at the time you pull it anyway so you can't get "instant" resolution.
lmao, and how does Chainlink not have "instant" resolution?

>no one is using it after 1 year testnet
Google Cloud was using the testnet: docs.chain.link/docs/big-query-chainlink-testnet
lol

Lets say you have a contract that will pay out some money based on the price of X. Theres a feed that periodically updates with data about the price of X.

Now lets say your contract will pay out based on the price of X at time T. Do you have it pull the data at exactly time T? What if the feed itself is down? What if it just hasn't updated with that data yet? A lesson from Augur (which people actually use and has undergone a ton of testing in the real world) is that these things do happen and its best to have some buffer time between the end of an event and resolution.

Chainlink people wouldn't know this because it's a joke and they dont give a shit if anything is ever actually made with it.

This entire thing is a thought exercise that only applies to Chainlink's initial mainnet, before reputation/staking becomes active.
It says so in the introduction.

Nevertheless; this: >Chainlink is supposed to be highly modular.
>All of its contract system (reputation, aggregation, and order matching contracts), as well as stuff like KYC and SGX methods, are all meant to be provided by third-party listing services.
>This is all laid down in the white paper.
>Adding a "secondary dispute layer" is very much part of this.

Repuation and Staking is never coming to Chainlink. They've never actually described in any amount of detail how such a system would work. I've read the whitepaper and their docs. They don't have it because the only way they could have it is by essentially re-creating Augur which would make them entirely pointless.

>What if the feed itself is down? What if it just hasn't updated with that data yet?
This has nothing to do with "instant resolution".
If the contract specifies "price P at time T", then that's what you'll get, regardless of whether ETH processes the contract in 1 second or 1 week.

Also, what you're describing is the source's problem, not the oracle's.
This is like seeing a motorized car for the first time and asking "what if the bridge you're driving on falls down?".

Even then, Chainlink clearly specifies that multiple parallel sources are ideal, and the mainstream adoption of decentralized oracles may even cause "decentralized sources" to become a reality. Much like cars changed the very nature of roads.

>>Repuation and Staking is never coming to Chainlink.
Oh, so you're arguing in bad faith.
In that case, get fucked faggot.

Bend those knees, Joey. It ain't gonna suck itself.

Attached: 1538510256703.png (869x952, 91K)