Unable to decode storage system.events after upgrading node template to 0.9.30 release

[lana-shanghai]

Hi, I am bumping into this issue with both running polkadotjs/apps locally, and using the polkadot.js.org page with the substrate node template (with 0.9.28 everything works well):

Browser Google Chrome, node version

npm version
{
  'polkadot-apps': '0.121.2-110-x',
  npm: '8.19.1',
  node: '16.17.0',
  v8: '9.4.146.26-node.22',
  uv: '1.43.0',
  zlib: '1.2.11',
  brotli: '1.0.9',
  ares: '1.18.1',
  modules: '93',
  nghttp2: '1.47.0',
  napi: '8',
  llhttp: '6.0.7',
  openssl: '1.1.1q+quic',
  cldr: '41.0',
  icu: '71.1',
  tz: '2022a',
  unicode: '14.0',
  ngtcp2: '0.1.0-DEV',
  nghttp3: '0.1.0-DEV'
}

[hbulgarini]

@jacogr reading the error i wonder if this paritytech/substrate#12219 included in the release 0.9.30 has something to do.

[hbulgarini]

also this paritytech/substrate#11981 renames the Event type to RuntimeEvent over the frame_system::Config, might also worth checking i think.

[jacogr]

The issue with Substrate (spec_name “node”) and the template (spec_name “node_template”) is that the API only tracks master. So for these it explicitly applies a weight override to use the latest v2.

Basically it means that older versions of those with the matching spec_name won’t work. There is most probably already a fix applied in api master that will also downgrade types based on detection (current releases versions only upgrade with detection - so without a downgrade the v2 weights are always applied to any “spec_name == node”)

[polkadot-js-bot]

This issue has been open for 21 days with no activity and is not labelled as an enhancement. It will be closed in 7 days.

[polkadot-js-bot]

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue if you think you have a related problem or query.