Open poemm opened 4 years ago
I'd say let's change envaddr
either to address
or contract
or a combination, get rid of EE terminology. Also rename timeslots
to blocks
?
The version I use locally is the following:
beacon_state:
execution_scripts:
- scripts/helloworld/target/wasm32-unknown-unknown/release/phase2_helloworld.wasm
shards:
- id: 0
pre_states:
- "0000000000000000000000000000000000000000000000000000000000000000"
transitions:
- env: 0
data: ""
post_states:
- "0000000000000000000000000000000000000000000000000000000000000000"
depost_receipts:
The following is a proposed sample yaml file which supports both shards ids and environment addresses. (I should write a schema, which yaml schema definition language is preferred?)
Before I extend C, C++, and Python Scout yaml parsers, I am soliciting feedback.
This is a dependency to test shard-aware host functions proposed here https://github.com/ewasm/scout/issues/38 .