Chralt

It happens since I work with multiple crates.

https://github.com/zeitgeistpm/zeitgeist/pull/729#discussion_r935178800 The `*_manager` functions should probably just return their own weight plus the weight of the mutation. https://github.com/zeitgeistpm/zeitgeist/blob/d9d180353dfa80e8e9e75afc7ac89ebc8c11d1bb/zrml/prediction-markets/src/lib.rs#L2066-L2111

Mr. Malicious could now use a `dispute_duration` of zero as market creator to deny any disputes. That's why I would propose a constant `MinDisputePeriod`, which should be at least some...

I would suggest a `trait Config` constant for this.

I just realised it in the test, yeah you are right, it makes sense as it was.

But on the second look for the global dispute mechanism it would make much sense to change that. So that the users don't dispute on the same outcome. I will...

I investigated time to understand the GitHub Workflow Settings. I found, that [this](https://github.com/zeitgeistpm/zeitgeist/blob/7e1cf3d7fdece62ce054fc8603977ba0b9e54395/.github/workflows/rust.yml#L35-L36) caches the rust crates if they were already compiled. I think about ordering the matrix in a...

Thank you so much for your deep and well thoughts. I follow your structure with my comments. - I took thought into it, that we "start" a global dispute after...

I want to discuss bullet point two again. That current solution should work for categorical markets fine, because at one point, all the categories are reached. But for scalar markets...

I've not managed to completely exclude the addition of the feature `with-global-disputes` from the main-net, because the common runtime would like to know, what happens if the feature is enabled...