944 Commits (6988e5f0747523d2e93f0c35b9c64a66a7f5986e)

Author	SHA1	Message	Date
Bas van Kervel	47ff813012	rpc: refactor subscriptions and filters	8 years ago
Bas van Kervel	bb8059f6aa	core: ensure the canonical block is written before the canonical hash is set	8 years ago
Felix Lange	e4736fe469	core/vm: hide ecrecover error message ... Fixes #2825	8 years ago
Felix Lange	704fde01e8	core/types, core/vm: improve docs, add JSON marshaling methods ... In this commit, core/types's types learn how to encode and decode themselves as JSON. The encoding is very similar to what the RPC API uses. The RPC API is missing some output fields (e.g. transaction signature values) which will be added to the API in a later commit. Some fields that the API generates are ignored by the decoder methods here.	8 years ago
Péter Szilágyi	2c2e389b77	cmd, core, eth, miner, params, tests: finalize the DAO fork	8 years ago
Péter Szilágyi	3291235711	accounts, core, eth: pass chain config for chain maker to test DAO	8 years ago
Péter Szilágyi	461cdb593b	core, params, tests: add DAO hard-fork balance moves	8 years ago
Péter Szilágyi	7f00e8c033	core, eth: enforce network split post DAO hard-fork	8 years ago
Péter Szilágyi	a87089fd2d	cmd, core, miner: add extradata validation to consensus rules	8 years ago
Péter Szilágyi	9e56811a37	core: gracefully handle missing homestead block config	8 years ago
Péter Szilágyi	6060e098c9	cmd, core, eth, params: implement flags to control dao fork blocks	8 years ago
zsfelfoldi	00787fe781	core: added CheckNonce() to Message interface	8 years ago
Péter Szilágyi	f5a29eab5c	core: solve a remote-import/local-mine data race	9 years ago
Péter Szilágyi	6362a9d610	Revert "test, cmd/evm, core, core/vm: illegal code hash implementation" ... This reverts commit 7a5b571c67.	9 years ago
Péter Szilágyi	d55fc35df1	Revert "core: add voting and result tracking for the dao soft-fork" ... This reverts commit c4de28938f.	9 years ago
Péter Szilágyi	67e9d33486	Revert "core: update DAO soft-fork number, clean up the code" ... This reverts commit ba784bdf36.	9 years ago
Péter Szilágyi	219859f8bb	Revert "core: update the DAO soft fork proposal to the final block" ... This reverts commit 1e3a7d4fab.	9 years ago
Péter Szilágyi	1e3a7d4fab	core: update the DAO soft fork proposal to the final block	9 years ago
Péter Szilágyi	ba784bdf36	core: update DAO soft-fork number, clean up the code	9 years ago
Péter Szilágyi	c4de28938f	core: add voting and result tracking for the dao soft-fork	9 years ago
Jeffrey Wilcke	7a5b571c67	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.	9 years ago
Yoichi Hirai	86bc7795a3	vm: Replace some SstoreClearGas with SstoreResetGas	9 years ago
Fabio Berger	a3efdb13f2	README, core, rpc: fix various typos	9 years ago
zsfelfoldi	3a97280ae8	eth: separate common and full node-specific API and backend service	9 years ago
Jeffrey Wilcke	bb3651abc8	core/state, eth: Updated suicides objects when tracing transactions ... Consensus rules dictate that objects can only be removed during the finalisation of the transaction (i.e. after all calls have finished). Thus calling a suicided contract twice from the same transaction: A->B(S)->ret(A)->B(S) results in 2 suicides. Calling the suicided object twice from two transactions: A->B(S), A->B, results in only one suicide and a call to an empty object. Our current debug tracing functionality replays all transaction that were executed prior to the targetted transaction in order to provide the user with an accurate trace. As a side effect to calling StateDB.IntermediateRoot it also deletes any suicides objects. Our tracing code never calls this function because it isn't interested in the intermediate root. Becasue of this it caused a bug in the tracing code where transactions that were send to priviously deleted objects resulted in two suicides rather than one suicide and a call to an empty object. Fixes #2542	9 years ago
zsfelfoldi	f9917c8c7b	core: improved chainDb using sequential keys	9 years ago
zsfelfoldi	5a458da42a	core: chain read/write speed benchmarks	9 years ago
Felix Lange	fc85dd175e	core: add missing lock in TxPool.{GetTransaction,RemoveTx} ... Fixes #2650	9 years ago
Péter Szilágyi	8ee84584a4	core/state: return the starting nonce for non-existent accs (testnet)	9 years ago
Péter Szilágyi	748d1c171d	core, core/state, trie: enterprise hand-tuned multi-level caching	9 years ago
Felix Lange	ca18202eb9	eth: enable bad block reports ... We used to have reporting of bad blocks, but it was disabled before the Frontier release. We need it back because users are usually unable to provide the full RLP data of a bad block when it occurs. A shortcoming of this particular implementation is that the origin peer is not tracked for blocks received during eth/63 sync. No origin peer info is still better than no report at all though.	9 years ago
Fabio Berger	faf663133b	core: Simplify bloom9 tests with available convenience method `TestBytes`	9 years ago
Jeffrey Wilcke	fe532a98f9	core: fixed pointer assignment ... This fixes an issue where it's theoretical possible to cause a consensus failure when hitting the lower end of the difficulty, though pratically impossible it's worth a fix.	9 years ago
Felix Lange	56ed6152a1	core, eth, miner: improve shutdown synchronisation ... Shutting down geth prints hundreds of annoying error messages in some cases. The errors appear because the Stop method of eth.ProtocolManager, miner.Miner and core.TxPool is asynchronous. Left over peer sessions generate events which are processed after Stop even though the database has already been closed. The fix is to make Stop synchronous using sync.WaitGroup. For eth.ProtocolManager, in order to make use of WaitGroup safe, we need a way to stop new peer sessions from being added while waiting on the WaitGroup. The eth protocol Run function now selects on a signaling channel and adds to the WaitGroup only if ProtocolManager is not shutting down. For miner.worker and core.TxPool the number of goroutines is static, WaitGroup can be used in the usual way without additional synchronisation.	9 years ago
Nicholas Johnson	c74a575725	core: Provide a public accessor for ChainConfig ... This is necessary for external users of the go-ethereum code who want to, for instance, build a custom node that plays back transactions, as core.ApplyTransaction requires a ChainConfig as a parameter.	9 years ago
Jeffrey Wilcke	c1a4dcfc87	core, eth: added json tag field for proper unmarshalling ... According to our own instructions the genesis config attribute should be "config". The genesis definition in the go code, however, has a field called `ChainConfig`. This field now has a `json:"config"` struct tag so that the json is properly unmarshalled. This fixes #2482	9 years ago
Felix Lange	6fdd0893c3	all: fix go vet warnings	9 years ago
Felix Lange	68c755a238	core/state: fix TestDump ... Lazy "I'll just put return here instead of fixing the test" found by go vet.	9 years ago
Felix Lange	24cdac41f3	core, core/types, eth: add and use Block.Body ... This fixes a few uses of unkeyed Body literals which go vet was complaining about.	9 years ago
Felix Lange	d04a2e7557	all: update license information	9 years ago
Péter Szilágyi	e9254bb0f9	core, miner: remove Frontier canary	9 years ago
Jeffrey Wilcke	1f3596c25a	core: transition db now also returns the required gas amount ... Exposes some core methods to transition and compute new state information and adds an additional return value to the transition db method to fetch required gas for that particular message (excluding gas refunds from any SSTORE[X] = 0 and SUICIDE. Fixes #2395	9 years ago
Jeffrey Wilcke	9055c16efa	accounts/a/b/backends, core: chain maker homestead block set to 0 ... 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	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	0cfa21fc7f	core, eth, cmd: temporary work around for enabling the jit ... This commit serves as a temporary workaround for enabling the jit until the block customisation PR is merged in.	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
Jeffrey Wilcke	342ae7ce7d	core, core/vm, tests: changed the initialisation behaviour of the EVM ... The EVM was previously initialised and created for every CALL, CALLCODE, DELEGATECALL and CREATE. This PR changes this behaviour so that the same EVM can be used through the session and beyond as long as the Environment sticks around.	9 years ago
Leif Jurvetson	434e4b31d8	core, eth: replace reorganiz with reorganis	9 years ago
Leif Jurvetson	b7bb2d8589	core: various typos	9 years ago
Leif Jurvetson	c7727191ae	core: fixed various typos	9 years ago