Alessio Onori

Hey Fabio, just a suggestion. Regarding [Graphs of Functions & Kinematics](https://github.com/lamafab/notes/blob/fabio-lama-notes/level-4/computational-mathematics/student-notes/fabio-lama/cheatsheet_graphs_functions_kinematics.png), specifically the Kinematics section: I found really handy to think in terms of derivatives and integrals. So, rather than...

I used to get the `Rewards to be claimed` [like this](https://github.com/w3f/polkadot-k8s-payouts/blob/v1.2.7/src/claimer.ts#L145-L148), but now it [seem to be deprecated](https://github.com/polkadot-js/api/blob/v10.11.3/packages/api-augment/src/substrate/query.ts#L1757-L1759) and the note says to use `EraInfo`... any suggestion ?

Thanks for the answer. fyi maybe related: being connected with a kusama node on v1.10.0, performing this (`this.api.derive.staking.query(validatorAddress,{withLedger:true})`) I don't see the `ClaimedRewards` property, but just the `legacyClaimedRewards`. And the...

Thanks for the quick resolution, I indeed implemented it using `this.api.derive.staking.query(validatorAddress,{withLedger:true, withClaimedRewardsEras: true})` For reference: https://github.com/w3f/polkadot-k8s-payouts/blob/v1.2.9/src/claimer.ts#L138-L171 --- Unfortunately, there seems to be a bug still: even if unclaimed rewards are...

> > * 6512, error > > Older rewards should work as usual. After the upgrade, all claimed rewards for eras are noted in the new storage `ClaimedRewards`. Older rewards...

> > Probably bug with the derived api? If you query the storage directly you can see that it is claimed. > > ```js > console.log((await api.query.staking.claimedRewards(6512, 'GaK38GT7LmgCpRSTRdDC2LeiMaV9TJmx8NmQcb9L3cJ3fyX')).length) > //...

> Before https://kusama.polkassembly.io/referenda/373, claimed rewards were saved in the storage item `Ledger` as a vec. After the upgrade it is stored in `ClaimedRewards`. Anything claimed after the upgrade is marked...

To recap: - [x] dockerhub images to be set: otv-gateway, otv-worker, otv-telemetry - [x] Gateway chart, stateless => Deployment - [x] Worker chart, stateless => Deployment, maybe autoscaling - [x]...

> * there doesn't need to be any exposed ports, save for the telemetry and db connections An exposed port is needed for the healthcheck

Thanks a lot @saul-jb, this was exactly what I was looking for ❤️ All the other (few) examples concerning e2ee on node are outdated, difficult to find, and not working....