Jacob Shufro
Jacob Shufro
> @jshufro this is going to obviate your one-word-at-a-time verifier, want to give it a look? This changes the api container, which is downstream. The word-at-a-time flow passes the full...
Ah I see, you don't want the mnemonic exposed when the cli forks off the api call. Well, this seems fine, though now I wonder if it has any value...
Hey @infosecual I believe I know why this happens. When you convert a solo validator into 4x LEB8s, you're actually only making 3 _new_ keypairs. The original keypair has to...
This theory didn't pan out; the code paths are the same. You recovered the wallet the second time with `--skip-validator-keys` (I see `(ignoring validator keys)`), which is likely why it...
The code there also accounts for solo conversions, provided the keys are in the custom_keys path.... are they?
You can use rocketpool_api to get a json formatted response. Ie, ``` docker exec -it rocketpool_api /go/bin/rocketpool api minipool status ```
Have you tried a different checkpointz provider? `https://goerli.beaconstate.ethstaker.cc/` has worked well for me in the past. I'm 99% sure this is not a smartnode issue.
Ah. Well, the [Mr. Frundles](https://github.com/sigp/lighthouse/releases/tag/v3.3.0) release of LH from Nov 2022 added a feature that isn't supported by checkpointz. ``` If the checkpoint sync provider does not support the feature...
The docs on the website fall out of sync every hard fork unfortunately. Probably room for improvement there, you're right.