- 07 1月, 2017 2 次提交
-
-
由 Felix Lange 提交于
-
由 Felix Lange 提交于
-
- 06 1月, 2017 2 次提交
-
-
由 Felix Lange 提交于
-
由 Felix Lange 提交于
This significantly reduces the dependency closure of ethclient, which no longer depends on core/vm as of this change. All uses of vm.Logs are replaced by []*types.Log. NewLog is gone too, the constructor simply returned a literal.
-
- 13 12月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 05 12月, 2016 1 次提交
-
-
由 Felix Lange 提交于
This field used to be assigned by the filter system and returned through the RPC API. Now that we have a Go client that uses the underlying type, the field needs to move. It is now assigned to true when the RemovedLogs event is generated so the filter system doesn't need to care about the field at all. While here, remove the log list from ChainSideEvent. There are no users of this field right now and any potential users could subscribe to RemovedLogsEvent instead.
-
- 28 11月, 2016 1 次提交
-
-
由 Jeffrey Wilcke 提交于
Fixed unwinding of bad hashes when already on the canon chain
-
- 23 11月, 2016 1 次提交
-
-
由 Jeffrey Wilcke 提交于
-
- 13 11月, 2016 2 次提交
-
-
由 Jeffrey Wilcke 提交于
-
由 Jeffrey Wilcke 提交于
This commit implements EIP158 part 1, 2, 3 & 4 1. If an account is empty it's no longer written to the trie. An empty account is defined as (balance=0, nonce=0, storage=0, code=0). 2. Delete an empty account if it's touched 3. An empty account is redefined as either non-existent or empty. 4. Zero value calls and zero value suicides no longer consume the 25k reation costs. params: moved core/config to params Signed-off-by: NJeffrey Wilcke <jeffrey@ethereum.org>
-
- 09 11月, 2016 1 次提交
-
-
由 Zsolt Felfoldi 提交于
-
- 21 10月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 18 10月, 2016 2 次提交
-
-
由 Péter Szilágyi 提交于
-
由 Martin Holst Swende 提交于
-
- 15 10月, 2016 1 次提交
-
-
由 Felix Lange 提交于
* trie: store nodes as pointers This avoids memory copies when unwrapping node interface values. name old time/op new time/op delta Get 388ns ± 8% 215ns ± 2% -44.56% (p=0.000 n=15+15) GetDB 363ns ± 3% 202ns ± 2% -44.21% (p=0.000 n=15+15) UpdateBE 1.57µs ± 2% 1.29µs ± 3% -17.80% (p=0.000 n=13+15) UpdateLE 1.92µs ± 2% 1.61µs ± 2% -16.25% (p=0.000 n=14+14) HashBE 2.16µs ± 6% 2.18µs ± 6% ~ (p=0.436 n=15+15) HashLE 7.43µs ± 3% 7.21µs ± 3% -2.96% (p=0.000 n=15+13) * trie: close temporary databases in GetDB benchmark * trie: don't keep []byte from DB load around Nodes decoded from a DB load kept hashes and values as sub-slices of the DB value. This can be a problem because loading from leveldb often returns []byte with a cap that's larger than necessary, increasing memory usage. * trie: unload old cached nodes * trie, core/state: use cache unloading for account trie * trie: use explicit private flags (fixes Go 1.5 reflection issue). * trie: fixup cachegen overflow at request of nick * core/state: rename journal size constant
-
- 11 10月, 2016 1 次提交
-
-
由 Jeffrey Wilcke 提交于
-
- 08 10月, 2016 1 次提交
-
-
由 Felix Lange 提交于
If geth is busy importing 2048 heavy blocks it can take a while before it prints anything. This change ensures that a message gets printed every 8s.
-
- 28 9月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 26 9月, 2016 1 次提交
-
-
由 Felix Lange 提交于
This change introduces a global, per-state cache that keeps account data in the canon state. Thanks to @karalabe for lots of fixes.
-
- 16 8月, 2016 1 次提交
-
-
由 Bas van Kervel 提交于
-
- 08 7月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 07 6月, 2016 1 次提交
-
-
由 zsfelfoldi 提交于
-
- 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.
-
- 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.
-
- 15 4月, 2016 2 次提交
-
-
由 Felix Lange 提交于
-
由 Felix Lange 提交于
This fixes a few uses of unkeyed Body literals which go vet was complaining about.
-
- 01 4月, 2016 1 次提交
-
-
由 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.
-
- 16 3月, 2016 2 次提交
-
-
由 Leif Jurvetson 提交于
-
由 Leif Jurvetson 提交于
-
- 11 3月, 2016 2 次提交
-
-
由 Jeffrey Wilcke 提交于
Added a future lock which prevents the anything being added or removed from or to the set when looping over the set of blocks. This fixes a nil pointer in the range loop when trying to retrieve a block from the set which was previously available but removed due to regular chain processing. Fixes #2305
-
由 Péter Szilágyi 提交于
-
- 10 3月, 2016 1 次提交
-
-
由 zsfelfoldi 提交于
-
- 08 3月, 2016 1 次提交
-
-
由 Jeffrey Wilcke 提交于
Previously all blocks that were already in our chain were never re announced as potential uncle block (e.g. ChainSideEvent). This is problematic during mining where you want to gather as much possible uncles as possible increasing the profit. This is now addressed in this PR where during reorganisations of chains the old chain is regarded as uncles. Fixed #2298
-
- 18 2月, 2016 1 次提交
-
-
由 Jeffrey Wilcke 提交于
Assuming the following scenario where a miner has 15% of all hashing power and the ability to exert a moderate control over the network to the point where if the attacker sees a message A, it can't stop A from propagating, but what it **can** do is send a message B and ensure that most nodes see B before A. The attacker can then selfish mine and augment selfish mining strategy by giving his own blocks an advantage. This change makes the time at which a block is received less relevant and so the level of control an attacker has over the network no longer makes a difference. This change changes the current td algorithm `B_td > C_td` to the new algorithm `B_td > C_td || B_td == C_td && rnd < 0.5`.
-
- 13 2月, 2016 1 次提交
-
-
由 Jeffrey Wilcke 提交于
Pending logs are now filterable through the Go API. Filter API changed such that each filter type has it's own bucket and adding filter explicitly requires you specify the bucket to put it in.
-
- 04 1月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 04 12月, 2015 1 次提交
-
-
由 Péter Szilágyi 提交于
-