go-tangerine - Tangerine full node (https://github.com/tangerine-network/go-tangerine)

	Commit message (Collapse)	Author	Age	Files	Lines
*	accounts/a/b/backends, core: chain maker homestead block set to 0	Jeffrey Wilcke	2016-04-01	1	-2/+1
\| \| \| \| \| \| \|	The chain maker and the simulated backend now run with a homestead phase beginning at block 0 (i.e. there's no frontier). This commit also fixes up #2388
*	core: added basic chain configuration	Jeffrey Wilcke	2016-04-01	1	-3/+9
\| \| \| \| \| \| \| \| \|	Added chain configuration options and write out during genesis database insertion. If no "config" was found, nothing is written to the database. Configurations are written on a per genesis base. This means that any chain (which is identified by it's genesis hash) can have their own chain settings.
*	cmd, common, core, eth, node, rpc, tests, whisper, xeth: use protocol stacks	Péter Szilágyi	2015-11-27	1	-1/+1
\|
*	core, eth, miner, xeth: clean up tx/receipt db accessors	Péter Szilágyi	2015-11-19	1	-1/+1
\|
*	core, eth, rpc: split out block validator and state processor	Jeffrey Wilcke	2015-11-18	1	-0/+89
	This removes the burden on a single object to take care of all validation and state processing. Now instead the validation is done by the `core.BlockValidator` (`types.Validator`) that takes care of both header and uncle validation through the `ValidateBlock` method and state validation through the `ValidateState` method. The state processing is done by a new object `core.StateProcessor` (`types.Processor`) and accepts a new state as input and uses that to process the given block's transactions (and uncles for rewords) to calculate the state root for the next block (P_n + 1).