smart-contracts

Issue

Vyper handles unmapped instructions differently from Solidity. In Solidity, unmapped instructions are given a file index of -1. When attempting to show the source for such an instruction, we instead just show 1: // No source code found..

However, in Vyper, such instructions are not given a file index of -1, but are given a start and length of 0. So when we show the source for t

When passing Wasm function to the host as a callback, it's passed as an index in the table.
Wasm3 needs to provide an API to call such functions.

Testing methods like evm_mine and evm_increaseTime expect integer parameters. Unlike other methods, they reject these parameters if they are not decimal-encoded.

To reproduce

npx hardhat --version -> 2.5.0

Run npx hardhat node and make the following rpc calls:

> curl -H "Content-Type: application/json" -X POST --data \
        '{"id":1337,"jsonrpc":"2.0","method":"evm

Each contract has its own Lua stack.
To advance over several events, use coroutines.

We can safely disallow any use of solc below 0.4.25.

Add an example to load file from a directory along with https://remix-ide.readthedocs.io/en/latest/locations.html#load-one-of-the-default-remix-files