gitwtfhub

wtf is treble?

edycutjong/treble — explained in plain English

Analysis updated 2026-05-18

1JavaScriptAudience · developerComplexity · 5/5LicenseSetup · moderate

TL;DR

A serverless football prediction pool where an on-device AI stakes its own cryptocurrency against human players, with no treasurer or cheating possible.

Mindmap

mindmap
  root((repo))
    What it does
      Runs prediction pot
      AI stakes own money
      Enforces tamper proof picks
    Tech stack
      Node.js
      Pear Hypercore
      WDK wallet SDK
      QVAC AI SDK
    Use cases
      Friend group betting pool
      AI vs humans prediction
      Trustless payouts
    Audience
      Hackathon judges
      Developers
      Crypto enthusiasts

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Run a serverless friend group prediction pool where no one holds everyone else's money.

REASON 2

Let an on-device AI stake its own cryptocurrency and compete against human predictions.

REASON 3

Study a working example of tamper-evident, peer to peer consensus using Autobase and Hypercore.

What's in the stack?

JavaScriptNode.jsPearHypercoreWDKQVAC

How it stacks up

edycutjong/treble0xmukesh/docusaurus-tutorial1tsmejp/palworld-docker-wine
Stars111
LanguageJavaScriptJavaScriptJavaScript
Last pushed2021-12-27
MaintenanceDormant
Setup difficultymoderateeasymoderate
Complexity5/52/54/5
Audiencedeveloperdeveloperops devops

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Running the real AI brain downloads a roughly 1GB Qwen3 model via @qvac/sdk on first use, a heuristic fallback runs offline instantly.

Use freely for any purpose, including commercial use, as long as you keep the copyright notice and any stated changes.

Wtf does this do

The Treble is a hackathon project that lets a small group of friends run a football prediction betting pool without a server, a treasurer, or any central authority holding the money, and it lets an AI join the pool as a real participant with its own money and its own set of keys. The project targets a common problem with informal prediction pools: someone has to hold everyone's cash, and everyone has to trust that whoever wrote down each person's pick did not later change it. Instead, every participant, human or AI, holds their own cryptocurrency wallet and stakes their own funds directly. Picks are written to a shared, tamper evident, append only log using peer to peer technology, so once the match starts, no one, including the AI, can edit their prediction. If someone tries, every other peer in the pool rejects the change. The AI participant, nicknamed the Gaffer, reasons about the match using a small AI model that runs directly on the device rather than in the cloud, produces a short written rationale for its prediction, and then stakes its own money using a wallet it controls, all governed by a spending policy that caps how much it is allowed to risk. Importantly, the AI has deliberately less power than the humans: it cannot vote on the final score or lock in the result, only humans can do that, so it cannot manipulate the outcome in its own favor. Once the match result is confirmed by a majority of the human participants, payouts are calculated automatically so that the total amount paid out always equals the total amount staked, with no cut taken by anyone. Every peer involved ends up with an identical copy of the final state, which is how the system stays trustworthy without a central server checking anyone's work. The project is built with JavaScript and Node.js version 20 or later, using peer to peer networking tools alongside a cryptocurrency wallet toolkit and an on device AI toolkit, includes nearly two hundred automated tests, and is released under the Apache 2.0 license. It was built for the Tether Developers Cup hackathon.

Yoink these prompts

Prompt 1
Walk me through running The Treble's demo and understanding the four peer consensus output.
Prompt 2
Explain how The Treble stops the AI pundit from cheating or changing its pick after kickoff.
Prompt 3
How does the WDK Transaction Policy cap limit how much money the AI agent can stake?
Prompt 4
Show me how the QVAC on-device model produces the AI's football prediction rationale.
Prompt 5
What happens in The Treble if a human tries to change their pick after kickoff?

Frequently asked questions

wtf is treble?

A serverless football prediction pool where an on-device AI stakes its own cryptocurrency against human players, with no treasurer or cheating possible.

What language is treble written in?

Mainly JavaScript. The stack also includes JavaScript, Node.js, Pear.

What license does treble use?

Use freely for any purpose, including commercial use, as long as you keep the copyright notice and any stated changes.

How hard is treble to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is treble for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.