Difference between revisions of "Geth --syncmode light"
Jump to navigation
Jump to search
(Created page with " What is wrong with my light client? Light sync relies on full nodes that serve data to light clients. Historically, this has been hampered by the fact that serving light c...") |
|||
| Line 1: | Line 1: | ||
| + | {{lc}} | ||
| + | [[geth --syncmode]] light | ||
| + | |||
What is wrong with my light client? | What is wrong with my light client? | ||
Light sync relies on full nodes that serve data to light clients. Historically, this has been hampered by the fact that | Light sync relies on full nodes that serve data to light clients. Historically, this has been hampered by the fact that | ||
Revision as of 12:57, 14 March 2023
geth --syncmode light
What is wrong with my light client? Light sync relies on full nodes that serve data to light clients. Historically, this has been hampered by the fact that serving light clients was turned off by default in geth full nodes and few nodes chose to turn it on. Therefore, light nodes often struggled to find peers. Since Ethereum switched to proof-of-stake, Geth light clients have stopped working altogether. Light clients for proof-of-stake Ethereum are expected to be implemented soon!
geth [ account | console | snapshot | --authrpc.addr | version | --sepolia | --goerli | --pprof | --http | --syncmode | --mine ] --rpc.evmtimeout | --ethstats | --help, Geth logs, geth logs WARN, Log.Error, ports: 8551, 30303, 8547, ~/.ethereum/geth/, , --verbosity, --config, geth initdevp2p, p2psim, devp2p, geth dumpconfig
Advertising:
