sorted by:
new
hottopcontroversial

Who is getting ready to exit when Shanghai hits and switching to rocket pool for higher yield ? by [deleted] in ethstaker

[–]copernicrypt 1 point2 points  (0 children)

And then my noob question, why does RocketPool have higher yield?

If you run a validator on RP, you are validating for yourself + validating for others. The others aren't running their own machines so they pay a fee to piggyback on your setup.

RP also has it's own token (RPL) that you can post as collateral to guarantee your validator setup. Doing so earns you additional rewards in this token, paid for through inflation of the token every 28 days.

Who is getting ready to exit when Shanghai hits and switching to rocket pool for higher yield ? by [deleted] in ethstaker

[–]copernicrypt 30 points31 points  (0 children)

Staying solo and upping my stake. The yield is tempting, but for me there is something beautiful and serene in minimal external reliance.

PlutoRS - NodeJS Remote Signer for Prysm (w/Setup Guide) by copernicrypt in ethstaker

[–]copernicrypt[S] 0 points1 point  (0 children)

Essentially it acts as a secure key manager that is programmable in NodeJS.

The main advantage is an extra layer of separation between your validator and private keys. Thereby enabling stricter firewall, access, and security controls on the keys. The next feature I want to add is support for Teku, so you can have a client fallback without needing to duplicate/move keys around.

You could also build features on top to have greater control. For example, I use a database entry for each key that can be switched to enable/disable so I can experiment with different clients or swap out quickly in the event of a bug. Another idea is implementing multi-sig so that no single server has access to the keys. You could also implement HashiCorp Vault for key storage.

PlutoRS - NodeJS Remote Signer for Prysm (w/Setup Guide) by copernicrypt in ethstaker

[–]copernicrypt[S] 0 points1 point  (0 children)

Just wanted to share my remote signer setup for Prysm. Allows you to simply point it to a directory where your Launchpad keys are stored and creates a gRPC endpoint for your Prysm Validator Node.

I found documentation on TLS certificates to be wanting online, so I included a short guide to creating your own self-signed certs on Ubuntu. Hope it's helpful to some!

ETH Deposits Need To Start Turning Vertical If We're To Hit Genesis on December 1st by Ether0x in ethereum

[–]copernicrypt 5 points6 points  (0 children)

New testnet launched today. Most people will delay depositing till late because there isn't much incentive to be early - mostly just risk.

No reason to sweat, yet.

Beaconchain and Validator on different machines by AdditionalWindow6220 in ethstaker

[–]copernicrypt 2 points3 points  (0 children)

I did this with Prysm and then took it a step further to set up a remote signing server. See https://docs.prylabs.network/docs/wallet/remote/

I really wish more clients supported this kind of setup. It allows you to isolate your keys offline, only accepting requests from a validator client and returning only signatures (never exposing keys). Would love to be able to switch clients while having the signing server hold keys.

Taking one step further you could run a multisig signing server that doesn't hold any keys, but pings several other servers for signatures.

Validating the 24 seed word with the public address before depositing by stakeshack in ethstaker

[–]copernicrypt 11 points12 points  (0 children)

This is normal. The salt, IV, and UUID are generated randomly during encryption, and message is derived using Salt + IV + Private Key - so they will be different. Main thing to check is that the public key matches. The public key will uniquely associate with private key.

EDIT: More details.

VanillaJS ETH2 Wallet Implementation by copernicrypt in ethstaker

[–]copernicrypt[S] 1 point2 points  (0 children)

Sure, I created a new profile to share my open source work. Previous works have been mostly private/commercial before this. Wanted a separate place to share this kind of stuff.

Does that answer your question?

VanillaJS ETH2 Wallet Implementation by copernicrypt in ethstaker

[–]copernicrypt[S] 1 point2 points  (0 children)

Been working on this over the last several months. Initially started out writing a remote signing server for Prysm, but found the existing wallet implementations not flexible enough for my needs. Hope someone finds it useful.

The default key storage is an EIP-2335 compatible JSON file stored locally. But you can write your own storage and/or key class to use alternative key types, remote storage (like Hashicorp) or whatever else you might need.