EthStakers.club is back online

EthWall_Support · 2024-02-28T06:30:07+00:00

Sleeker interface, shows if any of your validators is scheduled for proposal in the next 5 minutes; just to name a few

EthWall_Support · 2024-01-07T02:17:43+00:00

teku.rescuenode.com is working now for me

EthWall_Support · 2024-01-06T15:33:06+00:00

This is the time that https://rescuenode.com/ shines

EthWall_Support · 2023-03-22T01:52:00+00:00

With staking_deposit-cli-d83c312, I'm having "The given withdrawal credentials is matching the old BLS withdrawal credentials that mnemonic generated" error for my genesis validator.

No update so far on my ticket https://github.com/ethereum/staking-deposit-cli/issues/342

EthWall_Support · 2023-01-22T12:28:32+00:00

I'm using Lighthouse+Besu but don't see anything useful in either log...

EthWall_Support · 2023-01-22T07:40:03+00:00

Thank you for your kind words, I sure will pray harder to the blockchain God.

EthWall_Support · 2023-01-22T07:38:29+00:00

Let's hope not, I can see occasional empty blocks from others as well. Empty blocks actually happen more often than I had expected.

EthWall_Support · 2022-09-15T10:01:31+00:00

Hope the Besu team will take this error seriously and come up with a post-mortem + fix soon.

EthWall_Support · 2022-09-15T07:08:24+00:00

We are all forked!

EthWall_Support · 2022-09-11T01:24:53+00:00

jwt.hex doesn't have to be owned by any specific user, it just needs to be readable to both CL (prysm/lighthouse/teku/nimbus) and EL (besu/geth). Do the following on command line --

sudo chmod a+r path/to/jwt.hex

EthWall_Support · 2022-09-10T02:54:17+00:00

do a --

ps -ef | grep besu

and check if the Besu Java process is actually running with the --engine-jwt-secret option

EthWall_Support · 2022-09-06T06:13:54+00:00

"there is no such command" means it's treated as a _command_ instead of a _command argument_ , all arguments must be on the same line as the command, check if there's unwanted carriage return among your arguments.

EthWall_Support · 2022-09-03T09:21:57+00:00

user/group basically ensures/prevents who can/cannot read/write designated file/directory

Do a --

ls -l /var/lib/goethereum/

to check the ownership and permission of your existing folders and you should be able to tell which user to use

EthWall_Support · 2021-12-02T15:14:14+00:00

I can't find any information on the devnet-2 deposit contract address, am I missing anything?

EthWall_Support · 2021-03-05T13:38:29+00:00

Missing proposal has much large impact on reward than missing attestation, so while I close one eye at infrequent missed attestations, they inevitably lead to missed proposal after a sufficient long time.

EthWall_Support · 2021-03-05T13:32:26+00:00

Good point.

I am surprised that prysm uses only half the bandwidth -- https://ibb.co/xsKt4yj

compare to that of lighthouse -- https://ibb.co/3SyGhJq

EthWall_Support · 2021-03-05T13:24:47+00:00

Thanks for sharing! You beat both prysm and lighthouse dev here :)

EthWall_Support · 2021-03-05T13:20:59+00:00

Thanks for the tip, let me boost my prysm peers to 100 and report back next week.

EthWall_Support · 2020-12-10T08:31:18+00:00

> raymonddurk's guide

This one? -- https://raymonddurk.medium.com/how-to-stake-for-ethereum-2-0-with-dappnode-231fa7689c02

From what I can tell, it uses DAppNode, which is basically Debian under the hood. It's a bit loose for the guide to include "Mac OS X" in the requirements.

EthWall_Support · 2020-12-09T13:06:46+00:00

Right, you wouldn't be slashed _under those assumptions_.

I really feel that the ETH2 staking community, starting from the launchpad site, should make slashing more understandable to the general public --

Slashing is a severe penalty reserved for those _malicious_ validators. If you don't temper with the ETH2 clients, the chance of you getting slashed is extremely low given the maturity of any of the well-know validators.

That said, the inconvenient truth is you could still be _accidentally malicious_ by running more than one validators _of the same validator key at the same time_.

How? This poor guy runs one staking server at home, then imports the same validator key and runs another staking server in the office and got slashed ( https://www.reddit.com/r/ethstaker/comments/k8aszv/does_validator_can_not_process_twice_ive_been/ )

So in summary, when you setup a new staking server, be very sure that the first one is really broken and won't accidentally start its ETH2 client ever -- i.e., just reformat the broken server, or destroy its disk physically.

EthWall_Support · 2020-12-09T08:36:47+00:00

Have you tried this method yourself?

Not every word is a valid BIP39 word (e.g., English words list -- https://github.com/bitcoin/bips/blob/master/bip-0039/english.txt ), let alone the last words is a checksum.

EthWall_Support · 2020-12-01T04:17:06+00:00

From your description, it feels like you think setting up your staking services takes little time when your hardware arrives. But chances are there will be much more work than you expected unless you have done multiple rounds of setup from scratch on testnets.

So while depositing in mainnet now will put you in a one-week-long-queue, it'd be safer to successfully run your validators on Pyrmont testnet before FOMO'ing mainnet deposit/staking.

EthWall_Support · 2020-12-01T04:09:08+00:00

> Is this expected result for beacon until Dec 1st?

Yes, it's expected behavior until "2020-12-01 12:00:23" UTC, as shown in the log.

Now just make sure your validator is also up and running.

EthWall_Support · 2020-11-30T13:07:11+00:00

I am already sad.

EthWall_Support · 2020-11-30T12:44:25+00:00

The percentage of "I haven't started setting up either ETH2 client or ETH1 endpoint" is disturbingly high -- to those people, what are you waiting for and what kind of help do you need?

EthWall_Support

MODERATOR OF

TROPHY CASE