Glossary

Synchronization node

syncmode full

The default sync mode. Synchronizes a full Ethereum node using warp synchronization mode by downloading a snapshot of the 30,000 best blocks and the latest state database. Once the snapshot is restored, the client switches to full sync and ancient blocks are synchronized from the network in the background.

Clef

Clef can be used to sign transactions and data and is meant as a replacement for geth’s account management.

Solver

Solvers perform tasks in exchange for TRU rewards. Solvers will run continuously in Truebit OS until stopped, and they will bid to solve each task issued on the network unless initialized with a filter. A filter imposes a minimum TRU reward and/or ratio of reward to blockLimit for participation. Each task has a single Solver, and the Task Submitter always has first right-of-refusal to solve his own task. If the Task Submitter does not elect to solve her own task, then a Solver is selected randomly from among those who register to participate. The client throttle parameter sets the maximum number of tasks that a Solver will process simultaneously.

Verifier

Verifiers also execute tasks, and Verifiers’ solutions must match Solvers’ solutions in order to avoid dispute resolution. There is no limit to the number of Verifiers for each task, and the verifierTax is split equally among them. Verifiers initialized in Truebit OS will run continuously until stopped. As with Solvers, Verifiers can set filters which impose minimum TRU reward and/or ratio of reward to blockLimit for participation. The client throttle parameter sets the maximum number of tasks that a Verifier will process simultaneously.

Task Giver

Task Givers issue computational tasks to the Truebit network. A Task Giver consists of two parts: a Task Owner and a Task Submitter. The Task Owner provides a function f to be computed, some economic and virtual machine parameters (see below), and typically has a smart contract address. The Task Submitter provides applicable input(s) x, pays the TRU token expenses described below, and is a standard, human-operated address. The Task Owner can either deploy a smart contract through which the Task Submitter interacts, or she can submit tasks directly through Truebit OS. In the latter case, the Task Owner and the Task Submitter share an address.

TRU token

The TruebitOS microeconomy features a single token, called TRU, which Task Submitters use to remunerate Solvers and Verifiers. Upon receiving such payments, Solvers and Verifiers can then issue their own tasks. We now dive into macroeconomic details.

Owner Fee

Owner Fee is the amount of TRU that the Task Owner collects from the Task Submitter upon task issuance.

Bonus

This is the payment Solvers and Verifiers are going to receive in case the verification process is successful. For a limited time, Truebit’s incentive layer will automatically subsidize each task with extra TRU payments to its Task Owner, Solver, and Verifier(s). Run the bonus command in Truebit OS to check current subsidy amounts.