mirror of https://github.com/poanetwork/quorum.git
5765a6a331
The scenario is covered in https://github.com/jpmorganchase/quorum/issues/428, but in short, if we're mining but two new blocks come in over the network: (1) The first will clear the speculative chain. (2) The second previously would have been a noop here -- `removeProposedTxes` does nothing in this case, but we need to update the speculative chain head to the new block. The important invariant identified by @guojian1234 that this now maintains is `minter.speculativeChain.head.blockNumber >= minter.chain.head.blockNumber`. |
||
|---|---|---|
| .. | ||
| api.go | ||
| backend.go | ||
| constants.go | ||
| doc.md | ||
| events.go | ||
| handler.go | ||
| listener.go | ||
| minter.go | ||
| peer.go | ||
| persistence.go | ||
| snapshot.go | ||
| speculative_chain.go | ||
| util.go | ||
| wal.go | ||