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

	Commit message (Collapse)	Author	Age	Files	Lines
*	Use the state instead of the state object directly.	obscuren	2014-10-16	1	-0/+25
\| \| \| \| \| \| \|	If a state gets reset and you still hold a pointer to the previous, incorrect, state object you'll operate on the wrong object. Using the state to set/get objects and attributes you won't have this problem since the state will always have the correct object.
*	Fixed remote Arithmetic tests	obscuren	2014-10-15	1	-0/+9
\|
*	Couple of minor issues fixed	obscuren	2014-10-15	1	-1/+5
\| \| \| \| \|	* CALLVALUE pushed incorrect value to the stack * Set execution model to closure
*	Minor tweaks for poc7	obscuren	2014-10-08	1	-6/+8
\|
*	Improved catching up and refactored	obscuren	2014-09-15	1	-2/+3
\|
*	Added GetCode method	obscuren	2014-09-08	1	-0/+9
\|
*	Changed log statements	obscuren	2014-08-22	1	-1/+1
\|
*	Added message to closure && added change addresses	obscuren	2014-08-15	1	-2/+0
\|
*	Updated chain for filtering	obscuren	2014-08-11	1	-41/+4
\|
*	ethstate.NewState => ethstate.New	obscuren	2014-08-04	1	-2/+2
\|
*	Old code removed and renamed amount to balance	obscuren	2014-07-30	1	-2/+3
\|
*	Refactored to new state and vm	obscuren	2014-07-24	1	-26/+26
\|
*	Refactored state, state object and vm	obscuren	2014-07-22	1	-0/+259
	* The State and StateObject have been moved to their own package * The VM is moved to it's own package