on Moonriver? This is getting ridiculous
The issue started on February 7th and whole tokenomics and dapps got affected by it. Whether the responsibility is on Parity or some other entity, lt only feels like dotsama stinks lately as there's no official announcement about the issue or any ETA about the fix
We are doing everything that depends on us, but the main fix is in the parity hands: https://kusama.polkassembly.io/post/1424 https://github.com/paritytech/polkadot/issues/4911
From another perspective, this case is demonstrating how much a Canary network is a good idea to keep safe the main one (Polkadot/Moonbeam)
People aren't some test subjects tho, client updates should be tested properly before the deployment whether it's on Kusama or Polkadot. Stalling the whole network for almost 3 months is unbelievable
Обсуждают сегодня