[{"_1":2,"_160":-5,"_161":-5},"loaderData",{"_3":4,"_17":18,"_25":26,"_139":140},"root",{"_5":-5,"_6":-7,"_7":8,"_9":-7,"_10":11,"_12":-7,"_13":14,"_15":16},"currentUser","primaryEmail","siteVerification","6LeIxAcTAAAAAJcZVRqyHh71UMIEGNQ_MXjiZKhI","toast","enableDev",false,"incidentStatus","theme","system","contrast","normal","routes/_layout",{"_19":-5,"_20":21,"_22":21,"_23":11,"_24":21},"username","isAskGordonEnabled",true,"isUsingNewTemplate","showMinimalLanding","showHoneypotTrap","routes/_layout.r.$namespace.$reponame",{"_27":28,"_29":-5,"_30":11,"_31":11,"_32":33,"_34":35,"_36":-5,"_37":11,"_38":39,"_88":-5,"_89":90,"_128":-5,"_129":11,"_130":21,"_131":11,"_132":-5,"_133":11,"_134":-5,"_135":136,"_137":91,"_138":-7},"canonicalUrl","https://hub.docker.com/r/truja/truebit-beta/tags","mcpServer","canSeeDockerfile","canSeeAutobuilds","namespace","truja","reponame","truebit-beta","cloudBuildSource","isAutobuildsAvailable","repo",{"_40":41,"_42":43,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":55,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":74,"_79":11,"_80":81,"_85":33,"_86":87},"categories",[],"content_types",[44],"image","date_registered","2020-09-14T04:11:36.749792Z","description","","is_private","last_updated","2020-10-21T05:30:13.45264Z","last_modified","2024-10-16T13:48:34.145251Z","media_types",[56],"application/vnd.docker.container.image.v1+json","name","pull_count",338,"repository_type","star_count",0,"status",1,"status_description","active","source","collaborator_count","full_description","

\n \n

\n\n[![Docker Image](https://img.shields.io/docker/cloud/build/truja/truebit-beta)](https://hub.docker.com/r/truja/truebit-beta)\n\n# What is Truebit?\n[Truebit](https://truebit.io/) is a blockchain enhancement which enables smart contracts to securely perform complex computations in standard programming languages at reduced gas costs. As described in the [whitepaper](https://people.cs.uchicago.edu/~teutsch/papers/truebit.pdf) and this graphical, developer-oriented [overview](https://medium.com/truebit/truebit-the-marketplace-for-verifiable-computation-f51d1726798f), Task Givers can issue computational tasks while Solvers and Verifiers receive remuneration for correctly solving them.\n\nThis comprehensive Ethereum implementation includes everything you need to create (from C, C++, or Rust code), issue, solve, and verify Truebit tasks. This repo includes the Truebit-OS command line [client](https://github.com/TrueBitFoundation/truebit-eth/tree/master/wasm-client) for solving and verifying tasks, [WASM ports](https://github.com/TrueBitFoundation/truebit-eth/tree/master/wasm-ports) and [Emscripten module wrapper](https://github.com/TrueBitFoundation/truebit-eth/tree/master/emscripten-module-wrapper) for generating them, the [off-chain interpreter](https://github.com/TrueBitFoundation/truebit-eth/tree/master/ocaml-offchain), as well as [sample tasks](##Sample-tasks-via-smart-contracts). You can install Truebit using Docker or build it from source for Linux, MacOS, or Windows.\n\nFeel free to browse the [legacy wiki](https://github.com/TrueBitFoundation/wiki), contribute to this repo's wiki, or check out these classic development blog posts:\n* [Developing with Truebit: An Overview](https://medium.com/truebit/developing-with-truebit-an-overview-86a2e3565e22)\n* [Using the Truebit Filesystem](https://medium.com/truebit/using-the-truebit-filesystem-f6a5d4ac9604)\n* [Truebit Toolchain & Transmute](https://medium.com/truebit/truebit-toolchain-transmute-4984928364a7)\n* [Writing a Truebit Task in Rust](https://medium.com/truebit/writing-a-truebit-task-in-rust-6d96f2ee0a4b)\n* [JIT for Truebit](https://medium.com/truebit/jit-for-truebit-e5299afc72d8)\n\nIn addition, Truebit's [reddit](https://www.reddit.com/r/truebit/) channel features links to some excellent introductions and mainstream media articles about Truebit. If you'd like to speak with developers working on this project, come say hello on Truebit's [Gitter](https://gitter.im/TrueBitFoundation/Lobby) channel.\n\n# Table of contents\n1. [Quickstart guide: computational playground](#Quickstart-guide-computational-playground)\n2. [Solve and verify tasks](#Solve-and-verify-tasks)\n3. [Getting data into and out of Truebit](#Getting-data-into-and-out-of-Truebit)\n4. [Building your own tasks with the Truebit toolchain](#Building-your-own-tasks-with-the-Truebit-toolchain)\n5. [Native installation](#Native-installation)\n6. [Contract API reference](#Contract-API-reference)\n\n# Quickstart guide: computational playground\n\nThis tutorial demonstrates how to install Truebit, connect to Görli or Ethereum mainnet networks, solve, verify and issue tasks, and finally build your own tasks. Use the following steps to connect to the Görli testnet blockchain and solve tasks with your friends!\n\n## Install or update Truebit OS\n\nFollow the following steps to run a containerized Truebit OS client for Solvers, Verifiers, and Task Givers on any Docker-supported system. Docker provides a replicable interface for running Truebit OS and offers a streamlined installation process. First, download and install [Docker](https://docs.docker.com/get-docker/). Then run the following at your machine's command line.\n```bash\ndocker pull truja/truebit-beta:latest\n```\n\n## Docker incantations\n\nBuilding the image above will take some minutes, but thereafter running the container will give an instant prompt. While you are waiting for the image download to complete, familiarize yourself with the following three command classes with which you will access the Truebit network.\n\n### \"Start container\"\n\nWe first open a new container with two parts:\n\n1. **Truebit OS**. Solvers and Verifiers can solve and verify tasks via command-line interface.\n\n2. **Truebit Toolchain**. Task Givers can build and issue tasks.\n\nSelect a directory where you wish to store network cache and private keys. For convenience, we let `$YYY` denote the *full path* to this directory. To get the full path for your current working directory in UNIX, type `pwd`. For example, if we wish to place the files at `\\Users\\Shared`, we would write\n```bash\nYYY='/Users/Shared'\ndocker run --network host -v $YYY/docker-geth:/root/.ethereum -v $YYY/docker-ipfs:/root/.ipfs --rm -it truja/truebit-beta:latest /bin/bash\n```\nDocker will then store your Geth and IPFS files configuration files in the directories`docker-geth` and `docker-ipfs` respectively. The incantation above avoids having to synchronize the blockchain and your accounts from genesis and also stores your IPFS \"ID\" for better connectivity when you later restart the container.\n\n### \"Open terminal window\"\n\nWhen you [connect to the network](###Connect-to-the-network), you will need to open multiple windows *in the same Docker container*. Running Geth or IPFS locally or in a different container from Truebit OS will not work. When it is time to open a new terminal window for your existing container, find the name of your container running `truja/truebit-beta:latest` by using `docker ps`, open a new local terminal window and enter the following at the command line.\n```bash\ndocker exec -it _yourContainerName_ /bin/bash\n```\n_yourContainerName_ might look something like `xenodochial_fermat`. If you instead wish to run all processes in a single terminal window, initiate `tmux` and create sub-windows by typing `ctrl-b \"` or `ctrl-b %` and using `ctrl-b (arrow)` to switch between sub-windows.\n\nYou can share files between your native machine and the Docker container by copying them into your `docker-geth` or `docker-ipfs` folders. Alternatively, you may copy into (or out of) the container with commands of the following form.\n```bash\ndocker cp truebit-eth/supersecret.txt f7b994c94911:/docker-geth/supersecret.txt\n```\nHere `f7b994c94911` is the name of the container's ID. To exit a container, type `exit`. Your container process will remain alive in other windows unless you exited the original window which initiated with the `--rm` flag.\n\n### \"Connect to the network\"\n\nOne must simultaneously run [Geth](https://geth.ethereum.org/) and [IPFS](https://ipfs.io/) in order to communicate with the blockchain and data infrastructures. When you start up a new Truebit container, start IPFS in the background and configure the compiler with the following pair of commands (in this order).\n```bash\nsource /emsdk/emsdk_env.sh\nbash startup.sh\n```\nYou can terminate IPFS at any time by typing `ipfs shutdown`.\n\nGeth requires a more nuanced setup relative to IPFS. Below we'll connect to Truebit on the Görli testnet. As we shall see, connecting to Ethereum mainnet is quite similar. Truebit OS automatically detects which blockchain network Geth is connected to (Görli testnet or Ethereum mainnet).\n\n#### Initializing accounts\n\nIf you don't already have a local Görli account in your Docker container, create a new one inside the Docker container with the following command.\n```bash\ngeth --goerli account new\n```\nGeth will prompt you for an account password. You may wish to create more than one account. Paste each of your account passwords on separate lines, in order, into a text file. Drop this text file into your `docker-geth` folder. For example, your password file might have the name `supersecret.txt` and might look something like this:\n```\ntruebit\ntask\nsolve\nverify\n```\nFinally, fund your accounts! You can obtain Görli ETH from one of the faucets below, or send your accounts ETH from your favorite wallet (e.g. [Metamask](https://metamask.io/) or [MyCrypto](https://mycrypto.com/)).\n\nhttps://goerli-faucet.slock.it/\n\nhttps://faucet.goerli.mudit.blog/\n\n#### Connecting with Geth\n\nIn your Truebit Docker container, connect your account(s) to the Görli network using an incantation of the following form:\n```bash\ngeth --goerli --rpc --unlock \"0,1,2,3\" --password /root/.ethereum/supersecret.txt --syncmode \"light\" --allow-insecure-unlock console\n```\nHere `0,1,2,3` denotes the indices of the accounts you wish to use with Truebit OS. If we wanted to connect to mainnet instead of Görli, we would simply delete the term `--goerli` in the incantation above. Your Geth client should now begin syncing with the network and be up to date within a minute. If you are have trouble connecting to a light client peer, try the following.\n\n1. Exit `geth` (`Ctrl-C` or `exit`) and re-run the `geth` incantation above.\n\n2. Try running Truebit OS [natively](##Running-Truebit-OS-natively) instead of using Docker.\n\n3. Change your IP address.\n\n4. Reconnect later, or consider running a full Ethereum node.\n\nTo view a list of connected addresses inside the `geth console`, type `personal.listWallets` at the Geth command line.\n\n# Solve and verify tasks\n\nWe are now ready to run Truebit Solver and Verifier nodes. If you haven't already, [\"start container\"](###Start-container) and [\"connect to the network\"](###Connect-to-the-network). Now use the [\"open terminal window\"](###Open-terminal-window) incantation to connect to your Docker container in a terminal window separate from Geth. Then start Truebit OS! \n```bash\ncd truebit-eth\n./truebit-os\n```\nYou should now see a new shell prompt.\n```\nTHIS SOFTWARE IS PROVIDED \"AS IS\" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. YOU MAY NOT MODIFY, REVERSE ENGINEER, DISASSEMBLE, DECOMPILE, OR ATTEMPT TO DERIVE THIS FILE'S SOURCE CODE.\n _____ _ _ _ \n |_ _| _ __ _ _ ___ | |__ (_) | |_ _\n | | | '__| | | | | / _ \\ | '_ \\ | | | __| (_)\n | | | | | |_| | | __/ | |_) | | | | |_ _\n |_| |_| \\__,_| \\___| |_.__/ |_| \\__| (_)\n\n _ _ _ _ __ \n | |_ __ _ ___| | __ ___ ___ | |_ _____ __ _____ _ __(_)/ _|_ _\n | __/ _` / __| |/ / / __|/ _ \\| \\ \\ / / _ \\ \\ \\ / / _ \\ '__| | |_| | | |\n | || (_| \\__ \\ < \\__ \\ (_) | |\\ V / __/ \\ V / __/ | | | _| |_| |\n \\__\\__,_|___/_|\\_\\ |___/\\___/|_| \\_/ \\___| \\_/ \\___|_| |_|_| \\__, |\n |___/\n\n[10-17 22:40:48] info: Truebit OS 1.0.6 has been initialized on goerli network at block 3594922.\n```\nNote that you must be connected to either Görli testnet or Ethereum mainnet in order to execute commands in Truebit OS. You may see error messages at this point if your local node has not yet synchronized with the blockchain or is not connected to a suitable peer (e.g. `Error: Invalid JSON RPC response: \"Error: connect ECONNREFUSED 127.0.0.1:8545` ... or `error: no suitable peers available`). If this happens, quit and restart.\n\nFor a self-guided tour or to explore additional options not provided in this tutorial, type `help` at the command line, and (optionally) include a command that you want to learn more about. Here is a list of available commands:\n```\nhelp [command...] Provides help for a given command.\nexit Exits application.\naccounts List available network accounts.\nbalance [options] Show account balances.\nbonus Display current per task bonus payout.\ngas [options] Check or set gas price.\nipfs [options] Manage IPFS nodes.\nlicense [options] Obtain a Solver license.\nps List active Solvers and Verifiers along with their games and tasks.\nstart [options] Start a Solver or Verifier.\nstop Stop a Solver or Verifier. Get process numbers with 'ps'.\ntask [options] Submit a task or run a utility.\ntoken [options] Swap ETH for TRU. Deposit to or withdraw from incentive layer.\nversion Display Truebit OS version.\n```\n\n## Staking tokens\n\nIn order to start a Solver or Verifier, one must first stake TRU into Truebit's incentive layer. Let's purchase 1000 TRU tokens for account 0. Check the price using `token price`, then\n```sh\ntoken purchase -v 1000 -a 0\n```\nNow we can stake some of our TRU.\n```sh\ntoken deposit -v 500 -a 0\n```\nWe can repeat this process for account 1, if desired. We are ready to start a Verifier, but if we wish to run a Solver, there is one additional step. We must purchase a Solver license with ETH. Check the price using `license price`, then\n```sh\nlicense purchase -a 0\n```\nFinally, we can confirm account balances for ETH and TRU and the amount of TRU we have staked in Truebit's incentive layer.\n```sh\nbalance -a 0\n```\nIt is recommended, but not required, to run each Solver or Verifier node in a separate terminal window from a distinct account.\n\n## Running Solvers and Verifiers\n\nWe can now start our Solver and Verifier as follows.\n```sh\nstart solve -a 0\nstart verify -a 1\n```\nIf the Solver and Verifier do not immediately find a task on the network, try issuing a sample task yourself.\n```sh\ntask -f factorial.json submit -a 0\n```\nThe Task Submitter address always has first right-of-refusal to solve its own task, so your Solver should pick this one up! You can check progress of your Görli task here:\n\n\n\nYour Solver and Verifier will continue to solve and verify new tasks until a `stop` command is issued (e.g. `stop 1`) or you `exit` Truebit OS. Use `ps` to identify the appropriate process index. If you lose Internet connectivity while your deposit is bonded to a task, try restarting in recovery mode. For example,\n```sh\nstart solve -r 20\n```\nwill initialize a new Solver 20 blocks behind the current block and recover the intermediate events.\n\n## Faster IPFS uploads and downloads\n\nIPFS's peer-to-peer network can route data more efficiently when it knows where to find Truebit Task Submitters, Solvers, and Verifiers. It is recommended to register your IPFS node with Truebit via the following command which makes it easier for others to find your node while you are issuing or solving tasks:\n```sh\nipfs register\n```\nYou can then discover other nodes on Truebit's network by running:\n```sh\nipfs connect\n```\nIf your node didn't successfully connect to peers, try again in a few minutes. It takes some time for new addresses to propagate. Note that some registered nodes may be offline.\n\n## Logging sessions and command line execution\n\nThe vanilla `./truebit-os` command generates a file `combined.log.json` containing a .json log spanning across all Truebit OS terminals but does not include everything displayed on the terminal screens. You can inspect this log as follows:\n```bash\ncat /truebit-eth/combined.log.json | more\n```\nIt is safe to delete this file.\n\nIf one wishes to record a more detailed log for a Truebit OS interactive session, one can use a command of the following form to record the full terminal output:\n```bash\n./truebit-os 2>&1 | tee mylog.txt\n```\nOne can also execute Truebit OS commands directly from the native (Docker) command line using a `-c` flag. For example, try:\n```bash\n./truebit-os -c \"start solve -a 1\" --batch > mylog.txt 2>&1 &\n```\nHere the `--batch` flag tells Truebit OS to run non-interactively, and `> mylog.txt 2>&1 &` tells Truebit OS to write the output to a log file called `mylog.txt` rather than the terminal. The command above will return a process number at the command line (e.g. `[1] 412`). You can stop the Solver process later using the `kill` command, (e.g. `kill 412`). The following Unix shell command will return a list of active Truebit processes from all windows.\n```bash\nps a\n```\n\n## Client configuration\n\nIn the `/truebit-eth/wasm-client/` directory, you will find a file called `config.json` which looks something like this.\n```json\n{\n \"http-url\": \"http://localhost:8545\",\n \"ipfs\": {\n \"host\": \"localhost\",\n \"port\": \"5001\",\n \"protocol\": \"http\"\n },\n \"gasPrice\": 20.1,\n \"throttle\": 3,\n \"incentiveLayer\": \"incentiveLayer\"\n}\n```\nWhen running on Ethereum mainnet, you may wish to modify the `gasPrice` parameter to increase the chances that Ethereum miners will process your Truebit OS transactions or to economize on ETH. Every Ethereum transaction invokes some ETH gas cost, and price per unit gas is given in [gwei](https://ethdocs.org/en/latest/ether.html). The `gasPrice` can be set within Truebit OS. For example,\n```sh\ngas set -v 47.3 --default\n```\nwill set the running client gas price to 47.3 gwei, and the optional `--default` flag tells Truebit OS to write to `config.json` above so that this value becomes the starting `gasPrice` the next time you start Truebit OS. Beware that in Ethereum's capricious DeFi environment, gas prices can fluctuate wildly. Use the following command to get a real-time, suggested range of gas prices on mainnet.\n```sh\ngas check\n```\nOn Görli, a `gasPrice` of 1 gwei may suffice.\n\nThe `throttle` parameter above is the maximum number of simultaneous tasks that your Solver or Verifier will process. `http-url` and `ipfs` must match the network settings for Geth and IPFS. Do not change `incentiveLayer` as Truebit currently only supports a single incentive layer.\n\nYou must restart Truebit OS for configuration changes to take effect. For editing convenience and to save your changes to the next [\"start container\"](###Start-container), you may wish to add a volume to your Docker run incantation, e.g. `-v $YYY/wasm-client:/truebit-eth/wasm-client`.\n\n\n# Getting data into and out of Truebit\n\nTruebit can read and write data to three file types.\n\n0. **BYTES.** These are standard Ethereum bytes stored in Truebit's filesystem smart contract. Note that Truebit does *not* read data from arbitrary smart contracts.\n\n1. **CONTRACT.** This method uses a smart contract whose program code consists of the task data itself. This is not a typical contract deployment as the contract may not function.\n\n2. **IPFS.** Truebit can read and write to IPFS, a peer-to-peer, content-addressed storage system.\n\nEthereum has a limit of 5 million gas per contract deploy (~ 24 kilobytes) and roughly the same limit for other transactions. This means that larger files should always sit on IPFS.\n\n## Writing task outputs via Truebit OS\n\nLet's inspect a sample task meta file called `reverse.json` which can be found in the `/truebit-eth` directory:\n```json\n{\n \"codeFile\": {\n \"path\": \"/data/reverse_alphabet.wasm\",\n \"fileType\": \"IPFS\"\n },\n \"dataFiles\": {\n \"/data/alphabet.txt\": \"CONTRACT\",\n \"/data/reverse_alphabet.txt\": \"BYTES\"\n },\n \"outputs\": {\n \"reverse_alphabet.txt\": \"BYTES\"\n },\n \"solverReward\": \"2\",\n \"verifierTax\": \"6\",\n \"minDeposit\": \"10\",\n \"stackSize\": \"14\",\n \"memorySize\": \"20\",\n \"globalsSize\": \"8\",\n \"tableSize\": \"8\",\n \"callSize\": \"10\",\n \"blockLimit\": \"1\"\n}\n```\nYou can experiment with its filesystem configuration by adjusting parameters below.\n\n1. `codeFile`. This keyword specifies the compiled code that the Task Giver wishes to execute. Truebit OS automatically detects code type based on the code file extension (.wasm or .wast), however the Task Giver must specify a file type for the code (BYTES, CONTRACT, or IPFS) telling Solvers and Verifiers where to find it. Each task has exactly one `codeFile`.\n\n2. `dataFiles`. All input and output files for the task program must be listed under this keyword, and each must have a file type (BYTES, CONTRACT, or IPFS).\n\n3. `outputs`. The value(s) here are the subset of the data files which are produced and uploaded by the Solver. In this example both the empty data file `/data/reverse_alphabet.txt` and the corresponding output file `reverse_alphabet.txt` have the same file type (BYTES), however in general they need not match.\n\n4. `solverReward`, `verifierTax`, and `minDeposit` pertain to task economics. The `solverReward` is the reward paid to the Solver for a correct computation, the `verifierTax` is the fee split among Verifiers, and `minDeposit` is the minimum unbonded deposit that Solvers and Verifiers must have staked in the Incentive Layer in order participate. Note that the Task Owner's fee is automatically 0 since the Task Submitter is always the Task Owner when deploying from Truebit OS.\n\nIn a typical Ethereum deployment, the *Task Owner* is the Dapp smart contract that sends a task to Truebit which in turns calls back with a solution. The *Task Submitter* is always a regular (i.e. human-controlled) blockchain address that initiates the task and pays for it.\n\n5. `stackSize`, `memorySize`, `globalsSize`, `tableSize`, and `callSize`. These are virtual machine parameters. You may need to tweak `memorySize` when you create your own task.\n\n6. `blockLimit`. This is the length of time (in blocks) for which Solvers and Verifiers will attempt to run the task before reporting a timeout.\n\nTo run this example, enter the following commands in Truebit OS.\n```sh\nstart solve\ntask -f reverse.json submit\n```\n\n## Sample tasks via smart contracts\n\nIn general, Dapps will issue tasks from smart contracts rather than the Truebit OS command line. This allows Truebit to call back to the smart contract with a Truebit-verified solution. Typically the Task Owner smart contract fixes the task function code during deployment while the Task Submitter puts forth the function inputs at runtime. To demonstrate this method, we deploy and issue some tasks that are preinstalled in your container. One can deploy each of the samples onto the blockchain as follows.\n```bash\ncd wasm-ports/samples\nsh deploy.sh\n```\nTo run a sample task, `cd` into that directory and run `node send.js` as explained below. You may wish to edit `../deploy.js` or `send.js` by replacing the '`0`' in `accounts[0]` with the index of your desired Geth account. \n\n### Scrypt\n```bash\ncd /wasm-ports/samples/scrypt\nnode send.js \n```\nComputes scrypt. The string is extended to 80 bytes. See the source code [here](https://github.com/TrueBitFoundation/truebit-eth/blob/master/wasm-ports/samples/scrypt/scrypthash.cpp). Originally by @chriseth.\n\n### Bilinear pairing\n```bash\ncd /wasm-ports/samples/pairing\nnode send.js \n```\nFor ``, enter a string with more than 32 characters. This example uses the `libff` library to compute bilinear pairings for a bn128 curve. It reads two 32 byte data pieces `a` and `b` which are used like private keys to get `a*O` and `b*O`. Then a bilinear pairing is computed. The result has several components, and one of them is posted as output. (To be clear, the code just shows that `libff` can be used to implement bilinear pairings with Truebit).\nSee the source code [here](https://github.com/TrueBitFoundation/truebit-eth/blob/master/wasm-ports/samples/pairing/pairing.cpp).\n\n### Chess\n```bash\ncd /wasm-ports/samples/chess\nnode send.js \n```\nThis example checks moves in a game of chess. Players could use a state channel to play a chess match, and if there is a disagreement, then the game sequence can be posted to Truebit. This method will always work for state channels because both parties have the data available. See the source code [here](https://github.com/TrueBitFoundation/truebit-eth/blob/master/wasm-ports/samples/chess/chess.cpp).\nThe source code doesn't implement all the rules of chess, and is not much tested.\n\n### Validate WASM file\n```bash\ncd /wasm-ports/samples/wasm\nnode send.js \n```\nUses `parity-wasm` to read and write a WASM file. See the source code [here](https://github.com/TrueBitFoundation/truebit-eth/blob/master/wasm-ports/samples/wasm/src/main.rs).\n\n### Size of video packets in a file\n```bash\ncd /wasm-ports/samples/ffmpeg\nnode send.js input.ts\n```\nSee the source code [here](https://github.com/mrsmkl/FFmpeg/blob/truebit_check/fftools/ffcheck.c).\n\n# Building your own tasks with the Truebit Toolchain\nIf you haven't already, from your Truebit container, run the following commands (in order):\n```bash\nsource /emsdk/emsdk_env.sh\nbash startup.sh\n```\nYou should now be able to compile the sample tasks yourself in C++ (chess, scrypt, pairing), and C (ffmpeg) below.\n```bash\ncd /truebit-eth/wasm-ports/samples/chess\nsh compile.sh\ncd ../scrypt\nsh compile.sh\ncd ../pairing\nsh compile.sh\ncd ../ffmpeg\nsh compile.sh\n```\nFor Rust tasks, take a look @georgeroman's [workaround](\nhttps:","has_starred","hub_user","immutable_tags_settings",{"_75":11,"_76":77},"enabled","rules",[78],".*","is_automated","permissions",{"_82":21,"_83":11,"_84":11},"read","write","admin","user","storage_size",26783343047,"orgData","recentTags",[91],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":100,"_50":117,"_118":94,"_119":33,"_120":56,"_57":121,"_122":123,"_124":108,"_125":117,"_126":66,"_127":21},"content_type","creator",5396116,"full_size",3376388685,"id",121256434,"images",[101],{"_102":103,"_104":105,"_106":48,"_107":108,"_109":110,"_111":112,"_113":48,"_114":-5,"_115":96,"_63":66,"_116":-5},"architecture","amd64","digest","sha256:09549455ec9e5b94fddf1dba7aa316a0e87e95535be82b3eb52c685cae49e6a7","features","last_pulled","2026-10-05T05:14:43.579699887Z","last_pushed","2020-10-21T05:30:13Z","os","linux","os_features","os_version","size","variant","2020-10-21T05:30:12.803008Z","last_updater","last_updater_username","media_type","latest","repository",9826840,"tag_last_pulled","tag_last_pushed","tag_status","v2","sbxKitMetadata","isPotentialSpam","isHubSbxKitsEnabled","showSbxLogoOverride","sbxTrademarkText","displaySecurityMetadata","tagAttestations","tagsHaveAttestations",[],"selectedTag","attestationsUrl","routes/_layout.r.$namespace.$reponame.tags",{"_38":141,"_148":149,"_135":158,"_159":11},{"_40":142,"_42":143,"_45":46,"_47":48,"_49":11,"_50":51,"_52":53,"_54":144,"_57":35,"_32":33,"_58":59,"_60":44,"_61":62,"_63":64,"_65":66,"_67":-5,"_68":62,"_69":70,"_71":11,"_72":33,"_73":145,"_79":11,"_80":147,"_85":33,"_86":87},[],[44],[56],{"_75":11,"_76":146},[78],{"_82":21,"_83":11,"_84":11},"tags",{"_150":64,"_151":-5,"_152":-5,"_153":154},"count","next","previous","results",[155],{"_92":44,"_93":94,"_95":96,"_97":98,"_99":156,"_50":117,"_118":94,"_119":33,"_120":56,"_57":121,"_122":123,"_124":108,"_125":117,"_126":66,"_127":21},[157],{"_102":103,"_104":105,"_106":48,"_107":108,"_109":110,"_111":112,"_113":48,"_114":-5,"_115":96,"_63":66,"_116":-5},[],"canDeleteTags","actionData","errors"]

truja/truebit-beta

Tags for truja/truebit-beta