Nicolas Ochem

how about `unsafe_deterministic_key_seed` or `unsafe_key_seed` I want it to have unsafe in the name, because it is :)

OK, makes sense. I am actually using a seed for all faucet keys as well in #224 , and it's safe if you are careful with the seed.

We are hardcoding mainnet snapshots by default, which is useful for starting a mainnet node. When starting a private chain, it's necessary to override it to "null". Maybe we could...

Yes, I figured this shortly after writing this ticket, and it works. Still it doesn't hurt to display it, but feel free to close otherwise.

@alejandrojnm hi, did you have a chance to look? I am still blocked from resizing my node pools from pulumi (which is using this code). thanks in advance.

Hitting this with preview on github action. No issues when running preview locally from laptop. It is causing preview to hang.

we are not including the block fees into the reward distribution anymore, because the stakers don't get any block fees, so it would be strange if delegators received them.

> Our concern is, with this PR, will payments like the above go away? If they do go away, then wouldn't delegated rewards for the unstaked balance in the baker...

Here's a hint: https://github.com/midl-dev/tezos-serverless-signer-apps/blob/main/consensus-kms-signer/signer/tezos-kms-client.mjs#L94-L99 1. append prefix bytes `040101` 1. append the public key hash of the signer, in bytes, without prefix 1. append the message being signed, in bytes,...

An update on this. When running in retry mode, for every delegator with a failed payout, we update the balance: https://github.com/tezos-reward-distributor-organization/tezos-reward-distributor/blob/master/src/pay/retry_producer.py#L106-L107 but the only other occurence of `update_current_balances()` function in...