Jacob Shufro

> we are filtering those out on the beacon node before sending the registrations to the builder that's good and all but i really hope some day to be able...

They have implemented it here: https://github.com/sigp/lighthouse/pull/4343 I mistakenly thought this was already working and regressed, though. I will try to get my hands on some logs

cc @superphiz who is dealing with this right now

After a bit of inspecting it seems like this is because `--unecrypted-http-transport` was passed: ```rust .arg( Arg::with_name("unencrypted-http-transport") .long("unencrypted-http-transport") .help("This is a safety flag to ensure that the user is aware...

I'd prefer if the error message specified _why_ conditionally-required fields were indicated, ie: ```diff -error: The following required arguments were not provided: +error: The following arguments are required by --unencrypted-http-transport...

Duplicate of https://github.com/rocket-pool/smartnode/issues/194 I'll ping the team about it. I opened a pr to fix it 2 years ago. I think it's still valid - https://github.com/rocket-pool/smartnode/pull/195

I think the best thing would be to rebase onto the `v2` branch. A lot of the work unfortunately won't apply, but the good and bad news is that this...

I've been tracking this one. So far it seems like a besu issue but it's temporary and difficult to reproduce. The transaction is submitted anyway

It's unlikely we'll branch out beyond the receivers supported by alertmanager, but you can run this project to relay them:

Please vote here: Note that it might be some time before we are able to roll out support for additional channels. We're blocked on a major refactor.