From 0eeb9c089433bea8fbe6ae7b3aa83e36c679306b Mon Sep 17 00:00:00 2001 From: Sina M <1591639+s1na@users.noreply.github.com> Date: Tue, 25 Jun 2024 12:16:06 +0200 Subject: [PATCH 1/3] Update docs/fundamentals/blsync.md Co-authored-by: Marius van der Wijden --- docs/fundamentals/blsync.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/fundamentals/blsync.md b/docs/fundamentals/blsync.md index 2a2176f0c2..c8641175a9 100644 --- a/docs/fundamentals/blsync.md +++ b/docs/fundamentals/blsync.md @@ -56,7 +56,7 @@ Blsync takes the same flags as above to configure the HTTP endpoint as well as c Again to sync the Sepolia network in this mode, first run Geth: ```terminal -❯ ./build/bin/geth --sepolia --datadir light-sepolia-dir +./build/bin/geth --sepolia --datadir light-sepolia-dir ``` The logs will indicate the Engine API path which is by default `http://localhost:8551` and the path to the JWT secret created which is in this instance `./light-sepolia-dir/geth/jwtsecret`. Now blsync can be run: From 46544fe1fee0bda03f04e2cafd65dea031be7a2d Mon Sep 17 00:00:00 2001 From: Sina M <1591639+s1na@users.noreply.github.com> Date: Tue, 25 Jun 2024 12:16:21 +0200 Subject: [PATCH 2/3] Update docs/fundamentals/blsync.md Co-authored-by: Marius van der Wijden --- docs/fundamentals/blsync.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/fundamentals/blsync.md b/docs/fundamentals/blsync.md index c8641175a9..090359a58d 100644 --- a/docs/fundamentals/blsync.md +++ b/docs/fundamentals/blsync.md @@ -3,7 +3,7 @@ title: Beacon light client description: Running geth with integrated beacon light client --- -`blsync` is a beacon light client shipped by Geth, designed to synchronize with the beacon chain without the need for a [consensus client](/docs/getting-started/consensus-clients). Integrated within Geth, blsync eliminates the necessity of running a separate consensus client, making it ideal for most use-cases that do not require full validation capabilities. It comes with very low resource requirements and can sync the beacon chain within seconds. `blsync` can be run in two modes: integrated or standalone. In standalone mode it is possible to use it for driving other execution clients. +`blsync` is a beacon light client shipped by Geth, designed to synchronize with the beacon chain without the need for a [consensus client](/docs/getting-started/consensus-clients). Integrated within Geth, blsync eliminates the necessity of running a separate consensus client, making it ideal for use-cases that do not require full validation capabilities. It comes with very low resource requirements and can sync the beacon chain within seconds. `blsync` can be run in two modes: integrated or standalone. In standalone mode it is possible to use it for driving other execution clients. Important: blsync is not suitable for running a validator. It is also not recommended for nodes handling any amount of money or used in production settings due to its lower security guarantees compared to running a full consensus client. From 1e091a6643f7b5b7b9db604f607325684a06a776 Mon Sep 17 00:00:00 2001 From: Felix Lange Date: Tue, 25 Jun 2024 14:22:33 +0200 Subject: [PATCH 3/3] Update blsync.md --- docs/fundamentals/blsync.md | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/docs/fundamentals/blsync.md b/docs/fundamentals/blsync.md index 090359a58d..796432f71d 100644 --- a/docs/fundamentals/blsync.md +++ b/docs/fundamentals/blsync.md @@ -3,7 +3,7 @@ title: Beacon light client description: Running geth with integrated beacon light client --- -`blsync` is a beacon light client shipped by Geth, designed to synchronize with the beacon chain without the need for a [consensus client](/docs/getting-started/consensus-clients). Integrated within Geth, blsync eliminates the necessity of running a separate consensus client, making it ideal for use-cases that do not require full validation capabilities. It comes with very low resource requirements and can sync the beacon chain within seconds. `blsync` can be run in two modes: integrated or standalone. In standalone mode it is possible to use it for driving other execution clients. +`blsync` is a beacon chain light client. Integrated within Geth, blsync eliminates the necessity of running a separate [consensus client](/docs/getting-started/consensus-clients), making it ideal for use-cases that do not require full validation capabilities. It comes with very low resource requirements and can sync the beacon chain within seconds. `blsync` can be run in two modes: integrated or standalone. In standalone mode it is possible to use it for driving other execution clients. Important: blsync is not suitable for running a validator. It is also not recommended for nodes handling any amount of money or used in production settings due to its lower security guarantees compared to running a full consensus client. @@ -68,8 +68,3 @@ INFO [06-23|15:06:33.388] Loaded JWT secret file path=light-se INFO [06-23|15:06:34.130] Successful NewPayload number=6,169,314 hash=d4204e..772e65 status=SYNCING INFO [06-23|15:06:34.130] Successful ForkchoiceUpdated head=d4204e..772e65 status=SYNCING ``` - -## Summary - -This guide should provide the steps of using blsync in both integrated and standalone modes with Geth as an alternative to running a full consensus client. This is suitable for non-production use-cases and offers lower resource requirements and higher speed. The steps to run blsync include choosing an endpoint, obtaining a checkpoint, and starting the client with correct flags. -