truebitprotocol / wiki Goto Github PK
View Code? Open in Web Editor NEWClassic source for Truebit documentation
Home Page: https://truebit.io
License: MIT License
Classic source for Truebit documentation
Home Page: https://truebit.io
License: MIT License
Interfaces includes:
This post hasn't been published but it is a good technical summary of how Truebit works. Should be linked in GettingStarted and Overview
Received feedback that current WASM tutorial is hard to follow or distracted
Organize content around the high level architecture:
Incentive Layer
Dispute Resolution Layer
Computation Layer
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!
Determine best practices and tools for open source documentation
Concise summary of the dispute resolution layer, link with repo
Would be helpful if we stated which sections of the Whitepaper the code is implementing across the different repos
Include:
Why Truebit Loves Doge
History of Truebit and how it is related to Dogecoin
Information about the doge bridge
Link relevant resources
Concise summary of computation layer, link relevant code/repos
Document a concise summary of the incentive layer, include link of the repo
We should have the documentation markdown in a /docs
directory. WIth the README acting as a table of contents for the relevant documents
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
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.
@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.
A page dedicated to getting developers started with Truebit Code
Explain the current state of Truebit
Explain architecture vision
Show relevant repos
This is essentially a request for a pull from
to the wiki:
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.
Documentation about our documentation
Make a gitter channel and add link to here
Tutorial updates:
We should have links with a concise explanation to/of any relevant work related to the open source art projects
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
We have some miscellaneous items like
eth-patricia tree
Any open source projects we initiate
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.