Sina Habibian

WebAssembly in Blockchains

7

WebAssembly is finding a home within blockchains. As a non-web platform, blockchains have distinct requirements. We have compiled notes from projects across the space ([Ethereum](https://www.ethereum.org/), [Parity](https://www.parity.io/), [Dfinity](https://dfinity.org/), and [Truebit](https://truebit.io/)), and...

I unsuccessfully tried running a .wasm file using the interpreter. The error messages could be more helpful. I then tried running the .js file using our `emscripten-module-wrapper` and got more...

Implement the verifier monitoring fix (proposed in the white paper addendum)

2

To prevent the monitoring attack, “the protocol must prevent Verifiers from revealing which task they are challenging until the final phase of the protocol.” [[white paper addendum, page 42]](http://people.cs.uchicago.edu/~teutsch/papers/truebit.pdf). Verifiers...

Travis is currently failing due to Postgres. Builds [here](https://travis-ci.org/TrueBitFoundation/scrypt-interactive/builds/350849684).

The logging level should maybe be determined based on an ENV variable. could call it something like `LOG_LEVEL` like rails does.

This [method](https://github.com/TrueBitFoundation/scrypt-interactive/blob/master/contracts/Verifier.sol#L209) allows the client to end verification games.

Run security audit

2

Using this as an ongoing issue to keep track of points for a future security audit.

One point: check whose turn it is in a verification game, potentially by comparing `lastClaimangeMessage` and `lastChallengerMessage` on `scryptVerifier`.

Following up on discussion with Oscar, let's set minDeposit as `0.001 ETH`, and timeout as `5 blocks`.

E.g. when a challenger defeats a claimant, all next challengers need to unbond their deposits.