Alex Beregszaszi
Alex Beregszaszi
Depending on the speed of #189 we may want to consider augmenting Wasm with 256-bit support. This issue track the extreme end where native 256-bit opcodes are added. These native...
The execution engine part is mostly found here: https://notes.ethereum.org/s/HylpjAWsE#Shard-processing Official discussion thread: https://ethresear.ch/t/a-layer-1-minimizing-phase-2-state-execution-proposal/5397 We should investigate the feasibility of this proposal in ewasm and provide feedback on the ethresearch forum.
Based on the library design described in #17, suggest to support a small standard library at address `0x00..0f` to have the following exports: - `memcpy(dst:i32, src:i32, len:i32)` - `memset(dst:i32, val:i32,...
The [system contracts](./system_contracts.md) are currently defined as precompiles and live at addresses `0x000...0` to `0x000...b`. We should research how these can be moved into being part of the Ethereum state.
This is not a fully explored idea yet, and it can be considered quite dangerous, but it would interesting to see how we can have mutable code. One example is...
This topic has been touched upon a few times, but never discussed in actual depth. Not after doing some protoyping with *runevm* it seems the following features are missing: -...
One other idea I was having some thought about is the following: - by default ewasm contracts are executed via an interpreter and costs are tuned for that - the...
## serenity asynchronous execution (Some of these details are based on asking @vbuterin questions and my interpretation of the answers. I'm not 100% familiar with the entire Serenity specification.) Based...
This is a discussion we've had with @karalabe and @holiman. Having a mixed chain has a lot of challenges, some of which include: - What happens to wasm bytecode deployed...