Remove E from validator_client types where it's not required #6727
Conversation
jxs
force-pushed
the
remove-e-from-validator-client
branch
2 times, most recently
from
30c3a7c to
96dcd1d
Compare
| object, | ||
| Web3SignerObject::Deposit { .. } | Web3SignerObject::ValidatorRegistration(_) | ||
| ) && fork_info.is_some() | ||
| if matches!(message_type, MessageType::ValidatorRegistration) && fork_info.is_some() |
There was a problem hiding this comment.
object can never be a Web3SignerObject::Deposit as a SignableMessage doesn't convert to it, see line 202 above
There was a problem hiding this comment.
Feels kinda hard to keep track if SignableMessage starts converting to a Web3SignerObject::Deposit in the future.
I don't see the issue with keeping it as is, but what you said makes sense as well.
Although, i don't have enough context on the web3signer to know for sure
jxs
force-pushed
the
remove-e-from-validator-client
branch
8 times, most recently
from
6f0df3d to
b01c568
Compare
jxs
force-pushed
the
remove-e-from-validator-client
branch
5 times, most recently
from
b4920c5 to
08b3156
Compare
…rom-validator-client
jxs
force-pushed
the
remove-e-from-validator-client
branch
from
08b3156 to
a9cc2fb
Compare
| @@ -10,7 +10,10 @@ path = "src/lib.rs" | |||
|
|
|||
| [dependencies] | |||
| account_utils = { workspace = true } | |||
| beacon_node_fallback = { workspace = true } | |||
There was a problem hiding this comment.
Not really sure why we had to add dependencies here
There was a problem hiding this comment.
yup you are right, it was because I had remove doppelganger_service as a separate crate but I have since removed again, thanks Pawan!
| object, | ||
| Web3SignerObject::Deposit { .. } | Web3SignerObject::ValidatorRegistration(_) | ||
| ) && fork_info.is_some() | ||
| if matches!(message_type, MessageType::ValidatorRegistration) && fork_info.is_some() |
There was a problem hiding this comment.
Feels kinda hard to keep track if SignableMessage starts converting to a Web3SignerObject::Deposit in the future.
I don't see the issue with keeping it as is, but what you said makes sense as well.
Although, i don't have enough context on the web3signer to know for sure
and the
Ethspecparameters can be passed on function all time