truebitprotocol / wiki Goto Github PK

Received feedback that current WASM tutorial is hard to follow or distracted

This is essentially a request for a pull from

• https://github.com/smoelius/Developer-Resources.git

to the wiki:

• https://github.com/TrueBitFoundation/Developer-Resources.wiki.git

The proposed changes to the protocol do the following.

• Eliminate the jackpot.

• Convert verifier payments into something better resembling a continuous revenue stream.

There are at least three reasons to motivate eliminating the jackpot.

A first reason is simplicity, as the logic to maintain the jackpot is extremely complex.

A second reason is that the jackpot system results in huge, infrequent, unreliable payments to verifiers. Given the choice, verifiers would likely prefer smaller, more frequent, more reliable payments.

A third reason is that the jackpot's exponential decrease rule could potentially be weaponized, as demonstrated by the next example. Suppose there are two verifiers, BigGuy and LittleGuy. Suppose BigGuy is well-established and has capital to burn. Suppose LittleGuy is a newcomer and is barely staying afloat. Then BigGuy could submit extra verification bids every time LittleGuy submits a verification bid. In this way, BigGuy would dilute LittleGuy's payments and potentially squeeze LittleGuy out of the verification market.

I apologize if the proposed changes resemble something that has already been considered, or if they suffer from some obvious flaw.

Would be helpful if we stated which sections of the Whitepaper the code is implementing across the different repos

We should have links with a concise explanation to/of any relevant work related to the open source art projects

Concise summary of the dispute resolution layer, link with repo

Document a concise summary of the incentive layer, include link of the repo

Organize content around the high level architecture:

Incentive Layer
Dispute Resolution Layer
Computation Layer

Make a gitter channel and add link to here

The link currently goes here:
https://github.com/TrueBitFoundation/wiki/blob/master/open-problems.md

which is essentially empty. Should it instead point to this link?
https://github.com/TrueBitFoundation/wiki/wiki/Open-Problems

The last documentation reorganization was beneficial. In the jam session you guys discussed adding a better overview of truebit's repos. It would be nice if an overview could be added that focused on the source language and runtime environment of each repo.

For example, specifying that the incentive layer is primarily Solidity contracts would indicate that the source is run entirely on-chain. OCaml, of course, runs off-chain.

The real advantage is with wasm. It took me a while to wrap my head around the fact that wasm is the only code that runs both on-chain, on top of Solidity code, and off-chain, on top of OCaml code. With three languages involved simultaneously this can get confusing. Throw in C and Rust, that compile to wasm and are run on top of Solidy and OCaml interpreters, and you can see the friction in comprehending how these pieces all fit together.

Documentation about our documentation

A page dedicated to getting developers started with Truebit Code

Explain the current state of Truebit
Explain architecture vision
Show relevant repos

Determine best practices and tools for open source documentation

Tutorial updates:

1. Improve tutorial (readme) documentation
   a. Testing out tutorial and getting user feedback on common error
   b. Hold small demo sessions on running truebit OS and issuing tasks
   c. Ensure onboarding steps for primary user (ETH developers) is clear and errors minmized
   d. Direct users to Gitter for technical support
2. Review incentive layer and network economics
   a. Model and review economic incentive for individual ecosystem actors
   b. Produce short Medium explainer on network ecomics
3. General communication
   a. Create short Medium article version of the Truebit tutorial after #1 has been finalized.

Interfaces includes:

• command line interfaces and clients
• Interfaces between layers (incentive, dispute resolution, and off-chain computation layer)

This post hasn't been published but it is a good technical summary of how Truebit works. Should be linked in GettingStarted and Overview

We should have the documentation markdown in a /docs directory. WIth the README acting as a table of contents for the relevant documents

Concise summary of computation layer, link relevant code/repos

Truebit's verification mechanism is an interactive proof (the verification game). Interactive Proof is a larger research field that includes Truebit.

It would be helpful to introduce some of the ideas behind interactive proofs and summarize historical research

https://en.wikipedia.org/wiki/Interactive_proof_system

@OR13 asked about this in our gitter. We have a few examples of merkle proofing computation steps in ocaml-offchain, dispute-resolution-layer simple adder vm, and scrypt interactive.

Considering this is rather generic idea that applies to any instance of a truebit like system it would be great to have a nice write up on this.

Hey, do you have any supporting research on verification games, second layer scaling, or off-chain verification? I think it'd help add to the background of your project. Thanks!

We have some miscellaneous items like

eth-patricia tree

Any open source projects we initiate

Include:
Why Truebit Loves Doge
History of Truebit and how it is related to Dogecoin
Information about the doge bridge
Link relevant resources