odradev/casper-contract-schema

casper-contract-schema's Issues

Storing events

At the moment we store events according to the CES standard. What do we want to do next?

• Should we continue store them in the same way, so we don't break the compatibility with cspr.live? - Should we propose new schema and force cspr.live to update?

Payable

Should we add to the entrypoint definition the information to indicate if it accepts a purse?

Storage layout

Decide if we want to include the storage layout in the schema:

• named keys + types,
• elements of the dictionary with their keys structure + types.

Enums

Define how to represent enums.

WIT as interface definiton.

Bytecode Alliance is working on the extension to WASM's module called components. It's the next big change to the WASM ecosystem. It allows composing multiple WASM binaries into one. Wasmtime already implements it.

For components to work with each other they need an interface. Their standard is called WIT: https://component-model.bytecodealliance.org/design/wit.html.

There is also Rust lib for it: https://docs.rs/witgen/latest/witgen/ and JS: https://github.com/bytecodealliance/ComponentizeJS.

What do you think? Maybe for 2.0?

Prevent plain CLTypes to be events.

It's better/more handy when event's are wrapped in custom types.