james-prysm
james-prysm
we added another flag used with suggested-fee-recipient called `enable-validator-registration` to enable this. you can see what happened in my latest [PR](https://github.com/prysmaticlabs/prysm/pull/10992). currently only in develop.
@elopio responded to the kiln question, wondering if that answered you.
@tbenr just seeing this now... thanks for letting me know, I'll go update this.
the way Prysm works right now is we have an `enable-builder` flag that will turn on validator registration. if a user has their prysm validator client started with `enable-builder` then...
@timg512372 @kasey sorry just taking a look at this, to be more clear this issue was not for the validator client ( which also has this flag) as I am...
@lyzs90 It's set the first time here, but I think to kasey's point of starting this issue, the beaconConfig was intended to be this read-only config based on network settings...
Will start to assist with this
I'd like to help on this if there are more details on what needs to be done. i'm not sure where the validator reporting metrics are and whether or not...
Will start after Eth denver by asking some individuals on their use of grafana stats from the validator, and look at what metrics can be migrated to ( beaconchain/ monitor/metrics.go?)
related issue updated