# msf3 manual sync tests All nodes were started on fresh machines, they were all synced till the head of the chain. ~2H before TTD the respective EL/CL was paused with `docker pause ...`. Once TTD was hit (but before finality post TTD), the container was un-paused with `docker unpause ...`. ## Nodes: - mainnet-shadow-fork-3-pause-test-prysm-geth-1: Stop EL - mainnet-shadow-fork-3-pause-test-lighthouse-geth-1: Stop CL - mainnet-shadow-fork-3-pause-test-prysm-nethermind-1: Stop CL - mainnet-shadow-fork-3-pause-test-lighthouse-nethermind-1: Stop EL ## Results: ### mainnet-shadow-fork-3-pause-test-prysm-geth-1: Stop EL Access: `ssh [email protected]` Failed to catch up to head post unpause. Prysm logs: ``` time="2022-05-05 13:53:13" level=debug msg="Block is not processed" error="beacon node doesn't have a parent in db with root: (in processBlock, slot=41529) 0xa272b8e15d81fc4105e9a6cd7810d63307b36a2637913ff5a0ba5c33ee0d1d9a" prefix=initial-sync ``` Geth logs: ``` INFO [05-05|13:54:01.417] Legacy sync reached merge threshold number=14,716,821 hash=71ec49..8da10d td=48,144,739,311,386,193,556,332 ttd=48,144,711,970,238,236,721,152 INFO [05-05|13:54:01.417] State heal in progress accounts=247,[email protected] slots=469,[email protected] [email protected] nodes=3,813,[email protected] pending=17 WARN [05-05|13:54:01.417] Local chain is post-merge, waiting for beacon client sync switch-over... WARN [05-05|13:54:01.452] Unexpected trienode heal packet peer=8c987cc3 reqid=3,557,761,924,799,430,402 DEBUG[05-05|13:54:02.872] Served eth_getBlockByNumber conn=5.34.180.243:41512 reqid=1 duration="148.096µs" INFO [05-05|13:54:03.127] Disabling direct-ancient mode origin=14,716,820 ancient=14,626,820 INFO [05-05|13:54:03.502] Legacy sync reached merge threshold number=14,716,821 hash=71ec49..8da10d td=48,144,739,311,386,193,556,332 ttd=48,144,711,970,238,236,721,152 INFO [05-05|13:54:03.502] State heal in progress accounts=247,[email protected] slots=469,[email protected] [email protected] nodes=3,813,[email protected] pending=17 WARN [05-05|13:54:03.542] Unexpected trienode heal packet peer=8c987cc3 reqid=7,389,355,313,485,979,547 WARN [05-05|13:54:03.742] Failed to retrieve stats server message err="websocket: close 1006 (abnormal closure): unexpected EOF" WARN [05-05|13:54:04.245] Transaction stats report failed err="use of closed network connection" WARN [05-05|13:54:05.320] Stats server unreachable err="dial tcp 164.92.169.47:80: connect: connection refused" INFO [05-05|13:54:07.974] Disabling direct-ancient mode origin=14,716,820 ancient=14,626,820 INFO [05-05|13:54:08.422] Legacy sync reached merge threshold number=14,716,821 hash=71ec49..8da10d td=48,144,739,311,386,193,556,332 ttd=48,144,711,970,238,236,721,152 INFO [05-05|13:54:08.423] State heal in progress accounts=247,[email protected] slots=469,[email protected] [email protected] nodes=3,813,[email protected] pending=17 WARN [05-05|13:54:08.555] Unexpected trienode heal packet peer=ca53cbf1 reqid=1,547,625,417,515,909,221 ``` ### mainnet-shadow-fork-3-pause-test-lighthouse-geth-1: Stop CL Access: `ssh [email protected]` CL refuses to advance head state. Lighthouse logs: ``` May 05 13:56:06.001 DEBG Eth1 cache sync status ready: true, voting_target_timestamp: 1651718348, latest_cached_timestamp: 1651726797, latest_cached_block_number: 14715284, eth1_head_block: 14716820, service: slot_notifier May 05 13:56:08.001 DEBG Proposer prepare routine firing service: beacon May 05 13:56:08.077 DEBG Committee cache miss head_block_root: 0x6e74…18d7, shuffling_id: Epoch(1311), service: beacon May 05 13:56:09.001 DEBG Refused to advance head state current_slot: 41955, head_slot: 41685, service: state_advance ``` Geth logs: ``` INFO [05-05|13:57:00.137] Legacy sync reached merge threshold number=14,716,821 hash=71ec49..8da10d td=48,144,739,311,386,193,556,332 ttd=48,144,711,970,238,236,721,152 INFO [05-05|13:57:00.362] State heal in progress accounts=259,[email protected] slots=468,[email protected] [email protected] nodes=3,878,[email protected] pending=4369 WARN [05-05|13:57:00.362] Local chain is post-merge, waiting for beacon client sync switch-over... ``` ### mainnet-shadow-fork-3-pause-test-prysm-nethermind-1: Stop CL Access: `ssh [email protected]` Synced to head ### mainnet-shadow-fork-3-pause-test-lighthouse-nethermind-1 Access: `ssh [email protected]` Synced to head
Last changed by  
 
[email protected]
4268

Read more

《XX小学一年级“萌宝成长手册”》

(2025年秋季学期·行为规范月) 班级： ________________姓名： ________________我的照片： (可粘贴一张一寸照片) 致亲爱的宝贝和家长 亲爱的宝贝： 欢迎你正式加入XX小学这个温暖的大家庭！从今天起，你就是一名光荣的小学生啦！这本《萌宝成长手册》将陪伴你度过最初的美好时光，记录下你点点滴滴的进步。收集小星星，兑换大成长，让我们一起加油吧！ 尊敬的家长： 您好！习惯的养成始于点滴，成于坚持。我们诚挚地邀请您成为孩子成长路上最重要的见证者和合伙人。请您每日抽出几分钟时间，与孩子一同回顾在校表现，并给予真诚的鼓励。家校协同，共育未来！

9/16/2025
Mekong deprecation Announcement

The Mekong devnet was meant to be a playground for wallet developers to experiment with UX changes and for stakers to gain confidence in the upcoming Pectra changes. The Pectra network upgrade has been activated on the Ethereum Sepolia and Holesky testnets. These networks can now be used to test the Pectra upgrade features. In light of this, we'd like to announce the deprecation of the Mekong testnet on 7th March, 2025. Application and tooling developers are encouraged to use Sepolia to test applications, smart contracts, and other EVM functionality. Its permissioned validator set provides a stable test environment. Alternatively, many local development environments allow for testing against copies of the Ethereum mainnet state. Stakers and infrastructure providers concerned with protocol-level testing are encouraged to wait for the Holesky testnet to finalize, or to await an announcement on the Ethereum R&D discord for an alternate testing location. For validator setup testing, stakers should also consider the Ephemery testnet. This network resets weekly and enables lightweight end-to-end testing of the validator lifecycle.

3/6/2025
How to create a shadowfork

Introduction: shadowfork Theory: General info: A chain consists of an Execution layer(EL) and a Consensus layer(CL) The EL is responsible for state (transactions, history, etc) and the CL is responsible for consensus (agreement on chain head) at a high level The EL is driven by the CL. i.e, The CL decides what the head of the chain is and the EL must accept that decision (mostly) The CL asks the EL to produce blocks, these blocks are placed in the EL chain as well as execution_payloads in the CL slot. This links the CL slot to the EL chain (leaving out caveats here) When the CL sends the request to produce a block, it also sends information about the block to build on top of

3/5/2025
Verkle transition

Considerations Resource use: CPU, Disk, Cost, I/O Syncing and Sync complexity increase Complexity of Implimentation and Testing Time for conversion to take place Ideological Methods Overview

1/18/2024
Read more from [email protected]
Published on HackMD