Not exactly a bug, for for those who have been using Claimable in earlier versions of OZ (for the purpose of transferOwnership followed by claimOwnership) - what are the options in v2.0.0?

Relying solely on Ownable.transferOwnership lacks a safety mechanism for accidentally transferring the ownership to an incorrect address.

At present, the only alternative that I see is copying `Cla

The cpp-ethereum homepage is not exactly helpful... http://cpp-ethereum.org/ which just takes you to here: http://www.ethdocs.org/en/latest/ethereum-clients/cpp-ethereum/ which only helps with building and installing.. and the only useful link is the "Running" which is only this: "Running eth without any argument will synchronise your node to the public blockchain. It is also possible to create or

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

I'm trying to use ethereumjs-blockchain to read the raw levedb data created by geth, but I failed to do so.
And I also try to use the dbManager to read the levedb data, failed again. My steps are:

1. sync some the blockchain data by using geth --goerli --datadir <my data dir>
2. write code to read the level db data.

const level = require('level');
const DbManager = requ

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

Currently, we are not able to
a) symbolically execute init code with symbolic arguments
b) get srcmapping for init code with arguments

We could change ContractCode as follows:

data ContractCode
  = InitCode (ByteString, Buffer)    -- ^ "Constructor" code, during contract creation (possibly with arguments)
  | RuntimeCode ByteString           -- ^ "Instance" code, after contract crea

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

See ethereum/evmc#362 (comment)