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

Had a hard time building both Aleth and Solidity, which were getting stuck on make.

Realized I should upgrade my GCC to a more current version, I had the initial configuration of:

• Ubuntu 16.04
• GCC/G++ 5.4.0
• clang version 3.8.0
• Boost 1.71

I then upgraded to G++ 6.5.0 and it is building successfully.

Ironically I wanted to contribute so I think this is a good starting po

https://remix-ide.readthedocs.io/en/latest/remix_commands.html should have at least remix.call() and a link to the list of API calls or it could list all the api calls there too.

currently various remix plugins uses their own logging mechanism. So does remix-tests. I introduced winston logger for remix-tests. As remix-tests is a terminal package & also can be used in browser, I think winston can be very helpful as we want to use various debugging levels. I am trying to use the logger such that we can pass the verbosity across packages. Then from within

What is wrong?

Previous to ethereum/py-evm#1805 we had classes like eth.vm.BaseVM that served as the reference. Now, we have interfaces defined in eth.abc.

There are now two primary problems.

• Many of our docstrings might still refer to the wrong class. Most class references in docstrings should be referencing the abc base classes now.
• Most of the met

We currently have a generic make target that pulls in the latest protobuf dependencies - documented here. To prevent competing updates to our auto-generated code we should be more explicit. I quite like the documentation here

Discussing the API with @jochem-brouwer we thought it might be easier from a developer PoV to have a modifyAccountFields that internally fetches an account from the trie, modify the given fields and then do a putAccount. This is to avoid users having to to the getAccount everytime they want to change an account. The method should probably throw if account doesn't exist.

Right now I'd like to be able to change function name and class names colors. Because my Monokai theme makes the solidity file look very bland. Only 2-3 colors are used and makes coding difficult because I've spent years on Monokai in other languages.

When configuring echidna with balanceContract, but fuzzing a non-payable contract, echidna prints a Haskell exception instead of a meaningful error.

$ cat balance.yaml
balanceContract: 100
format: text

$ cat balance.sol
contract C {
  function f() public {}
  function echidna_true() public returns (bool) {return true;}
}

$ echidna-test balance.sol --config balance.yaml
Analy

There is a way to build the bamboo compiler in Javascript:
pirapira/bamboo#260 (comment)
but it is not documented yet in README. This issue keeps track of adding the instruciton to README.

I could help getting this piece documented if you could guide me the following things:

• required dependencies
• installation (rake?)
• basic usage (any hint will do)

Some pending instructions not implemented by any eth clients (such as JUMPTO) are current listed in the main table. There are also instructions like SSTOREBYTES references in ethereum/EIPs#97 that are not actually implemented. These should be split into a separate tables

We should create a corpus of tests to verify that CFG recovery is accurate and complete, and there are no regressions.

Do we really need gethrpc crate in SputnikVM ?
If don't we should put into separate project, maybe inside etcommon-rs

If similar functionality used in emerald-rs consider putting it into common place

Commands are automatially found and listed.

I suppose that if the comment at the top is missing, the command doesn't get listed. See e.g. the --to-dec command.

recently CI failed many times testing cluster because of port already used, which can be very annoying.

I was researching on the various tools for Ethereum smart contract security and came across Securify. I read through in this document that Securify detects 18 critical vulnerabilities in Ethereum smart contracts. Can someone kindly consider my humble request fo

See ethereum/evmc#362 (comment)