Nils-Erik Frantzell
Nils-Erik Frantzell
ETC bootnodes for testing: https://github.com/multi-geth/multi-geth/blob/864e5788786f198ef4d64d151766d10bab13a82d/params/bootnodes_classic.go#L20-L39
@wifi-ctrl None of the hard forks require a resync from genesis. Requiring a resync from genesis means that you’re on an entirely new chain.
This ultimately looks like a peering issue - if Aleth had at least 2 peers which are on the canonical longest Ropsten chain, it would go through a chain reorg...
Hitting this again when syncing Aleth (built from source, head = c47760657321d216c74bc9d5849a2857da29d7e1) from genesis on Ropsten.
@chfast : > w `--private` does not imply `--no-dicovery`, so discovery should be on. Just build the recent version. `--private` still appears to imply `--no-discovery`: https://github.com/ethereum/aleth/blob/ae042a32103e4c421f942952bd42afdbd1e6b96f/aleth/main.cpp#L758 I think that private...
I think this is a great idea