- 15 7月, 2016 5 次提交
-
-
由 Péter Szilágyi 提交于
-
由 Péter Szilágyi 提交于
-
由 Péter Szilágyi 提交于
-
由 Péter Szilágyi 提交于
-
由 Péter Szilágyi 提交于
-
- 11 7月, 2016 1 次提交
-
-
由 zsfelfoldi 提交于
-
- 08 7月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 29 6月, 2016 4 次提交
-
-
由 Péter Szilágyi 提交于
This reverts commit 7a5b571c.
-
由 Péter Szilágyi 提交于
This reverts commit c4de2893.
-
由 Péter Szilágyi 提交于
This reverts commit ba784bdf.
-
由 Péter Szilágyi 提交于
This reverts commit 1e3a7d4f.
-
- 24 6月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 23 6月, 2016 2 次提交
-
-
由 Péter Szilágyi 提交于
-
由 Péter Szilágyi 提交于
-
- 22 6月, 2016 3 次提交
-
-
由 Jeffrey Wilcke 提交于
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.
-
由 Yoichi Hirai 提交于
-
由 Fabio Berger 提交于
-
- 16 6月, 2016 1 次提交
-
-
由 zsfelfoldi 提交于
-
- 13 6月, 2016 1 次提交
-
-
由 Jeffrey Wilcke 提交于
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
-
- 07 6月, 2016 1 次提交
-
-
由 zsfelfoldi 提交于
-
- 06 6月, 2016 1 次提交
-
-
由 zsfelfoldi 提交于
-
- 03 6月, 2016 1 次提交
-
-
由 Felix Lange 提交于
Fixes #2650
-
- 27 5月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 26 5月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 25 5月, 2016 1 次提交
-
-
由 Felix Lange 提交于
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.
-
- 23 5月, 2016 1 次提交
-
-
由 Fabio Berger 提交于
-
- 13 5月, 2016 1 次提交
-
-
由 Jeffrey Wilcke 提交于
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.
-
- 09 5月, 2016 1 次提交
-
-
由 Felix Lange 提交于
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.
-
- 29 4月, 2016 1 次提交
-
-
由 Nicholas Johnson 提交于
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.
-
- 25 4月, 2016 1 次提交
-
-
由 Jeffrey Wilcke 提交于
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
-
- 15 4月, 2016 4 次提交
-
-
由 Felix Lange 提交于
-
由 Felix Lange 提交于
Lazy "I'll just put return here instead of fixing the test" found by go vet.
-
由 Felix Lange 提交于
This fixes a few uses of unkeyed Body literals which go vet was complaining about.
-
由 Felix Lange 提交于
-
- 04 4月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 01 4月, 2016 3 次提交
-
-
由 Jeffrey Wilcke 提交于
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
-
由 Jeffrey Wilcke 提交于
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
-
由 Jeffrey Wilcke 提交于
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.
-
- 24 3月, 2016 2 次提交
-
-
由 Jeffrey Wilcke 提交于
This commit serves as a temporary workaround for enabling the jit until the block customisation PR is merged in.
-
由 Jeffrey Wilcke 提交于
The EVM is now initialised with an additional configured object that allows you to turn on debugging options.
-