Lets assume that I create a decentralized validator (SSV) with four operators. One operator is using geth, the other three are using Nethermind, Erigon and Besu respectively.

Per the SSV rules, I believe, the 4 operators will have to come to consensus, otherwise they will try again. If they keep failing in their attempts they will just fail to attest.

This means, I think, that if geth creates a block that would fork the chain then this decentralized validator would not be able to attest.

Am I correct in all of this?

If I am then there is an advantage and a disadvantage with having a heterogeneous system with only geth execution client, over having strictly a minority client. The advantages is that I will not contribute to a fork and I will not get slashed. The disadvantage is that I’m not actively voting against geth.

Am I correct in that understanding as well?

I read that a geth archive node needs south of 20 TB and that in order for it to sync it must first have prysm sync. Both have been running for several days now and I only have 40GB from (I think) prysm.

​

Am I doing something wrong?

​

​

curl http://localhost:3500/eth/v1/node/syncing | jq

% Total % Received % Xferd Average Speed Time Time Time Current

Dload Upload Total Spent Left Speed

100 117 100 117 0 0 56 0 0:00:02 0:00:02 --:--:-- 56

{

"data": {

"head_slot": "2429997",

"sync_distance": "5527944",

"is_syncing": true,

"is_optimistic": false,

"el_offline": true

}

}

​

sudo geth attach geth.ipc

Welcome to the Geth JavaScript console!

​

instance: Geth/v1.13.4-stable-3f907d6a/linux-amd64/go1.21.3

at block: 0 (Wed Dec 31 1969 19:00:00 GMT-0500 (EST))

datadir: /mnt/Eth/Blockchain

modules: admin:1.0 debug:1.0 engine:1.0 eth:1.0 miner:1.0 net:1.0 rpc:1.0 txpool:1.0 web3:1.0

​

To exit, press ctrl-d or type exit

> eth.syncing

false

​

Truth is: I don't like managing my server and spending time on it. So I've been working on an ansible playbook automating it all. I'm quite happy about it and feel like sharing it: if it can help only a few people to get started and feel more confident running their server, then that's mission accomplished.

here's the project --> https://github.com/salanfe/eth-server

It is inspired by Eth Docker which has been a huge help to get started. Both projects are complementary. Whereas Eth Docker focuses on installing the Ethereum clients, my project focuses on setting up the linux server itself, on which Eth Docker will run. Eth Server uses ansible to automate SSH hardening, VPN setup, chrony, monitoring etc. Namely

1. eth-server sets up your staking server
2. then eth-docker sets up your ethereum clients

So far, this project is highly opinionated and works for me. My current motivation is to inspire others, but not necessary to extend it so that it can meet everyone's custom needs and setup: i.e. Eth Docker is a real utility software. This project here is mainly hacked together.

I'm also taking a different path than eth-docker about monitoring. Whereas eth-docker offers a monitoring stack, I prefer to reduce its scope to only setting up and running the eth clients. Instead, I'm installing the grafana-agent to push logs and metrics directly to grafana cloud. The decoupling between eth-docker and the monitoring was important to me, but again, a highly opinionated project.

Anyhow, I hope it can be useful to other stakers. Let me know what you think

I currently have 2TB SSD, it seems to be mostly full. I know it's a matter of time before I need to upgrade, I'm just wondering how long I have. I have Geth/Lighthouse, but if it buys me a year for some other combination, I could be convinced to switch. I know I have to resync geth one of these days anyway to get the benefits of pruning. Does geth pruning buy me more time?

Hello,

I set up an Eth2 validator in November 2020 set to a BLS withdrawal address. I foolishly copied down my Eth2 public address thinking it was my private key. I'm unable to locate my mnemonic if I ever had it.

What I do have: a folder called "validator_keys" with a keystore.json and a deposit data.json.

Is there any way I can change my withdrawal address to 0x01 using these files? Is my private key embedded in them?

Thanks.

I am in the process of setting up a validator on Allnodes. The final step now is to interact with a smart contract. It asks to interact with a smart contract (0xFA5f9..B5b18). Metamask cannot verify it and it asks to send 32 ETH with blind signing.

1. How would I verify that this is indeed safe?
2. Do all SaaS services require sending 32 ETH to some contract?

Any one else having issues with Kiln woke up this morning to all of my eth not showing in the staked pool.

Talked to their support said they were running maintenance. I found this odd because there was never a warning.

A couple hours later still says they are experiencing issues. My eth shoes back up but there's no option to exit.

So I use docker a lot on my self hosting server. I would consider myself an advanced beginner to intermediate level user certainly not an expert.

One thing I do obviously all the time is stop/start and update dockers and then rebuild and redeploy them. It's part of what makes docker, docker.

So that's what I don't get about ethdocker as a project - if you can redeploy it, how does that not create a slash able event?

I need to update my SSD and so I'm going to have to reinstal everything. I am planning on dumping prysm for client diversity. I'm investigating other options including ethdocker, and obviously I'm missing something here, but I do NOT want to rely on myself not to do something stupid and get slashed, because I WILL do something stupid eventually.

​

Appreciate any feedback, especially from users.

I'm almost at the finish line with setting up my ETH validator using a DappNode. However, I've hit a major roadblock in the final stage - depositing ETH through MetaMask on the Ethereum Launchpad. Here's what I've tried:

1. Linked my Ledger to MetaMask, but the Ethereum Launchpad won't recognize this wallet.
2. Enabled debug mode on my cold wallet, but still no success.
3. Moved Ethereum from cold wallet to a MetaMask hot wallet, but it didn't solve the issue.
4. The Ethereum Launchpad is showing a MetaMask wallet I don't recognize when trying to deposit.
5. Direct attempts to force a connection with the Ethereum Launchpad site were unsuccessful.

I've done extensive research but haven't found a solution yet. Does anyone in the community have any suggestions or fixes for this situation? I'd really appreciate any help or advice!

https://preview.redd.it/mebbgpurwa5c1.png?width=836&format=png&auto=webp&s=6d5691a04eb4398fd9b66f22e2c553127c850ff8

UPDATE:

Okay, I FINALLY figured it out... Completely deleting Google Chrome and removing all settings and re-installing from a 100% clean slate worked! My guess was that the Ethereum Launchpad was recognizing my Google Chrome cookies from a previous connection.

First let me say I appreciate how helpful this community has generally been.

I have 2 core questions:Is the Holesky testnet deposit contract functionally identical to the mainnet one, except it's contract address and the chain it's on?

​

Now on to my practically taboo request to obtain 32 testnet Eth ether. I am using independently developed software to interface with the blockchain, and am planning to stake real ether on the mainnet so I need to make sure my code is bullet proof and won't fail!

I've already successfully completed a validator deposit using the /cheap-holesky-validator program on the discord, but I have learned it doesn't perfectly mirror interacting with the real deposit contract, though I'm hoping it's almost identical, but before I throw real ether at such a conjecture on the main net I want to fully test it on the testnet.

So you can see to test on the testnet which is its intended function I'm running into a supply issue. Recommendations on ways to obtain or borrow the needed HolEth are appreciated :)

Please be friendly to me and don't flame me for trying to legitimately make use of the test net for testing, thank you :)

My Test Net Address is: 0xb55e5167467CC6d5788Aa13C07fF16e3AFF1c823

Hi guys, I'm wondering about the different ways how one can exit their validator and withdraw the underlying stake. The only way I know is through the Seed Signer UI. Is there other ways to do so?

I want to join a smoothing pool and therefore have to change my withdrawal address to their address. I'm scared that they could somehow exit my validator and run away with my entire stake. Is that even possible without local access to my staking machine? (I don't have an open VPN connection to reach my validator.)

For example is it possible to broadcast an unsigned message on Beaconchain and exit any validator without their keys or access to their machine?

Just my paranoid me that doesn't like to loose control over my money. Thanks for helping🤗

Hello - I am new to ETH and staking. I'm am looking for a way to stake a little bit of ETH safely that would also report yield to the IRS for easy tax filling. Is there a platform that will do that? Should I just use Coinbase?

I wanted to express my gratitude for providing the Rocket Rescue Node!

I read the doc, created the credentials, added it as fallback node to the lighthouse validator client and took the leap of faith. Well actually first i stopped besu + beacon node, saw that the validator was attesting.

Off we go - deleted /var/lib/besu/database folder and its content and restarted besu.

14 hours later and 1 attestation missed, my EL was again synced!

Folder size after re-sync: 764 GB (8th of december)

Add another 50 for the CL and now my machine has again 900 GB free on a 2 TB drive, yay, let that Dencun come, no need to upgrade to 4TB as of yet!

As side node, i had 198 TBW and when all was finished the ssd log showed 204, so i 'burnt' 6 TBW of life of the Samsung 970 evo pro, which has like 1400TBW according to the specs.

If you were thinking about changing EL to a minority client, now you wont even miss out on attestations AND potential block rewards! No more excuses :)

Happy Staking

Hi,

​

I recently setup a ETH node using Geth and Prysm on a debian server.

The node looks to be synced, but when I call blockNumber RPC or getBalance, it return me 0x0 as result.

I don't really understand why, please find attached some logs of prysm and geth :

​

Prysm :

Dec 08 11:06:02 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:02" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0x7026d6b0ded0 headSlot=7933828 prefix=blockchain
Dec 08 11:06:03 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:03" level=info msg="Synced new block" block=0x1e8e0cdc... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933828
Dec 08 11:06:03 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:03" level=info msg="Finished applying state transition" attestations=128 payloadHash=0x7026d6b0ded0 prefix=blockchain slot=7933828 syncBitsCount=506 txCount=144
Dec 08 11:06:12 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:12" level=info msg="Called new payload with optimistic block" payloadBlockHash=0x1f8ab52219a3 prefix=blockchain slot=7933829
Dec 08 11:06:13 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:13" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0x1f8ab52219a3 headSlot=7933829 prefix=blockchain
Dec 08 11:06:14 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:14" level=error msg="Unable to process past deposit contract logs, perhaps your execution client is not fully synced" error="processPastLogs: no contract code at given address" prefix=powchain
Dec 08 11:06:14 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:14" level=info msg="Synced new block" block=0x554dc760... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933829
Dec 08 11:06:14 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:14" level=info msg="Finished applying state transition" attestations=128 payloadHash=0x1f8ab52219a3 prefix=blockchain slot=7933829 syncBitsCount=507 txCount=192
Dec 08 11:06:25 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:25" level=info msg="Called new payload with optimistic block" payloadBlockHash=0x0494557fd573 prefix=blockchain slot=7933830
Dec 08 11:06:26 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:26" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0x0494557fd573 headSlot=7933830 prefix=blockchain
Dec 08 11:06:26 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:26" level=info msg="Synced new block" block=0xd5e9711d... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933830
Dec 08 11:06:26 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:26" level=info msg="Finished applying state transition" attestations=67 payloadHash=0x0494557fd573 prefix=blockchain slot=7933830 syncBitsCount=508 txCount=156
Dec 08 11:06:36 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:36" level=info msg="Peer summary" activePeers=45 inbound=2 outbound=43 prefix=p2p
Dec 08 11:06:38 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:38" level=info msg="Called new payload with optimistic block" payloadBlockHash=0x2673533c5a7e prefix=blockchain slot=7933831
Dec 08 11:06:39 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:39" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0x2673533c5a7e headSlot=7933831 prefix=blockchain
Dec 08 11:06:39 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:39" level=info msg="Synced new block" block=0x7e55f0be... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933831
Dec 08 11:06:39 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:39" level=info msg="Finished applying state transition" attestations=67 payloadHash=0x2673533c5a7e prefix=blockchain slot=7933831 syncBitsCount=507 txCount=153
Dec 08 11:06:48 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:48" level=info msg="Called new payload with optimistic block" payloadBlockHash=0xe372da938e07 prefix=blockchain slot=7933832
Dec 08 11:06:50 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:50" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0xe372da938e07 headSlot=7933832 prefix=blockchain
Dec 08 11:06:50 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:50" level=info msg="Synced new block" block=0xcc322380... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933832
Dec 08 11:06:50 yuripoloalphaone bash[1199697]: time="2023-12-08 11:06:50" level=info msg="Finished applying state transition" attestations=128 payloadHash=0xe372da938e07 prefix=blockchain slot=7933832 syncBitsCount=495 txCount=124
Dec 08 11:07:00 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:00" level=info msg="Called new payload with optimistic block" payloadBlockHash=0x5e4d5d65d352 prefix=blockchain slot=7933833
Dec 08 11:07:00 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:00" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0x5e4d5d65d352 headSlot=7933833 prefix=blockchain
Dec 08 11:07:01 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:01" level=info msg="Synced new block" block=0x0667f4da... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933833
Dec 08 11:07:01 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:01" level=info msg="Finished applying state transition" attestations=84 payloadHash=0x5e4d5d65d352 prefix=blockchain slot=7933833 syncBitsCount=509 txCount=161
Dec 08 11:07:12 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:12" level=info msg="Called new payload with optimistic block" payloadBlockHash=0xa7a232217769 prefix=blockchain slot=7933834
Dec 08 11:07:13 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:13" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0xa7a232217769 headSlot=7933834 prefix=blockchain
Dec 08 11:07:13 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:13" level=info msg="Synced new block" block=0x3b10f260... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933834
Dec 08 11:07:13 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:13" level=info msg="Finished applying state transition" attestations=128 payloadHash=0xa7a232217769 prefix=blockchain slot=7933834 syncBitsCount=509 txCount=268
Dec 08 11:07:26 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:26" level=info msg="Called new payload with optimistic block" payloadBlockHash=0xeca073dc827d prefix=blockchain slot=7933835
Dec 08 11:07:27 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:27" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0xeca073dc827d headSlot=7933835 prefix=blockchain
Dec 08 11:07:27 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:27" level=info msg="Synced new block" block=0x2bfe49e3... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933835
Dec 08 11:07:27 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:27" level=info msg="Finished applying state transition" attestations=128 payloadHash=0xeca073dc827d prefix=blockchain slot=7933835 syncBitsCount=508 txCount=374
Dec 08 11:07:36 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:36" level=info msg="Peer summary" activePeers=47 inbound=2 outbound=44 prefix=p2p
Dec 08 11:07:36 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:36" level=info msg="Called new payload with optimistic block" payloadBlockHash=0xafb4244f7103 prefix=blockchain slot=7933836
Dec 08 11:07:37 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:37" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0xafb4244f7103 headSlot=7933836 prefix=blockchain
Dec 08 11:07:37 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:37" level=info msg="Synced new block" block=0x0172ee58... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933836
Dec 08 11:07:37 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:37" level=info msg="Finished applying state transition" attestations=128 payloadHash=0xafb4244f7103 prefix=blockchain slot=7933836 syncBitsCount=482 txCount=262
Dec 08 11:07:49 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:49" level=info msg="Called new payload with optimistic block" payloadBlockHash=0xee8a29719d10 prefix=blockchain slot=7933837
Dec 08 11:07:50 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:50" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0xee8a29719d10 headSlot=7933837 prefix=blockchain
Dec 08 11:07:50 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:50" level=info msg="Synced new block" block=0xe552ebcc... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933837
Dec 08 11:07:50 yuripoloalphaone bash[1199697]: time="2023-12-08 11:07:50" level=info msg="Finished applying state transition" attestations=68 payloadHash=0xee8a29719d10 prefix=blockchain slot=7933837 syncBitsCount=508 txCount=256
Dec 08 11:08:01 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:01" level=info msg="Called new payload with optimistic block" payloadBlockHash=0x6e466aa4d437 prefix=blockchain slot=7933838
Dec 08 11:08:02 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:02" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0x6e466aa4d437 headSlot=7933838 prefix=blockchain
Dec 08 11:08:02 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:02" level=info msg="Synced new block" block=0xfcba0f9b... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933838
Dec 08 11:08:02 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:02" level=info msg="Finished applying state transition" attestations=128 payloadHash=0x6e466aa4d437 prefix=blockchain slot=7933838 syncBitsCount=507 txCount=219
Dec 08 11:08:13 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:13" level=info msg="Called new payload with optimistic block" payloadBlockHash=0x0c1256cecb41 prefix=blockchain slot=7933839
Dec 08 11:08:15 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:15" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0x0c1256cecb41 headSlot=7933839 prefix=blockchain
Dec 08 11:08:16 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:16" level=info msg="Synced new block" block=0xbb5b7525... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933839
Dec 08 11:08:16 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:16" level=info msg="Finished applying state transition" attestations=128 payloadHash=0x0c1256cecb41 prefix=blockchain slot=7933839 syncBitsCount=503 txCount=172
Dec 08 11:08:24 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:24" level=info msg="Called new payload with optimistic block" payloadBlockHash=0xdb76232f9ae2 prefix=blockchain slot=7933840
Dec 08 11:08:25 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:25" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0xdb76232f9ae2 headSlot=7933840 prefix=blockchain
Dec 08 11:08:26 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:26" level=info msg="Synced new block" block=0x5cc12bbf... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933840
Dec 08 11:08:26 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:26" level=info msg="Finished applying state transition" attestations=128 payloadHash=0xdb76232f9ae2 prefix=blockchain slot=7933840 syncBitsCount=508 txCount=147
Dec 08 11:08:29 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:29" level=error msg="Unable to process past deposit contract logs, perhaps your execution client is not fully synced" error="processPastLogs: no contract code at given address" prefix=powchain
Dec 08 11:08:36 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:36" level=info msg="Peer summary" activePeers=41 inbound=2 outbound=39 prefix=p2p
Dec 08 11:08:36 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:36" level=info msg="Called new payload with optimistic block" payloadBlockHash=0x748a4752bcd5 prefix=blockchain slot=7933841
Dec 08 11:08:37 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:37" level=info msg="Called fork choice updated with optimistic block" finalizedPayloadBlockHash=0x5312b7d2e725 headPayloadBlockHash=0x748a4752bcd5 headSlot=7933841 prefix=blockchain
Dec 08 11:08:37 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:37" level=info msg="Synced new block" block=0xc34ed287... epoch=247932 finalizedEpoch=247930 finalizedRoot=0x3a8c7307... prefix=blockchain slot=7933841
Dec 08 11:08:37 yuripoloalphaone bash[1199697]: time="2023-12-08 11:08:37" level=info msg="Finished applying state transition" attestations=128 payloadHash=0x748a4752bcd5 prefix=blockchain slot=7933841 syncBitsCount=506 txCount=144

​

Geth :

Dec 08 10:59:39 yuripoloalphaone geth[1199587]: INFO [12-08|10:59:39.578] Syncing: state healing in progress       accounts=1527@76.72KiB slots=176@13.82KiB codes=16232@115.32MiB nodes=75,139,002@24.27GiB pending=23901
Dec 08 10:59:41 yuripoloalphaone geth[1199587]: INFO [12-08|10:59:41.810] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,801@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=38.351s
Dec 08 10:59:47 yuripoloalphaone geth[1199587]: INFO [12-08|10:59:47.829] Syncing: state healing in progress       accounts=1566@78.82KiB slots=188@14.76KiB codes=16232@115.32MiB nodes=75,139,191@24.27GiB pending=23954
Dec 08 10:59:49 yuripoloalphaone geth[1199587]: INFO [12-08|10:59:49.814] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,802@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=39.122s
Dec 08 10:59:50 yuripoloalphaone geth[1199587]: INFO [12-08|10:59:50.295] Forkchoice requested sync to new head    number=18,740,802 hash=b1130b..7a6a0e finalized=18,740,733
Dec 08 10:59:56 yuripoloalphaone geth[1199587]: INFO [12-08|10:59:56.373] Syncing: state healing in progress       accounts=1589@79.98KiB slots=198@15.57KiB codes=16232@115.32MiB nodes=75,139,364@24.27GiB pending=24102
Dec 08 10:59:57 yuripoloalphaone geth[1199587]: INFO [12-08|10:59:57.824] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,802@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=39.515s
Dec 08 11:00:02 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:02.028] Forkchoice requested sync to new head    number=18,740,803 hash=399c12..124acf finalized=18,740,733
Dec 08 11:00:04 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:04.508] Syncing: state healing in progress       accounts=1596@80.34KiB slots=216@16.93KiB codes=16232@115.32MiB nodes=75,139,512@24.27GiB pending=24227
Dec 08 11:00:05 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:05.830] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,803@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=40.298s
Dec 08 11:00:12 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:12.913] Syncing: state healing in progress       accounts=1616@81.34KiB slots=250@19.64KiB codes=16232@115.32MiB nodes=75,139,738@24.27GiB pending=24334
Dec 08 11:00:13 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:13.836] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,803@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=41.089s
Dec 08 11:00:13 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:13.964] Forkchoice requested sync to new head    number=18,740,804 hash=ea5db4..843592 finalized=18,740,733
Dec 08 11:00:21 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:21.731] Syncing: state healing in progress       accounts=1626@81.86KiB slots=274@21.55KiB codes=16233@115.35MiB nodes=75,139,909@24.27GiB pending=24424
Dec 08 11:00:21 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:21.846] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,804@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=41.489s
Dec 08 11:00:24 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:24.779] Forkchoice requested sync to new head    number=18,740,805 hash=e531e6..3181de finalized=18,740,733
Dec 08 11:00:29 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:29.852] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,805@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=42.291s
Dec 08 11:00:31 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:31.079] Syncing: state healing in progress       accounts=1654@83.43KiB slots=300@23.70KiB codes=16233@115.35MiB nodes=75,140,103@24.27GiB pending=24536
Dec 08 11:00:37 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:37.842] Forkchoice requested sync to new head    number=18,740,806 hash=be9e1b..31d9ee finalized=18,740,733
Dec 08 11:00:37 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:37.858] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,805@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=43.101s
Dec 08 11:00:40 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:40.489] Syncing: state healing in progress       accounts=1715@86.89KiB slots=328@25.97KiB codes=16233@115.35MiB nodes=75,140,318@24.27GiB pending=24523
Dec 08 11:00:45 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:45.863] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,806@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=43.509s
Dec 08 11:00:48 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:48.905] Syncing: state healing in progress       accounts=1765@89.63KiB slots=349@27.62KiB codes=16233@115.35MiB nodes=75,140,541@24.27GiB pending=24591
Dec 08 11:00:49 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:49.349] Forkchoice requested sync to new head    number=18,740,807 hash=c28d13..f42609 finalized=18,740,733
Dec 08 11:00:53 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:53.870] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,807@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=44.331s
Dec 08 11:00:57 yuripoloalphaone geth[1199587]: INFO [12-08|11:00:57.393] Syncing: state healing in progress       accounts=1813@92.29KiB slots=375@29.74KiB codes=16233@115.35MiB nodes=75,140,769@24.27GiB pending=24697
Dec 08 11:01:00 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:00.624] Forkchoice requested sync to new head    number=18,740,808 hash=5b2334..7155c7 finalized=18,740,733
Dec 08 11:01:01 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:01.876] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,807@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=45.160s
Dec 08 11:01:05 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:05.414] Syncing: state healing in progress       accounts=1875@95.22KiB slots=410@32.64KiB codes=16233@115.35MiB nodes=75,141,010@24.27GiB pending=24643
Dec 08 11:01:09 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:09.879] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,808@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=45.575s
Dec 08 11:01:13 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:13.251] Forkchoice requested sync to new head    number=18,740,809 hash=4a000c..ec4d8b finalized=18,740,733
Dec 08 11:01:15 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:15.926] Syncing: state healing in progress       accounts=1906@96.73KiB slots=467@37.21KiB codes=16233@115.35MiB nodes=75,141,269@24.27GiB pending=24893
Dec 08 11:01:17 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:17.883] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,809@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=46.416s
Dec 08 11:01:24 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:24.648] Syncing: state healing in progress       accounts=1938@98.58KiB slots=500@39.84KiB codes=16233@115.35MiB nodes=75,141,468@24.27GiB pending=25087
Dec 08 11:01:25 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:25.574] Forkchoice requested sync to new head    number=18,740,810 hash=c06c57..9522ec finalized=18,740,733
Dec 08 11:01:25 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:25.889] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,809@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=47.264s
Dec 08 11:01:32 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:32.942] Syncing: state healing in progress       accounts=1989@101.10KiB slots=570@45.79KiB codes=16233@115.35MiB nodes=75,141,716@24.27GiB pending=25120
Dec 08 11:01:33 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:33.894] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,810@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=47.687s
Dec 08 11:01:37 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:37.313] Forkchoice requested sync to new head    number=18,740,811 hash=a183bc..5db85d finalized=18,740,733
Dec 08 11:01:41 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:41.899] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,811@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=48.547s
Dec 08 11:01:42 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:42.005] Syncing: state healing in progress       accounts=2024@103.10KiB slots=667@53.67KiB codes=16233@115.35MiB nodes=75,142,002@24.27GiB pending=25035
Dec 08 11:01:49 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:49.903] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,811@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=48.974s
Dec 08 11:01:50 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:50.796] Forkchoice requested sync to new head    number=18,740,812 hash=18bff1..f6790e finalized=18,740,733
Dec 08 11:01:52 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:52.005] Syncing: state healing in progress       accounts=2047@104.28KiB slots=724@58.35KiB codes=16233@115.35MiB nodes=75,142,251@24.27GiB pending=25190
Dec 08 11:01:57 yuripoloalphaone geth[1199587]: INFO [12-08|11:01:57.908] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,812@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=49.845s
Dec 08 11:02:01 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:01.706] Syncing: state healing in progress       accounts=2072@105.45KiB slots=790@63.80KiB codes=16233@115.35MiB nodes=75,142,528@24.27GiB pending=25290
Dec 08 11:02:02 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:02.780] Forkchoice requested sync to new head    number=18,740,813 hash=65b41c..e3bd4c finalized=18,740,733
Dec 08 11:02:05 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:05.913] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,813@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=50.725s
Dec 08 11:02:11 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:11.627] Syncing: state healing in progress       accounts=2089@106.30KiB slots=856@69.19KiB codes=16233@115.35MiB nodes=75,142,794@24.27GiB pending=25423
Dec 08 11:02:13 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:13.331] Forkchoice requested sync to new head    number=18,740,814 hash=995ae8..37f7a3 finalized=18,740,733
Dec 08 11:02:13 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:13.919] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,813@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=51.612s
Dec 08 11:02:20 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:20.292] Syncing: state healing in progress       accounts=2089@106.30KiB slots=881@71.34KiB codes=16233@115.35MiB nodes=75,142,952@24.27GiB pending=25628
Dec 08 11:02:21 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:21.923] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,814@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=52.050s
Dec 08 11:02:25 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:25.643] Forkchoice requested sync to new head    number=18,740,815 hash=0022b6..9f0cfa finalized=18,740,733
Dec 08 11:02:29 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:29.929] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,815@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=52.948s
Dec 08 11:02:32 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:32.123] Syncing: state healing in progress       accounts=2094@106.53KiB slots=908@73.50KiB codes=16233@115.35MiB nodes=75,143,174@24.27GiB pending=26071
Dec 08 11:02:33 yuripoloalphaone geth[1199587]: WARN [12-08|11:02:33.937] Snapshot extension registration failed   peer=8faf3e54 err="peer connected on snap without compatible eth support"
Dec 08 11:02:36 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:36.840] Forkchoice requested sync to new head    number=18,740,816 hash=6f25d9..2f589c finalized=18,740,733
Dec 08 11:02:37 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:37.934] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,815@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=53.855s
Dec 08 11:02:41 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:41.231] Syncing: state healing in progress       accounts=2135@108.63KiB slots=959@77.64KiB codes=16233@115.35MiB nodes=75,143,421@24.27GiB pending=26126
Dec 08 11:02:45 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:45.939] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,816@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=54.300s
Dec 08 11:02:49 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:49.607] Syncing: state healing in progress       accounts=2198@111.61KiB slots=1012@81.97KiB codes=16233@115.35MiB nodes=75,143,686@24.27GiB pending=26083
Dec 08 11:02:49 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:49.831] Forkchoice requested sync to new head    number=18,740,817 hash=951907..1d7dd3 finalized=18,740,733
Dec 08 11:02:53 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:53.943] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,817@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=55.218s
Dec 08 11:02:57 yuripoloalphaone geth[1199587]: INFO [12-08|11:02:57.632] Syncing: state healing in progress       accounts=2234@113.50KiB slots=1135@92.12KiB codes=16233@115.35MiB nodes=75,144,003@24.27GiB pending=26037
Dec 08 11:03:01 yuripoloalphaone geth[1199587]: INFO [12-08|11:03:01.947] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,817@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=56.143s
Dec 08 11:03:02 yuripoloalphaone geth[1199587]: INFO [12-08|11:03:02.597] Forkchoice requested sync to new head    number=18,740,818 hash=6e7c0e..98e9dd finalized=18,740,733
Dec 08 11:03:06 yuripoloalphaone geth[1199587]: INFO [12-08|11:03:06.103] Syncing: state healing in progress       accounts=2245@113.97KiB slots=1248@101.25KiB codes=16233@115.35MiB nodes=75,144,285@24.27GiB pending=26007
Dec 08 11:03:09 yuripoloalphaone geth[1199587]: INFO [12-08|11:03:09.953] Syncing: chain download in progress      synced=100.00% chain=367.43GiB headers=18,740,818@6.96GiB bodies=18,740,700@243.76GiB receipts=18,740,700@116.70GiB eta=56.597s
Dec 08 11:03:13 yuripoloalphaone geth[1199587]: INFO [12-08|11:03:13.150] Forkchoice requested sync to new head    number=18,740,819 hash=b5877c..3ddc53 finalized=18,740,733
Dec 08 11:03:14 yuripoloalphaone geth[1199587]: INFO [12-08|11:03:14.725] Syncing: state healing in progress       accounts=2263@114.82KiB slots=1426@115.91KiB codes=16233@115.35MiB nodes=75,144,668@24.27GiB pending=25867

​

And the syncing RPC result :

{
   "jsonrpc":"2.0",
   "id":1,
   "result":{
      "currentBlock":"0x11df6b9",
      "healedBytecodeBytes":"0x7375da3",
      "healedBytecodes":"0x3f7c",
      "healedTrienodeBytes":"0x6124bd689",
      "healedTrienodes":"0x47b3897",
      "healingBytecode":"0x0",
      "healingTrienodes":"0x454",
      "highestBlock":"0x11df72e",
      "startingBlock":"0x11dedb8",
      "syncedAccountBytes":"0xcffc64156",
      "syncedAccounts":"0x1115baac",
      "syncedBytecodeBytes":"0x1c3607e8b",
      "syncedBytecodes":"0x10a260",
      "syncedStorage":"0x43f6267e",
      "syncedStorageBytes":"0x3922c34475"
   }
}

​

Someone of you have an idea of what can happened ?

​

Thank you,

What gives? Distance was zero, everything seems fine. I didn't know this was possible

once I've generated keystores, is there a way to verify the withdrawal address is correct before going live ?

​

My friend has the Blox staking app on his computer and this is the guide that has been posted several times on the Blox discord:

https://docs.google.com/document/d/1mHGnbjuYIcaxtrpEsRKpy6vQvvqcvC6GYaRDas1lfrA/edit

I need help, I'm trying to setup a test validator on the holesky test net before doing anything live. I've setup Ubuntu, created my validator keys, and now I have the deposit.json file and the keystore file.

I went to /cheap-holesky-deposit whose withdrawl address was used when creating the keys. It wants me to give it a signature URL, but I don't know what that is. So I tried going to the holesky launchpad and gave it the desposit file but it wants link to metamask, why does it want that? Is that someway to sign the correct transaction and just broadcast it into the network. For my real live setup later there is no way the private keys are hitting an internet connected computer in any format, but I have an airgapped system that can be used to create transactions and the like.

I have gone through the vaults on the StakeWise V3 vault page and found the vaults that appear to be the best for the Ethereum Network health. Comments welcome.

https://preview.redd.it/p9h6ybsfzv4c1.jpg?width=1061&format=pjpg&auto=webp&s=ddd00d803d41fa3fb1810a08822884b0eeb8f355

it's my first time to use reddit and geth so forgive me if i make sth wrong.

I try to connect geth and lighthouse but it not works

it seems like it's lighthouse's false but i cant solve it

===snippit geth===

WARN [12-07|17:38:25.958] Beacon client online, but never received consensus updates. Please ensure your beacon client is operational to follow the chain!

===snippit lighthouse===

Dec 07 09:41:05.008 INFO Ready for Capella info: ensure the execution endpoint is updated to the latest Capella/Shanghai release, service: slot_notifier

Dec 07 09:41:17.001 INFO Syncing est_time: 4 days 10 hrs, speed: 20.45 slots/sec, distance: 7867720 slots (156 weeks 0 days), peers: 5, service: slot_notifier

Dec 07 09:41:17.002 WARN Not ready for merge info: The execution endpoint is connected and configured, however it is not yet synced, service: slot_notifier

Dec 07 09:41:17.003 INFO Ready for Capella info: ensure the execution endpoint is updated to the latest Capella/Shanghai release, service: slot_notifier

​

i just want to build a connection between some local device so i don't need to load all block.

now i just want to connect to consensus client and communicate in a computer. how can i do it?

Is there a website that shows real time how often one node should theoretically be getting a block reward?

Also, has anyone done the math on how many nodes it would take not consider the new dappnode smoothing pool?

I staked an eth node via Allnodes a couple of years ago and recently had to designate an address to receive partial withdrawals from withdrawal credentials 0x00 to 0x01. To do so, I followed the instructions cited here: https://help.allnodes.com/en/articles/7235575-how-to-change-your-ethereum-withdrawal-credentials-from-0x00-to-0x01-deposit-cli

On Step #11, I had to enter my seed phrase (cold wallet). I used an airgap computer to enter the seed phrase, creating the JSON file and copying the JSON file over to the active computer via USB stick (as per the instructions).

Being highly neurotic, I've been stressing about this since the best safekeeping is to never enter your seed phrase on any electronic device. Without fully understanding how this all works and assuming I've followed instructions, is my seed phrase safe?

Would it be best if I get another wallet and move all other funds out of this wallet?

It is:

1. non custodial
2. not requiring hardware (for stakers)
3. somewhat useful in supporting minority clients.
4. tax friendly. I believe staking won't be a taxable event because the act of staking does not cause a token conversion.

Some of the vaults use SSV which also is pretty cool. And the documentation is great and the Discord is friendly and helpful.

The only thing missing is a way to calculate the rewards for tax purposes but that is being worked on.

Good work, StakeWise people! 🤗

If you use ledger wallet to stake and the government tries to attack rocket or lido, can you be prevented from unstaking? Or can you use the keys you have to unstake regardless?

Also if you self stake with your own hardware is that effectively a hot wallet?

Heya,

I'm wondering if anyone knows why my erigon archive node might be taking so long to sync, it's running in docker with 32gb ram, 3900x and WD_BLACK 4TB SN850X NVMe for data. It's been going for 6 days, and is making progress, but very slowly :( sorry for potato's, that pc is not connected easily!

https://imgur.com/a/6yJY75C

I am getting about 20 "late block imports" per hour in the Teku logs. Is this normal, or should I hold off on starting the validator up? It isn't consistently the Nethermind execution; sometimes arrival is too slow. I have updated my chrony settings to use google instead of ubuntu (currently testing).

tail -10000 /data/var/lib/teku/logs/teku.log | grep -i 'late block import' | grep -i "2023-12-05 07" | wc -l

Most of the delay is with the:

• arrival: 600ms to 3500ms
• execution_payload_result_received: 2000ms - 8000ms

Typical warning:

2023-12-04 01:23:18.543-05:00 | forkchoice-async-0 | WARN | teku-event-log | mLate Block Import *** Block: 9060335021c18bfecab954523832a57dac6662b4a50b9393136308c89ef89817 (7903914) proposer 644106

• arrival 2723ms
• gossip_validation +2ms
• pre-state_retrieved +7ms
• processed +240ms
• execution_payload_result_received +4555ms
• begin_importing +0ms
• transaction_prepared +1ms
• transaction_committed +0ms
• completed +15ms

Automated script to see hourly "late block imports". I'd be interested in what others are seeing, running Teku.

​

FULLDATE=`date +"%Y-%m-%d"`
echo $FULLDATE
for HOUR in 01 02 03 04 05 06 07 08 09 10 11 12 13 14 15 16 17 18 19 20 21 22 23 00
do
  echo -n $FULLDATE $HOUR ": "
  tail -10000 /data/var/lib/teku/logs/teku.log | grep -i 'late block import' | grep -i "$FULLDATE $HOUR" | wc -l
done

​