Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix typo. #31

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/DisputeResolutionLayer.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Dispute Resolution Overview

The point of the Dispute Resolution Layer is to provide general purpose tools around building verification games. Verification games are at the very heart of the Truebit protocol. Anytime there is a dispute there between the parties involved in the Truebit system, a verification game is be played to determine fraud. These games can be verifying different things like WASM programs, Scrypt hashes, Merkle Proofs, etc. Howeverm, in most cases the behavior is very similar across different types of games. There are really three main pieces:
The point of the Dispute Resolution Layer is to provide general purpose tools around building verification games. Verification games are at the very heart of the Truebit protocol. Anytime there is a dispute there between the parties involved in the Truebit system, a verification game is be played to determine fraud. These games can be verifying different things like WASM programs, Scrypt hashes, Merkle Proofs, etc. However, in most cases the behavior is very similar across different types of games. There are really three main pieces:

1. Initializing a new game

Expand All @@ -20,4 +20,4 @@ If a Solver is backed into a corner, where they've been narrowed down to two sta

If you want to see our dipsute resolution contract, go [here](https://github.com/TrueBitFoundation/truebit-os/blob/master/contracts/dispute/Interactive.sol)

Users and developers will never to need to worry about the details about this contract because the truebit-os client abstracts these details away.
Users and developers will never to need to worry about the details about this contract because the truebit-os client abstracts these details away.