Harald Heckmann
Harald Heckmann
Yes, I proposed both the convention to check in the PR and the yearly update to reduce human error in case of manual copyright adjustment. However, if we can use...
I'd say we are free to use whatever is best suited for that task. I am pretty confident that there are already scripts out there that do this, so a...
Depends on AMM 2.0
Ideally we'd have those tests separated, as in prediction-markets unit tests (within the crate) mock the functionality of dependencies and can work solely by itself, thus effectively testing the unit...
> Why don't you let the admin of the campaign asset define what the fee factor should look like? For the sake of simplicity (not having to maintain extra metadata),...
This is also a continuation of the discussion at https://github.com/zeitgeistpm/zeitgeist/pull/1099#discussion_r1340004299 I think the first simple adjustment would be to remove the requirement `scoring_rule == ScoringRule::orderBook`. This would generally allow trading...
Guess it will be tricky to define a `Default` as it depends on the runtimes configuration of the prediction markets pallet. I assume it makes sense to define it in...
> Local node produces blocks and accepts transactions. This is planned to be part of the release automation CI https://github.com/zeitgeistpm/zeitgeist/issues/870
I realized that we need two scripts: 1. One script triggers when the benchmark label is set. It only respects our own pallets stored in the folder *zrml*. The label...
Automatic benchmarks of all pallets once per release are sufficient for now. I think it makes more sense to shift the responsibility of ensuring up to date weights to the...