You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/cli/networks.md
+21-21Lines changed: 21 additions & 21 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -23,32 +23,32 @@ To experiment with the Beacon Light Client Network, do the following:
23
23
- Observe the logs. If all goes well, you should see something like below eventually, which indicates that the embedded Lodestar light client has begun tracking the head of the chain and will continue to do so as long as new updates are piped in.
24
24
25
25
```sh
26
-
13527:Portal:BeaconLightClientNetwork:LightClientTransport Found LightClientBootstrap locally. Initializing light client... +0ms
13527:Portal:Beacon:LightClient:DEBUG Started tracking the head +1ms
45
45
ultralight Received portal_beaconStore with params: 0: 0x03f67e760000000000,1: 0xbba4da96ac000000ffffffffffff7fffffffffffffffffffffffffffffffff... +14s
46
-
13527:Portal:BeaconLightClientNetwork storing LightClientOptimisticUpdate content corresponding to 0x03f67e760000000000 +14s
ultralight Received portal_beaconStore with params: 0: 0x02a07e760000000000,1: 0xbba4da9670010000ad040000f5b30300000000000000000000000000000000... +429ms
50
-
13527:Portal:BeaconLightClientNetwork storing LightClientFinalityUpdate content corresponding to 0x02a07e760000000000 +428ms
You can also call the RPC methods `beacon_getHead` and `beacon_getFinalized` to get the latest Light Client Headers for`latest` and `finalized` blocks known to the light client.
0 commit comments