Allow providing suggestedFeeRecipient as a file about nimbus-eth2

[kdeme]

I think you could make use of the yaml config file for that: https://nimbus.guide/options.html#configuration-files

[jakubgs]

But I don't want to handle the whole file as a secret, just the fee address.

[tersec]

How is something which shows up in plaintext in the block on chain a secret?

[jakubgs]

Because you might want to avoid the association of a wallet address and yourself?

[tersec]

I mean, again, in plaintext for blocks on chain. If that validator never proposes, then it's moot. If it does, then the world will see it anyway, no?

I guess I'm missing or misunderstanding something.

[jakubgs]

I forgot to mention that my configuration is public:
https://github.com/jakubgs/nixos-config/blob/master/roles/nimbus-eth2.nix

Considering the fee recipient address can be looked up on the chain and associated with specific nodes and validators I do not want to include it in my configuration without encrypting it and treating it as a secret. And because secrets in NixOS have to be files which are created at runtime I would like to provide it as a file, rather than having to treat the whole configuration as a secret. Effectively negating the declarative nature of NixOS for this particular service.

[cheatfate]

@jakubgs you can store suggestedFeeRecipient in file called suggested_fee_recipient.hex in hexadecimal form inside your validator directory.

[jakubgs]

Oh, that's neat! That would work for me.

I see this mentioned here: https://nimbus.guide/data-dir.html#secrets-and-validators
But I see no mention of this in: https://nimbus.guide/suggested-fee-recipient.html

[tersec]

So this is a documentation issue now, not a missing-functionality issue?

[jakubgs]

Ah, forgot to close it.