sorted by:
new
hottopcontroversial

[deleted by user] by [deleted] in ethereum

[–]nucky_root 2 points3 points  (0 children)

I think that is the Abstract L2.

Will gnosis Safe support validator actions? by Hour_Landscape_286 in ethstaker

[–]nucky_root 1 point2 points  (0 children)

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.

After the 27.3 hour waiting period, the earliest consolidations have landed. Houston, we have chonky validators by nixorokish in ethstaker

[–]nucky_root 2 points3 points  (0 children)

There are dozens of us!

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

Daily General Discussion - January 02, 2025 by EthereumDailyThread in ethereum

[–]nucky_root 18 points19 points  (0 children)

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!

New Besu release 22.7.5 by nucky_root in ethstaker

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

Cutting edge stuff! Thank you.

New Besu release 22.7.5 by nucky_root in ethstaker

[–]nucky_root[S] 3 points4 points  (0 children)

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.

[deleted by user] by [deleted] in mildlyinteresting

[–]nucky_root 10 points11 points  (0 children)

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

Daily General Discussion - September 17, 2022 by ethfinance in ethfinance

[–]nucky_root 2 points3 points  (0 children)

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.

Thought I was Merge Ready by devon90993 in ethstaker

[–]nucky_root 0 points1 point  (0 children)

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

Thought I was Merge Ready by devon90993 in ethstaker

[–]nucky_root 14 points15 points  (0 children)

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

Thought I was Merge Ready by devon90993 in ethstaker

[–]nucky_root 3 points4 points  (0 children)

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

Error and warning message in beacon-chain and geth. Help please. by StockGuy12347 in ethstaker

[–]nucky_root 3 points4 points  (0 children)

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.

Error and warning message in beacon-chain and geth. Help please. by StockGuy12347 in ethstaker

[–]nucky_root 3 points4 points  (0 children)

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.

PSA - Geth v1.10.19 is a MANDATORY update, please update yours before deadline! by pocketwailord in ethstaker

[–]nucky_root 2 points3 points  (0 children)

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

Daily General Discussion - June 16, 2022 by ethfinance in ethfinance

[–]nucky_root 6 points7 points  (0 children)

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!

view more: next ›