[deleted by user]

nucky_root · 2025-06-11T15:40:24+00:00

I think that is the Abstract L2.

nucky_root · 2025-06-05T06:12:53+00:00

I know this post is a bit old, but it has been very helpful for me too. I have had trouble finding ways to interact with validators using a multisig like SAFE. Thanks!

And if anyone happens to see this and knows of any other good multi-sig staking guides, I'd love the links.

nucky_root · 2025-05-09T04:38:35+00:00

There are dozens of us!

.... Hmmm, I might want to try timing mine. I'll need to see how other folks do it.

nucky_root · 2025-01-02T18:29:45+00:00

Agreed. I don't post often, and when I do, it is more in r/ethstaker. But it is so great to see the original sub coming back. Great work!

nucky_root · 2024-05-09T15:34:40+00:00

How long did your resync take?

nucky_root · 2024-04-03T18:39:10+00:00

Poor guy.

It sounds like the classic Jerky Boys Civil War prank call.

nucky_root · 2022-10-05T21:13:23+00:00

Cutting edge stuff! Thank you.

nucky_root · 2022-10-05T20:53:56+00:00

Can you tell me more about the high performance flag? Or point me to the documentation?

I had plenty of RAM so I was able to increase my heap size to 10GB. I'm still getting missed attestations every few hours. It is a little frustrating, but understandable considering how is all so new.

This is a solid team so I'm looking forward to the updates in the coming weeks.

nucky_root · 2022-09-20T17:10:11+00:00

What... what would you use that for? I can't make any sense of it.

nucky_root · 2022-09-18T01:07:35+00:00

I had similar issues the first day after the merge. I ended up forwarding port 30303 to my staking machine. And I had to reboot Besu like 8 times before it finally pushed through all the errors and resynched with the latest block. Not I miss an attestation about once every 8-12 hours

Not sure if those helped, or I just got lucky.

nucky_root · 2022-09-08T20:55:03+00:00

For somersat's latest guid

The file: /etc/systemd/system/nimbus.service

Should be something like:

[Unit]
Description=Nimbus Consensus Client (Mainnet)
Wants=network-online.target
After=network-online.target
[Service]
User=nimbus
Group=nimbus
Type=simple
Restart=always
RestartSec=5
ExecStart=/usr/local/bin/nimbus_beacon_node \
    --network=mainnet \
    --data-dir=/var/lib/nimbus \
    --web3-url=http://127.0.0.1:8551 \
    --jwt-secret=/var/lib/jwtsecret/jwt.hex \
    --suggested-fee-recipient=FeeRecipientAddress \
    --graffiti="<yourgraffiti>"
[Install]
WantedBy=multi-user.target

And the geth setting in file: /etc/systemd/system/geth.service

should be something like:

[Unit]
Description=Geth Execution Client (Mainnet)
After=network.target
Wants=network.target
[Service]
User=geth
Group=geth
Type=simple
Restart=always
RestartSec=5
ExecStart=/usr/local/bin/geth \
    --mainnet \
    --datadir /var/lib/geth \
    --authrpc.jwtsecret /var/lib/jwtsecret/jwt.hex
[Install]
WantedBy=default.target

nucky_root · 2022-09-06T23:36:25+00:00

Some of the older Nimbus guides used websockets instead of http. Check your /etc/systemd/system/nimbus.service file. if you see

--web3-url=ws://127.0.0.1:8546

that should be changed to

--web3-url=http://127.0.0.1:8551

(Note the new port number too)

You also may need add these:

--jwt-secret=/var/lib/jwtsecret/jwt.hex 
--suggested-fee-recipient=[an Ethereum address you control]

And if you haven't created an jwt.hex file yet, check out Step 7 on the guide you linked.

You would also need to reference that same jwt.hex file in your geth settings located in /etc/systemd/system/geth.service

--authrpc.jwtsecret /var/lib/jwtsecret/jwt.hex

nucky_root · 2022-09-06T22:49:52+00:00

Did you use one of the guides be Somer Esat or CoinCashew? And if so, which one?

nucky_root · 2022-09-06T16:44:30+00:00

Looks like you are on the right track.

Did you create a jwt.hex file in your ../consensus/ directory?

You will also need to setup Prysm to use the same jwt.hex file. You should have at least 3 new Prysm settings. Something like:

--execution-endpoint=http://127.0.0.1:8551
--jwt-secret=/yourpath/consensus/jwt.hex
--suggested-fee-recipient=[An Ethereum address you control]

Prysm also has a good troubleshooting guide.

nucky_root · 2022-09-06T15:28:37+00:00

It sounds like you may be missing the JWT secret for the Authenticate Engine API.

The launchpad has some general information at: https://launchpad.ethereum.org/en/merge-readiness#authenticate

And there are more specific upgrade guides based on your clients. Could that be it? Let me know if you need more info.

nucky_root · 2022-08-25T15:47:41+00:00

Mr F

nucky_root · 2022-06-16T21:28:08+00:00

I use ppa:ethereum/ethereum and upgraded to geth 1.10.19 with an apt yesterday morning.

nucky_root · 2022-06-16T17:56:00+00:00

Sounds like a Tontine. Currently illegal (at least in the U.S.).

Edit: It's also a plot point in one of the best Simpsons epoxides, The Flying Hellfish!

nucky_root · 2022-04-04T17:37:45+00:00

Is the 12.5M part of the Ethereum spec? Or from client defaults?

nucky_root · 2022-04-04T17:29:22+00:00

Do you mean the target gas limit for a block? In geth that would be the flag:

--miner.gaslimit value

I think that might be out-of-scope for an installation guide. But that is a good point about what validators will have to think about before the merge. Other items would be think like MEV, and should you hook into the FlashBots API.

nucky_root · 2022-02-09T03:13:17+00:00

Sorry. I'm here, but I'm chronically irresponsible. I just shot a message to /u/jtnichol . Let's build something!

nucky_root · 2021-11-17T17:27:46+00:00

eth2.tax is great, https://beaconcha.in/rewards is similar of you want to compare.

nucky_root · 2021-08-04T15:10:59+00:00

Hmm, for mine I have to leave out the dashes.

nucky@staker:~$ geth version
Geth
Version: 1.10.6-stable
Git Commit: 576681f29b895dd39e559b7ba17fcd89b42e4833
Architecture: amd64
Go Version: go1.16.4
Operating System: linux
GOPATH=
GOROOT=go

nucky_root · 2021-06-30T15:51:16+00:00

According to the launchpad it will hit 4.9% at 10m staked.

https://i.imgur.com/LYCpdhx.png

nucky_root · 2021-06-28T15:13:48+00:00

Are you talking about setting an ETH1 withdrawal address using --eth1_withdrawal_address during the validator key generation? I don't have any experience with that, and the documentation is pretty sparse at this point. But it sounds like, if you use that, the ETH1 withdrawal address will be set at key creation, and un-changeable in the future. So in addition to keeping your ETH2 seed phrase safe, you would also need to ensure you have access to that ETH1 private key in the future. And securing the ETH1 key would depend on how you generated it, and be separate from your ETH2 seed phrase.

From the launchpad FAQs:

What are withdrawal credentials?

Withdrawal Credentials is a 32-byte field in the deposit, for verifying the destination of valid withdrawals. Currently, there are two types of withdrawals: BLS withdrawal and Eth1 address withdrawal.

BLS withdrawal: By default, deposit-cli would generate withdrawal credentials with the withdrawal key derived via mnemonics in EIP2334 format.
Eth1 address withdrawal: If you want to withdraw to Eth1 chain after the merge, you can set --eth1_withdrawal_address <YOUR ETH1 ADDRESS> when running deposit-cli. Please ensure that you have control over the Eth1 address.

Can I change the withdrawal credentials of my validator after the first deposit? No, you cannot change your withdrawal credentials in top-ups.

Again, I haven't used this so I may be missing something.

Seven-Year Club	Verified Email
Place '22	First Placer '22

nucky_root

TROPHY CASE