As per EIPs/eip-1474.md at master · ethereum/EIPs. For details see this PR discussion

Description

As i needed to use some method to verify ( recover? ) a signed message, i did a lot of research and what came out of it is that apparently a lot of people ( mostly stackexchange ) reffer to a method that is rather complicated AKA : web3.eth.accounts.recover(signatureObject);

As i am working with Ethereum technologies since a long time, i know that it is really easy to implemen

• I've asked for help in the Truffle Gitter before filing this issue.

Issue

As of 5.0.35, imports from node packages now throw compilation errors. This may or may not be intended behaviour, but it is a breaking change from 5.0.34 compiler - which seems to work just fine. I much prefer to have these imports over relat

These contracts' functions don't have explanations:

https://docs.openzeppelin.com/contracts/2.x/api/token/erc20#ERC20Pausable
https://docs.openzeppelin.com/contracts/2.x/api/token/erc20#SafeERC20
https://docs.openzeppelin.com/contracts/2.x/api/token/erc20#TokenTimelock

Since we switched to C++17 we can replace several boost constructs by their STL equivalent.
This includes, but may not be limited to:

• changing boost::optional to std::optional
• changing boost::variant to std::variant
• changing boost::filesystem to std::filesystem (note: this might have to be postponed due to ethereum/solidity#7263

Version: `0.10.0`
OS & Version: linux
Node version: `geth 1.8.2-stable-b8b9f7f4`

It seems that in "Latest transactions" in Ethereum Wallet there are listed pending transactions from all networks (the real network and several test networks) without displaying which network this transaction is of.

So either show it noticeably or l

• Parity Ethereum version: 2.4.5 or 2.4.6
• Operating system: Linux
• Installation: binary from Github | releases
• Fully synchronized: both, no and yes
• Network: ethereum
• Restarted: yes

Actual behaviour

When starting parity 2.4.5/2.4.6 in archive mode (tracing on, db_compaction ssd, pruning archive, fat_db on) with the default settings for the cache_size

Problem

The repository here mentions http://cpp-ethereum.org, which redirects to:

http://www.ethdocs.org/en/latest/ethereum-clients/cpp-ethereum/

which contains outdated documentation.

This can be highly misleading.

Solution

• Remove redirection / link
• mark http://www.ethdocs.org/en/latest/ethereum-clients/cpp-ethereum as outdated/legacy
• better yet: mark whole http://

Quorum doesn't return a message error clearly specifying the cause of an error (from a user standpoint) when the transaction manager fails to Quorum (e.g: 400 bad request, ...).

System information

Release: 2.2.3

Expected behaviour

Helpful error message

Actual behaviour

invalid argument 0: json: cannot unmarshal non-string into Go value of type common.Hash

Describe the bug
QR Code Scanner fails to scan input fields on Send Transaction view when scanning QR Code contains an EIP-681 URI

Example URI

ethereum:0x46c69f4424043e720a704330748cf3c593656b9c

To Reproduce
Steps to reproduce the behavior:

1. Go to Send Transaction view
2. Click on QR Code scanner
3. Position QR Code in front of Webcam
4. QR Code scanner closes

This module was used only in travis and appveyor

Problem

Currently when a user receives a PN, we show a very generic message (no indication of sender, body, etc). This will change in the future (e.g. with status-im/status-react#7043), so it would be good to be more explicit about the fact that we are showing a generic PN message due to the db being locked. Also, since we may receive PNs from users we've since removed

Summary of the problem

Manticore is unable to open multiple sockets with the same FileDescriptor (FD) because the symbolic array is named according to the FD, socket4, but when that FD is closed, we are unable to open/create a new socket with the same FD due to name collisions.

Step to reproduce the behavior

There is an expectedFailure test for this in #1514 in `tests/native/test_

Update to mypy 0.730 to get the latest improvements for type checking.