9 Commits (faa54e59c1c276d153299c73afdea246941ec952)

Author	SHA1	Message	Date
obscuren	1337a8dfb1	upped pv	10 years ago
zelig	5a9952c7b4	major blockpool change ... - the spec says response to getBlockHashes(from, max) should return all hashes starting from PARENT of from. This required major changes and results in much hackier code. - Introduced a first round block request after peer introduces with current head, so that hashes can be linked to the head - peerInfo records currentBlockHash, currentBlock, parentHash and headSection - AddBlockHashes checks header section and creates the top node from the peerInfo of the best peer - AddBlock checks peerInfo and updates the block there rather than in a node - request further hashes once a section is created but then no more until the root block is found (so that we know when to stop asking) - in processSection, when root node is checked and receives a block, we need to check if the section has a parent known to blockchain or blockPool - when peers are switched, new peer launches a new requestHeadSection loop or activates its actual head section, i.e., the section for it currentBlockHash - all tests pass	10 years ago
obscuren	d001479a47	unclean shutdown for now	10 years ago
obscuren	6abf8ef78f	Merge	10 years ago
zelig	4c89d5331f	adapt blockpool/backend to use pow/ezp with pow.Block for VerifyPoW func	10 years ago
zelig	01dc1c1394	blockpool rewritten , tests broken FIXME	10 years ago
zelig	5e4d77b2b8	initial commit for eth blockpool + test	10 years ago
zelig	76070b4674	blockpool rewritten , tests broken FIXME	10 years ago
zelig	4366fdfc13	initial commit for eth blockpool + test	10 years ago
zelig	3e38f8af23	initial commit for eth blockpool + test	10 years ago