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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Renamed `chain` => `core`	obscuren	2014-12-04	1	-8/+8
\|
*	merge errors fixed	obscuren	2014-12-02	1	-8/+2
\|\
\| *	Changed the way transactions are being added to the transaction pool	obscuren	2014-12-02	1	-4/+5
\| \|
* \|	Fixed merge	obscuren	2014-11-29	1	-2/+1
\|\\|
\| *	Changed refund	obscuren	2014-11-29	1	-1/+1
\| \|
\| *	GasData changes & removed min gas price	obscuren	2014-11-29	1	-1/+0
\| \|
* \|	Added a callback mechanism to chain adding.	obscuren	2014-11-19	1	-2/+5
\| \| \| \| \| \| \| \| \| \| \| \|	Not sure if this is the right approach. Why? BlockChain shouldn't need the "Ethereum" object. BlockChain shouldn't need to worry about notifying listeners or message propagation.
* \|	Begin of moving objects to types package	obscuren	2014-11-18	1	-7/+8
\|/ \| \| \| \|	* Block(s) * Transaction(s)
*	Fixed bloom, updated mining & block processing	obscuren	2014-11-10	1	-3/+26
\| \| \| \| \| \|	* Reverted back to process blocks in batches method * Bloom generation and lookup fix * Minor UI changed (mainly debug)
*	Implemented new miner w/ ui interface for merged mining. Closes #177	obscuren	2014-11-07	1	-144/+154
\| \| \| \| \| \| \| \|	* Miner has been rewritten * Added new miner pane * Added option for local txs * Added option to read from MergeMining contract and list them for merged mining
*	Reworked chain handling process	obscuren	2014-11-04	1	-2/+5
\| \| \| \| \| \| \|	* Forks * Rename * Moved inserting of blocks & processing * Added chain testing method for validating pieces of a a chain.
*	StateManager => BlockManager	obscuren	2014-11-04	1	-5/+5
\|
*	ethminer => miner	obscuren	2014-10-31	1	-0/+217