Nick Hynes

[This is the specification of the IDL.](https://github.com/oasislabs/oasis-rs/blob/master/idl-gen/src/rpc.rs) [Here is an example idl.json](https://github.com/oasislabs/oasis-rs/blob/master/tests/idl_gen/res/TestContract.json) Events are still tbd, but they'll probably look like ```rust pub struct RpcEvent { name: RpcIdent, fields: Vec,...

What, into separate PRs? fuzzing tools and verbosity are atomic, imho. There were no bugs found during fuzzing.

You might want to give [caffegraph](https://github.com/nhynes/caffegraph) a try.

This looks good. Thanks for the PR. I proposed a few modifications around keeping `KeyUse` as an enum so that the [two](https://www.rfc-editor.org/rfc/rfc7517.html#section-4.2) named in the spec are more convenient and...

@joshpowell you might want to give [caffegraph](https://github.com/nhynes/caffegraph) a try. It's not yet as fully featured as loadcaffe (it's missing a few modules), but it will load your resnet just fine.

> i don't think a standardized api for cryptocurrencies is related to wasi's goals at all. Where did I say cryptocurrency? Blockchain is a decentralized computation platform that [benefits greatly...

> crytographic [sic] functions to create chained signatures I don't see how that applies. A `call` in a smart contract platform is just an RPC with value. Unlike the input...

Okay, so imagine a world in which the canvas API were _modular_ and the histogram function were in a plotting module. The plotting module would make it significantly easier for...

> why this api needs to be in the wasi namespace Well, it wasn't meant to be in the namespace any more than the graphics or (eventually) bluetooth modules would...

> We should use wasm's funcRefs directly. And extend WASI's file APIs to be able to store funcRefs like files Neat! I like this idea. Let me try to reiterate...