Add documentation for zrml-futarchy #89
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
| _negative outcomes_. When calling the `submit_proposal` extrinsic, this data is | ||
| specified as the `oracle` parameter, whose fields are `pool_id`, | ||
| `positive_outcome` and `negative_outcome`. |
There was a problem hiding this comment.
In the example above there are two positive outcomes, one for L and one for S, right? (and two negative outcomes)
There was a problem hiding this comment.
So, I expect two proposals to be submitted. One for L and one for S. Is this right? Then we have two pools, right? But this is also confusing from the standpoint that one can think about a pool that trades Welfare measure long if X enacted (L+) and Welfare measure short if X enacted (S+) and another pool that trades Welfare measure long if X not enacted (L-) and Welfare measure short if X not enacted (S-).
There was a problem hiding this comment.
On the other hand I read this:
Zeitgeist's combinatorial tokens allow users to combine outcome tokens of several markets and trade these combined tokens in a single liquidity pool.
There was a problem hiding this comment.
No, just one positive and one negative outcome. The idea is to measure whether or not the welfare measure is higher if the proposal is enacted or not. This boils down to checking that L+ is more valuable to L-.
|
The vercel deployment failed. |
No description provided.