snek

the wasm c api uses "store" as well: https://github.com/WebAssembly/wasm-c-api/blob/master/include/wasm.h

we already have this (to some degree), it is called a wasi reactor and it uses `_initialize`: https://github.com/WebAssembly/WASI/blob/main/design/application-abi.md#current-unstable-abi

I think making it be on another thread limits implementations, and making it on the same thread eventually becomes something like epoll once you generalize it enough, and of course...

there's also been some light discussion of exposing things like cldr tables and timezone charts in js itself, this could be another push in that direction.

why does this need to exist in wasi? i don't think a standardized api for cryptocurrencies is related to wasi's goals at all.

the thing that is representing a transaction of tokens seems out of place for wasi. crytographic functions to create chained signatures seems like something that could be in a wasi...

ok so how I'm currently thinking about this is like, a js canvas api to draw a line vs a function that draws a histogram. Certainly drawing histograms is useful,...

to be clear, I don't doubt that wasi is valuable to the blockchain, or that this API is valuable to blockchain, I just don't yet understand why this api needs...

fwiw I'm not entirely sure in what context func refs are being used, but you probably don't need to do the weird functions from open() thing. a funcref table is...

If those aren't different enough, I've got an implementation written in js: https://github.com/devsnek/node-wasi/