Jake Lang

## Proposal: Storage Modules In order to handle the case of re-entrancy, we need the storage mappings (or at least info about revisions to storage) to persist across calls. With...

## Proposal 2: Storage Paging (ROUGH(!!) DRAFT) This is an alternative memory mapping proposal which avoids the complexities of persistent wasm modules as storage while retaining the benefits of memory-mapped...

Personally I feel like it would complicate the design for the bignum library to only contain the arithmetic methods that are not fast enough in wasm. Reducing code duplication is...

I agree with @axic here. Although it's somewhat common in POSIX and other legacy conventions to use `op(dst, src)`, It is far more linguistically intuitive writing `op(src, dst)` when lacking...

I think that deployed contracts could potentially have a flag in the magic number which specifies they are a "library" module. This would override the normal ECI properties and allow...

@DemiMarie I think this issue is out of scope. Ewasm does not intend to make any changes to the WebAssembly specification. Even then, it is up to the implementer of...

@DemiMarie I think this would then be more of a research topic, in that someone should look into whether the major WASM implementations have this optimization. Edit: I am guessing...

I think it doesn't make sense to enforce that unused topic pointers are zero. The implementation of `log` should not be trying to dereference those anyway. On the other hand,...

Meh. I think we should focus fully on the bignum library. Augmenting the WASM spec has a lot of implications and resource requirements that we can't fulfill.

Considering logistics, what changes to existing VM implementations would this require? On Tue, Nov 20, 2018, 11:57 Alex Beregszaszi This came up as a discussion at Devcon 4. I think...