Robiquet

A few other notes from my side: - Votes can be changed, even after the end block has passed - Jurors that have failed to vote still have the 'ok'...

"long", "Long", "Short", `0` and `1` also give the same error message. However a random string or number gives a different error

I think this is a runtime restriction @Chralt98

>Even if we had a dispute suggestion, the outcome could still be wrong, leaving us with the same situation as we have right now. I am not saying this is...

Anything that alters the original resolution criteria shouldn't be allowed as traders would have already positioned themselves based off that description. I think additions to resolution criteria where things are...

Thanks @TarikGul we managed to get it working with [this change](https://github.com/zeitgeistpm/sdk-next/pull/50/files) and signing with a keyring pair, see transaction [here](https://polkadot.js.org/apps/?rpc=wss%3A%2F%2Fbsr.zeitgeist.pm#/explorer/query/0xf9d3071a70c01306d53a76152e1565765134af84ea573c66ee0edc7baee056f5). However when we try to sign with an extension we...

Hi @TarikGul would you be able to take a look at this and let us know the best course of action?

I'm using version 0.44.1. I think this is the issue because it looks very similar to [this](https://github.com/polkadot-js/extension/issues/1314). It looks like the reason for it was that [these changes](https://github.com/polkadot-js/api/pull/5752/files) to override...

@gagi13 I'm not too sure about that as the correct overrides should already be there for the asset hubs. I would try different wallets and versions of polkadot js. It...

> New versions of the extension have both been released for a while now: @Robiquet is this still an issue? Yeah the new release of the extension has made things...