- 09 11月, 2016 1 次提交
-
-
由 Felix Lange 提交于
-
- 04 11月, 2016 1 次提交
-
-
由 RJ 提交于
solves #3119 Signed-off-by: NVoR0220 <rj@erisindustries.com>
-
- 29 10月, 2016 1 次提交
-
-
由 bas-vk 提交于
This commit includes several API changes: - The behavior of eth_sign is changed. It now accepts an arbitrary message, prepends the well-known string \x19Ethereum Signed Message:\n<length of message> hashes the result using keccak256 and calculates the signature of the hash. This breaks backwards compatability! - personal_sign(hash, address [, password]) is added. It has the same semantics as eth_sign but also accepts a password. The private key used to sign the hash is temporarily unlocked in the scope of the request. - personal_recover(message, signature) is added and returns the address for the account that created a signature.
-
- 06 10月, 2016 1 次提交
-
-
由 Felix Lange 提交于
This commit replaces the deep-copy based state revert mechanism with a linear complexity journal. This commit also hides several internal StateDB methods to limit the number of ways in which calling code can use the journal incorrectly. As usual consultation and bug fixes to the initial implementation were provided by @karalabe, @obscuren and @Arachnid. Thank you!
-
- 28 9月, 2016 1 次提交
-
-
由 Gustav Simonsson 提交于
-
- 26 9月, 2016 2 次提交
-
-
由 Péter Szilágyi 提交于
-
由 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.
-
- 23 8月, 2016 1 次提交
-
-
由 Felix Lange 提交于
The need for these functions comes up in code that actually deploys and uses contracts. As of this commit, they can be used with both SimulatedBackend and ethclient. SimulatedBackend gains some additional methods in the process and is now safe for concurrent use.
-
- 22 8月, 2016 1 次提交
-
-
由 Felix Lange 提交于
In this commit, contract bindings and their backend start using the Ethereum Go API interfaces offered by ethclient. This makes ethclient a suitable replacement for the old remote backend and gets us one step closer to the final stable Go API that is planned for go-ethereum 1.5. The changes in detail: * Pending state is optional for read only contract bindings. BoundContract attempts to discover the Pending* methods via an interface assertion. There are a couple of advantages to this: ContractCaller is just two methods and can be implemented on top of pretty much anything that provides Ethereum data. Since the backend interfaces are now disjoint, ContractBackend can simply be declared as a union of the reader and writer side. * Caching of HasCode is removed. The caching could go wrong in case of chain reorganisations and removing it simplifies the code a lot. We'll figure out a performant way of providing ErrNoCode before the 1.5 release. * BoundContract now ensures that the backend receives a non-nil context with every call.
-
- 21 8月, 2016 1 次提交
-
-
由 Felix Lange 提交于
The remote backend is superseded by ethclient. The nil backend's stated purpose was to enable testing of accounts/abi/bind. None of its methods actually worked. A much simpler way to get a crashing backend is to simply pass nil as the backend. With a one-line change to the generator (removing two explicit interface assertions), passing nil actually works. Removing these backends means that less changes are required later.
-
- 17 8月, 2016 1 次提交
-
-
由 Felix Lange 提交于
The account manager was previously created by packge cmd/utils as part of flag processing and then passed down into eth.Ethereum through its config struct. Since we are starting to create nodes which do not have eth.Ethereum as a registered service, the code was rearranged to register the account manager as its own service. Making it a service is ugly though and it doesn't really fix the root cause: creating nodes without eth.Ethereum requires duplicating lots of code. This commit splits utils.MakeSystemNode into three functions, making creation of other node/service configurations easier. It also moves the account manager into Node so it can be used by those configurations without requiring package eth.
-
- 23 7月, 2016 1 次提交
-
-
由 Felix Lange 提交于
The new client implementation supports concurrent requests, subscriptions and replaces the various ad hoc RPC clients throughout go-ethereum.
-
- 15 7月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 11 7月, 2016 1 次提交
-
-
由 zsfelfoldi 提交于
-
- 16 6月, 2016 1 次提交
-
-
由 zsfelfoldi 提交于
-
- 10 6月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 06 6月, 2016 1 次提交
-
-
由 Thomas Bocek 提交于
When converting a negative number e.g., -2, the resulting ABI encoding should look as follows: fffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffe. However, since the check of the type is for an uint instead of an int, it results in the following ABI encoding: 0101010101010101010101010101010101010101010101010101010101010102. The Ethereum ABI (https://github.com/ethereum/wiki/wiki/Ethereum-Contract-ABI) says, that signed integers are stored in two's complement which should be of the form ffffff.... and not 01010101..... for e.g. -1. Thus, I removed the type check in numbers.go as well as the function S256 as I don't think they are correct. Or maybe I'm missing something?
-
- 20 5月, 2016 2 次提交
-
-
由 Bas van Kervel 提交于
-
由 Péter Szilágyi 提交于
-
- 12 5月, 2016 2 次提交
-
-
由 Péter Szilágyi 提交于
-
由 Péter Szilágyi 提交于
-
- 11 5月, 2016 1 次提交
-
-
由 Jeffrey Wilcke 提交于
Previously it was assumed that wheneven type `[]interface{}` was given that the interface was empty. The abigen rightfully assumed that interface slices which already have pre-allocated variable sets to be assigned. This PR fixes that by checking that the given `[]interface{}` is larger than zero and assigns each value using the generic `set` function (this function has also been moved to abi/reflect.go) and checks whether the assignment was possible. The generic assignment function `set` now also deals with pointers (useful for interface slice mentioned above) by dereferencing the pointer until it finds a setable type.
-
- 02 5月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 28 4月, 2016 4 次提交
-
-
由 Ales Katona 提交于
-
由 Jeffrey Wilcke 提交于
-
由 Jeffrey Wilcke 提交于
-
由 Jeffrey Wilcke 提交于
-
- 27 4月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 25 4月, 2016 1 次提交
-
-
由 Felix Lange 提交于
-
- 20 4月, 2016 1 次提交
-
-
由 Jeffrey Wilcke 提交于
Refactored the abi package parsing and type handling. Relying mostly on package reflect as opposed to most of our own type reflection. Our own type reflection is still used however for cases such as Bytes and FixedBytes (abi: bytes•). This also inclused several fixes for slice handling of arbitrary and fixed size for all supported types. This also further removes implicit type casting such as assigning, for example `[2]T{} = []T{1}` will fail, however `[2]T{} == []T{1, 2}` (notice assigning *slice* to fixed size *array*). Assigning arrays to slices will always succeed if they are of the same element type. Incidentally also fixes #2379
-
- 15 4月, 2016 3 次提交
-
-
由 Péter Szilágyi 提交于
-
由 Felix Lange 提交于
-
由 Felix Lange 提交于
-
- 13 4月, 2016 1 次提交
-
-
由 Péter Szilágyi 提交于
-
- 12 4月, 2016 6 次提交
-
-
由 Felix Lange 提交于
-
由 Felix Lange 提交于
- Sign takes common.Address, not Account - Import/Export methods work with encrypted JSON keys
-
由 Felix Lange 提交于
-
由 Felix Lange 提交于
-
由 Felix Lange 提交于
In order to avoid disk thrashing for Accounts and HasAccount, address->key file mappings are now cached in memory. This makes it no longer necessary to keep the key address in the file name. The address of each key is derived from file content instead. There are minor user-visible changes: - "geth account list" now reports key file paths alongside the address. - If multiple keys are present for an address, unlocking by address is not possible. Users are directed to remove the duplicate files instead. Unlocking by index is still possible. - Key files are overwritten written in place when updating the password.
-
由 Felix Lange 提交于
-