Roman Khimov 920d7c610c core: remove blockCache, use MemoryStore, redesign persist() ... Commit 578ac414d4 was wrong in that it saved only a part of the block, so depending on how you use blockchain, you may still see that the block was not really processed properly. To really fix it this commit introduces intermediate storage layer in form of memStore, which actually is a MemoryStore that supports full Store API (thus easily fitting into the existing code) and one extension that allows it to flush its data to some other Store. It also changes AddBlock() semantics in that it only accepts now successive blocks, but when it does it guarantees that they're properly added into the Blockchain and can be referred to in any way. Pending block queing is now moved into the server (see 8c0c055ac657813fe3ed10257bce199e9527d5ed). So the only thing done with persist() now is just a move from memStore to Store which probably should've always been the case (notice also that previously headers and some other metadata was written into the Store bypassing caching/batching mechanism thus leading to some inefficiency).		2019-09-27 15:42:35 +03:00
..
core	core: remove blockCache, use MemoryStore, redesign persist()	2019-09-27 15:42:35 +03:00
crypto	crypto: change files mode to 644 (some *.go had exec flags set)	2019-09-17 15:34:00 +03:00
internal/keytestcases	*: add/fix godoc comments to satisfy golint	2019-09-03 17:57:51 +03:00
interop	*: fix some misspellings	2019-09-03 18:20:05 +03:00
io	io: drop getVarStringSize() completely	2019-09-20 20:01:56 +03:00
network	network: add block queue	2019-09-27 13:00:09 +03:00
rpc	core: remove blockCache, use MemoryStore, redesign persist()	2019-09-27 15:42:35 +03:00
smartcontract	io: move BinReader/BinWriter there, redo Serializable with it	2019-09-16 23:39:51 +03:00
util	io: drop Size() method from Serializable and associated	2019-09-17 13:21:45 +03:00
vm	vm: add CHECKSIG/VERIFY/CHECKMULTISIG implementations	2019-09-24 13:01:54 +03:00
wallet	*: gofmt -s	2019-09-09 12:02:24 +03:00