Gregor Mitscha-Baude

The "fix" is to use a TURN server. My experience with 4 professional WebRTC projects so far: * Before you have a TURN server: everything works fine on your machine...

Ok, yeah sure I know what it is and I totally get where you're coming from. Just wanted to share my experience ;) FWIW, if the TURN server slows down...

Hi, not directly related but starting from @nazar-pc's work I made a fork of `simple-peer` which has no external dependencies at all: [mitschabaude/simple-peer-light](https://github.com/mitschabaude/simple-peer-light) It's on npm as well: `npm install...

Hi, if this is enough for you, I made a fork of `simple-peer` which is a plain ES module: [mitschabaude/simple-peer-light](https://github.com/mitschabaude/simple-peer-light) It's on npm as `simple-peer-light`.

Hey, I think this language is a great idea! It's exactly what's missing for me in the Wasm ecosystem. My 2 cents: It would be cool if inference of both...

I want to add that I'd be happy to dig into the code and make a PR that fixes this, however I don't know whether it's the wast pipeline or...

@xtuc another thing: I also noticed that the wasm-parser -> wast-printer pipeline generates wast code with "u32" and "u64" instead of "i32", "i64", e.g. the code will contain stuff like...

@shimkiv, to clarify: Does this error also occur if the `to` and `from` fields on the `sendPayment` txns in the mempool do **not** take part in the zkapp deployment (either...

@jasongitmail this would also be fixed by separating the `compile` and `deploy` steps, as proposed here: https://github.com/o1-labs/zkapp-cli/issues/158

Verification key generation in snarkyjs with Izzy's performance improvements will take less than a minute, but more than 10 seconds. I don't think there's a way to avoid it taking...