901 Commits (c4d21bc8e548d909d5b2940cb00d3d068f5697ec)

Author	SHA1	Message	Date
Péter Szilágyi	6060e098c9	cmd, core, eth, params: implement flags to control dao fork blocks	8 years ago
Péter Szilágyi	a691aa2a13	eth/downloader: return invalid chain (peer drop) on import fails	8 years ago
zsfelfoldi	00787fe781	core: added CheckNonce() to Message interface	8 years ago
Henning Diedrich	51f8ce26cf	eth: fix #2710 filter races ... and locking bugs found in its wake.	8 years ago
Péter Szilágyi	ddfef21125	eth: disable eth/61 to prepare for more elaborate fork sync algos	8 years ago
Péter Szilágyi	96dc42d99c	cmd, common, console, eth, release: drop redundant "full"s	8 years ago
zsfelfoldi	3a97280ae8	eth: separate common and full node-specific API and backend service	9 years ago
Péter Szilágyi	783289068a	eth/downloader: fix occasional fast sync critical section test fails	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
Péter Szilágyi	32559ccad1	eth: don't accept transactions until we sync up with the network	9 years ago
Péter Szilágyi	88f174a014	eth/downloader: adaptive quality of service tuning	9 years ago
Péter Szilágyi	61ee9f299d	eth/downloader: make fast sync resilient to critical section fails	9 years ago
Péter Szilágyi	4496a44f68	eth/downloader: ensure cancel channel is closed post sync	9 years ago
Péter Szilágyi	4f1d92b332	eth/downloader, trie: pull head state concurrently with chain	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
Rémy Roy	f86ea9aad5	eth/api: fixed GetCompilers when there is no error creating Solc	9 years ago
Bas van Kervel	64a6c2c1b6	eth: add new RPC method (personal.) SignAndSendTransaction	9 years ago
Péter Szilágyi	1580ec1804	accounts/abi/bind, eth: rely on getCode for sanity checks, not estimate and call	9 years ago
Péter Szilágyi	8906b2fe09	eth/downloader: fix reviewer comments	9 years ago
Jeffrey Wilcke	4b1a7d3868	eth: fixed regression in eth_signTransaction fixes #2578 ... Sign transaction returned the unsigned transaction rather than the signed one.	9 years ago
Bas van Kervel	67cd4ee8d2	eth/filter: bugfix which can cause a nil pointer crash when parsing filter arguments	9 years ago
Péter Szilágyi	d87f7a1e81	eth: skip transaction handling during fast sync	9 years ago
Péter Szilágyi	e86619e75d	eth/downloader: stream partial skeleton filling to processor	9 years ago
Péter Szilágyi	b40dc8a1da	eth/downloader: implement concurrent header downloads	9 years ago
Péter Szilágyi	39ce85cf5d	eth/downloader: bound fork ancestry and allow heavy short forks	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
Jeffrey Wilcke	7d59c5c58d	eth: fixed tracing functions using the current header instead of parent ... Fixes #2525	9 years ago
Péter Szilágyi	586eddfd09	release, all: integrate the release service into geth	9 years ago
Ales Katona	572da73d4d	eth: add personal_importRawKey for runtime private key import	9 years ago
Bas van Kervel	48cc36ce83	eth/filters: ignore logs that don't match filter criteria on chain reorg	9 years ago
Péter Szilágyi	cdcbb2f160	accounts/abi/bind, eth: add contract non-existent error	9 years ago
Felix Lange	a40e61b4ac	rpc: remove NotifierContextKey ... Context keys must have a unique type in order to prevent any unintented clashes. The code used int(1) as key. Fix it by implementing the pattern recommended by package context.	9 years ago
Felix Lange	6fdd0893c3	all: fix go vet warnings	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	53016c1225	eth, rpc: make trace configs optional	9 years ago
Péter Szilágyi	bbc77f488e	eth: fix single transaction tracing (run prev mutations)	9 years ago
Felix Lange	bcd8aeefdd	eth: add chaindbProperty to debug API	9 years ago
Felix Lange	46df50be18	accounts: improve API and add documentation ... - Sign takes common.Address, not Account - Import/Export methods work with encrypted JSON keys	9 years ago
Felix Lange	549f1add29	eth: report unlock errors to RPC clients	9 years ago
Felix Lange	46e8940b19	accounts: streamline API ... - Manager.Accounts no longer returns an error. - Manager methods take Account instead of common.Address. - All uses of Account with unkeyed fields are converted.	9 years ago
Felix Lange	85e6c40c00	accounts, crypto: move keystore to package accounts ... The account management API was originally implemented as a thin layer around crypto.KeyStore, on the grounds that several kinds of key stores would be implemented later on. It turns out that this won't happen so KeyStore is a superflous abstraction. In this commit crypto.KeyStore and everything related to it moves to package accounts and is unexported.	9 years ago
Péter Szilágyi	aceaaa5178	eth: gracefully fail if chain config is missing	9 years ago
Bas van Kervel	aa9fff3e68	rpc: various fixes/enhancements ... rpc: be less restrictive on the request id rpc: improved documentation console: upgrade web3.js to version 0.16.0 rpc: cache http connections rpc: rename wsDomains parameter to wsOrigins	9 years ago
Péter Szilágyi	bf1f620343	eth: fix GPU miner chain config regression	9 years ago
Felix Lange	cf842b3fe5	cmd/geth, eth: move --genesis deprecation warning to cmd/geth ... This prevents display of the warning for --dev and --olympic.	9 years ago
Bas van Kervel	f7328c5ecb	rpc: add pub/sub support	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