15 Commits (289c6c3b157a5bf7111a667bc0d760bd1a6911a6)

Author	SHA1	Message	Date
Péter Szilágyi	1e556d220c	all: remove notion of trusted checkpoints in the post-merge world (#27147) ... * all: remove notion of trusted checkpoints in the post-merge world * light: remove unused function * eth/ethconfig, les: remove unused config option * les: make linter happy --------- Co-authored-by: Gary Rong <garyrong0905@gmail.com>	2 years ago
Péter Szilágyi	9e17648d8c	les: duplicate downloader and fetcher to allow progressive refactoring	3 years ago
gary rong	45cb1a580a	eth, les: add new config field SyncFromCheckpoint (#22123) ... This PR introduces a new config field SyncFromCheckpoint for light client. In some special scenarios, it's required to start synchronization from some arbitrary checkpoint or even from the scratch. So this PR offers this flexibility to users so that the synchronization start point can be configured. There are two relevant configs: SyncFromCheckpoint and Checkpoint. - If the SyncFromCheckpoint is true, the light client will try to sync from the specified checkpoint. - If the Checkpoint is not configured, then the light client will sync from the scratch(from the latest header if the database is not empty) Additional notes: these two configs are not visible in the CLI flags but only accessable in the config file. Example Usage: [Eth] SyncFromCheckpoint = true [Eth.Checkpoint] SectionIndex = 100 SectionHead = "0xabc" CHTRoot = "0xabc" BloomRoot = "0xabc" PS. Historical checkpoint can be retrieved from the synced full node or light client via les_getCheckpoint API.	4 years ago
gary rong	9f6bb492bb	les, light: remove untrusted header retrieval in ODR (#21907) ... * les, light: remove untrusted header retrieval in ODR * les: polish * light: check the hash equality in odr	4 years ago
gary rong	4fabd9cbd2	les: separate peer into clientPeer and serverPeer (#19991) ... * les: separate peer into clientPeer and serverPeer * les: address comments	5 years ago
gary rong	c6285e6437	les/checkpointoracle: move oracle into its own package (#20508) ... * les: move the checkpoint oracle into its own package It's first step of refactor LES package. LES package basically can be divided into LES client and LES server. However both sides will use checkpoint package for status retrieval and verification. So this PR moves checkpoint oracle into a separate package * les: address comments	5 years ago
gary rong	32b07e8b1f	les: fix checkpoint sync (#20120)	5 years ago
gary rong	2ed729d38e	les: handler separation (#19639) ... les: handler separation	5 years ago
gary rong	f7cdea2bdc	all: on-chain oracle checkpoint syncing (#19543) ... * all: implement simple checkpoint syncing cmd, les, node: remove callback mechanism cmd, node: remove callback definition les: simplify the registrar les: expose checkpoint rpc services in the light client les, light: don't store untrusted receipt cmd, contracts, les: discard stale checkpoint cmd, contracts/registrar: loose restriction of registeration cmd, contracts: add replay-protection all: off-chain multi-signature contract params: deploy checkpoint contract for rinkeby cmd/registrar: add raw signing mode for registrar cmd/registrar, contracts/registrar, les: fixed messages * cmd/registrar, contracts/registrar: fix lints * accounts/abi/bind, les: address comments * cmd, contracts, les, light, params: minor checkpoint sync cleanups * cmd, eth, les, light: move checkpoint config to config file * cmd, eth, les, params: address comments * eth, les, params: address comments * cmd: polish up the checkpoint admin CLI * cmd, contracts, params: deploy new version contract * cmd/checkpoint-admin: add another flag for clef mode signing * cmd, contracts, les: rename and regen checkpoint oracle with abigen	5 years ago
Péter Szilágyi	6cf0ab38bd	core/rawdb: separate raw database access to own package (#16666)	7 years ago
thomasmodeneis	ba1030b6b8	build: enable goimports and varcheck linters (#16446)	7 years ago
Felix Lange	c213fd1fd8	all: import "context" instead of "golang.org/x/net/context" ... There is no need to depend on the old context package now that the minimum Go version is 1.7. The move to "context" eliminates our weird vendoring setup. Some vendored code still uses golang.org/x/net/context and it is now vendored in the normal way. This change triggered new vet checks around context.WithTimeout which didn't fire with golang.org/x/net/context.	8 years ago
Felix Lange	35a7dcb162	all: gofmt -w -s	8 years ago
Felix Lange	b8bd9a71c8	all: update license information	8 years ago
Zsolt Felfoldi	9f8d192991	les: light client protocol and API	8 years ago