🧐 Motivation
Create simple ERC20 and ERC777 presets with fixed supply.
The benefits are:

• Easy to deploy (including from Remix).
• No access control (for minting/pausing), and hence no governance required.
• Can be verified easily on public networks and then are verified for all.

📝 Details

Community members are creating their own simple ERC20 tokens, so it would be good if they

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?

https://eips.ethereum.org/EIPS/eip-2926

EIP-2027, aka Code Merklization is coming down the EIP pipeline. It would be nice to have a basic implementation of it.

How can it be fixed

Implement a stand-alone API for merklizing code. I'd recommend something loosely using the following structure:

from typing import NamedTuple

class MerklizedCode(Name

Lots of methods in Common have to do with numbers. We sometimes convert BNs to numbers (for instance block numbers) and feed those to Common. Common should support inputs where this input is of type BN and should also handle arithmetic as BN. We can keep supporting numbers by internally converting it to BN and then feeding it to the same method which handles the input as BN.

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

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

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

See ethereum/evmc#362 (comment)