2018-11-23 23:58:49 +00:00
|
|
|
import
|
2019-11-21 09:15:10 +00:00
|
|
|
os, chronos, json_serialization,
|
2019-10-25 10:59:56 +00:00
|
|
|
spec/[datatypes], beacon_chain_db
|
2018-11-29 01:08:34 +00:00
|
|
|
|
|
|
|
|
const
|
2019-03-22 15:49:37 +00:00
|
|
|
WEAK_SUBJECTVITY_PERIOD* =
|
|
|
|
|
Slot(uint64(4 * 30 * 24 * 60 * 60) div SECONDS_PER_SLOT)
|
2018-11-29 01:08:34 +00:00
|
|
|
# TODO: This needs revisiting.
|
|
|
|
|
# Why was the validator WITHDRAWAL_PERIOD altered in the spec?
|
2018-11-23 23:58:49 +00:00
|
|
|
|
|
|
|
|
proc obtainTrustedStateSnapshot*(db: BeaconChainDB): Future[BeaconState] {.async.} =
|
|
|
|
|
# In case our latest state is too old, we must obtain a recent snapshot
|
|
|
|
|
# of the state from a trusted location. This is explained in detail here:
|
|
|
|
|
# https://notes.ethereum.org/oaQV3IF5R2qlJuW-V1r1ew#Beacon-chain-sync
|
|
|
|
|
|
|
|
|
|
# TODO: implement this:
|
|
|
|
|
#
|
|
|
|
|
# 1. Specify a large set of trusted state signees
|
|
|
|
|
# (perhaps stored in a config file)
|
|
|
|
|
#
|
|
|
|
|
# 2. Download a signed state hash from a known location
|
|
|
|
|
# (The known location can be either a HTTPS host or a DHT record)
|
|
|
|
|
#
|
|
|
|
|
# 3. Check that enough of the specified required signatures are present
|
|
|
|
|
#
|
|
|
|
|
# 4. Download a snapshot file from a known location
|
|
|
|
|
# (or just obtain it from the network using the ETH protocols)
|
|
|
|
|
#
|
|
|
|
|
# 5. Check that the state snapshot hash is correct and save it in the DB.
|
|
|
|
|
|
2019-03-22 15:49:37 +00:00
|
|
|
# TODO or just pass a state root via command line?
|
|
|
|
|
|
2019-03-13 23:04:43 +00:00
|
|
|
doAssert(false, "Not implemented")
|
2018-11-23 23:58:49 +00:00
|
|
|
|
