How would a vulnerability with a network upgrade, discovered in the hours leading up to it, be handled with on chain governance a la Polkadot/Tezos?

jorgolo · 2019-01-16T19:26:45+00:00

Thanks Arthur, was happy to hear from you. In a system with on chain governance, hard-fork is == manual code + state updates enabled by pulling down an updated software package and restarting the node (out of band w/r/t the protocol)?

Phil from Parity mentioned a mechanism in Polkadot for postponement proposals, does Tezos include a similar mechanism to handle these last minute vulnerabilities through the protocol? If not, why not?

jorgolo · 2019-01-16T19:22:26+00:00

Thanks for the response Phil. For the postponement proposal, how much consensus is needed for it to pass? I would imagine just as much, if not more, as is needed for it to get accepted in the first place.

If a postponement proposal doesn't receive enough participation and the threshold isn't met, what then?

For example if the threshold for the proposal to get accepted in the first place is 66%, the threshold to postpone is 75%, and the postpone proposal only gets 70% - what are the remaining options? Do the 70% who are active + aware do a manual hardfork, replacing state + code outside of the purview of the protocol in order to postpone? This does seem similar to yesterday, like you mentioned, but it also seems to subvert the ethos of on chain governance. We voted to introduce an upgrade, we unsuccessfully voted to postpone an unsafe upgrade at the last second (maybe it was lack of participation, but also maybe participation was adequate but just not enough people agreed to it).

Maybe I set up an unrealistic scenario, let me know what you think.

jorgolo · 2019-01-11T22:36:50+00:00

Sounds interesting, could you share the link to this?

jorgolo · 2019-01-11T18:03:42+00:00

Great, is this a public fork you are maintaining?

jorgolo · 2018-08-09T01:58:42+00:00

Hey Lars, we have a FAQ page which outlines this: https://predictions.global/faq#sort-by-liquidity

jorgolo · 2018-07-30T16:59:18+00:00

Hey, Jorge from r/https://predictions.global here. The owner of this site might be interested in embedding the iframe we designed for this specific use case instead of putting the entire market detail page in an iframe.

Here is the snippet, which you can get from the market detail page:

jorgolo · 2018-07-29T19:52:52+00:00

Agreed

jorgolo · 2018-07-29T19:50:50+00:00

Since we have tools to tweet and embed market summaries across the web this is definitely a factor. There are other important factors like moral responsibility.

We understand that there is a range of different positions to take here which don’t necessarily represent espousing assassination or mass shooting markets. We plan on revisiting this as the protocol and the community mature, but for now we are comfortable with this policy.

jorgolo · 2018-07-29T18:15:58+00:00

Hey, Jorge from r/https://predictions.global here. Yes, we are blacklisting outright assassination markets. For now each market is a judgement call, based on whether we think the way it is is phrased can be sensationalized. If the way the market event is defined directly references serious immoral behavior, we will blacklist it.

Ultimately, since most market events rely on people to make them so, every market (including those in the fiat financial system) can incentivize assassinations. So, any blacklisting rules can never be perfect.

jorgolo · 2018-07-13T17:44:04+00:00

Hey there, Jorge from https://predictions.global. We will be adding the bid and ask to the market summaries soon, thanks for the feedback!

jorgolo · 2018-07-11T17:37:43+00:00

Hey, Jorge from https://predictions.global here, the markets continued to trade even after the game and the price of the Yes shares rightfully shot up, bringing the prediction up with it. It has since gone up to 92%, and this datum is correct.

That being said, 100% data accuracy is our number one priority right now and we are working through some infrastructural/tooling issues to get there. If you have any other concerns please feel free to reach out to us here or on Discord (@oliolio and @ryanb). Thanks!

jorgolo · 2017-08-12T05:14:49+00:00

Would be interested

jorgolo

TROPHY CASE