Ricardo Maltez

@ivanturlakov the "types" errors was expected after the runtime upgrade, it's necessary to upgrade the joystream-node after the Nara runtime upgrade. I have done that, please try again to access:...

@ivanturlakov also the expected council duration parameters is here: https://github.com/Joystream/joystream/issues/4866#issuecomment-1732561544 please update your tests results based on that

it seems that this bug could be related with freezing, unfreezing the pallet and then freezing it again

@mochet good questions! In Nara AFAIK the validator node upgrade is not really mandatory, during the QA tests we tested using only ephesus validators and the network keep running fine...

More info here: https://wiki.polkadot.network/docs/learn-proxies

> @freakstatic any updated on the internal review? sorry for the late reply, I was able to run it and got this file as [output](https://filebin.net/49ajs0u9w7be3hkh/bag_availability.json.txt). this [tool](https://github.com/Joystream/community-repo/pull/679) can be handy...

so I suggest that we develop something with puppeteer if the objective is to check how good are the distributors when using atlas. if we gonna check how good are...

I found that at least this fields have different timestamps for different QN instances: - bounties - createdAt - updatedAt [Check Diff](https://www.diffchecker.com/dnisVyY7) ``` query { bounties (orderBy:title_ASC, limit:1000) { id,...

For the bounties I found the following places in the query-node mapping code where `new Date()` is used https://github.com/Joystream/joystream/blob/3153a3f7f4cef19f2441e92c6de57e7b897e84a6/query-node/mappings/src/bounty.ts#L215 https://github.com/Joystream/joystream/blob/3153a3f7f4cef19f2441e92c6de57e7b897e84a6/query-node/mappings/src/bounty.ts#L197 https://github.com/Joystream/joystream/blob/3153a3f7f4cef19f2441e92c6de57e7b897e84a6/query-node/mappings/src/scheduler.ts#L62

> For proposals that are about to expire (