core: find block in db (#174)

* Make sure block pool is large enough

It's safe to use a larger blockPool when
the number of chains is smaller.

* Construct latticeData via config.
* Seek acked blocks in blockdb when
   unable to find them in memory cache.

In previous implementation, we assume
our cache in memory is enough to perform
DAG's sanity check. However, it's no longer
true when the number of chains might be
changed between rounds.

* Simplify purge.

Remove the relation to purge block by chainStatus.

1 files changed, 4 insertions, 1 deletions

diff --git a/integration_test/node.go b/integration_test/node.go
index c0c4fa1..555142d 100644
--- a/integration_test/node.go
+++ b/integration_test/node.go
@@ -203,11 +203,14 @@ func (n *Node) processBlock(b *types.Block) (err error) {
 		}
 		// Deliver blocks.
 		for _, b = range delivered {
-			if err = n.db.Update(*b); err != nil {
+			if err = n.db.Put(*b); err != nil {
 				return
 			}
 			n.app.BlockDelivered(*b)
 		}
+		if err = n.lattice.PurgeBlocks(delivered); err != nil {
+			return
+		}
 		// Update pending blocks for verified block (pass sanity check).
 		pendings = append(pendings, verified...)
 	}