8 Commits (a9c94cbf48fefe39104ee3495df139ff374dd219)

Author	SHA1	Message	Date
Jeffrey Wilcke	a9c94cbf48	[release/1.4.8] test, cmd/evm, core, core/vm: illegal code hash implementation ... This implements a generic approach to enabling soft forks by allowing anyone to put in hashes of contracts that should not be interacted from. This will help "The DAO" in their endevour to stop any whithdrawals from any DAO contract by convincing the mining community to accept their code hash. (cherry picked from commit 7a5b571c67)	9 years ago
Felix Lange	d04a2e7557	all: update license information	9 years ago
Jeffrey Wilcke	f0cbebb19f	core: added basic chain configuration ... 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.	9 years ago
Jeffrey Wilcke	14013372ae	core: Added EVM configuration options ... The EVM is now initialised with an additional configured object that allows you to turn on debugging options.	9 years ago
Leif Jurvetson	b7bb2d8589	core: various typos	9 years ago
Ricardo Catalinas Jiménez	436fc8d76a	all: Rename crypto.Sha3{,Hash}() to crypto.Keccak256{,Hash}() ... As we aren't really using the standarized SHA-3	9 years ago
Jeffrey Wilcke	6cace73bea	core/vm/runtime: simplified runtime calling mechanism ... Implemented `runtime.Call` which uses - unlike Execute - the given state for the execution and the address of the contract you wish to execute. Unlike `Execute`, `Call` requires a config.	9 years ago
Jeffrey Wilcke	1372b991c3	core/vm/runtime: added simple execution runtime ... The runtime environment can be used for simple basic execution of contract code without the requirement of setting up a full stack and operates fully in memory.	9 years ago