Tipster or syndicate? Prove your edge without showing a pick, and earn from the profit it makes.Earn from your edge. →
Open source

The parts you have to trust are the parts you can read.

Open source does not make a betting edge public. It makes the parts that touch your money and your proof readable: the Agent, the protocol it speaks, and the verifier that checks our work. The table below says where each part stands.

Repositories

The Agent, the Originator Kit, the protocol and the verifier are public on GitHub.

Open

  • The Manometer Agent. The program that places the bets, including what it reports to us.
  • The protocol. Proposal contract v1, sealing, receipts, scorecard bundles.
  • The verifier. Byte-identical copies of the referee's own scoring modules.
  • The scoring formulas. Devig, closing-line value, EV honesty, uniqueness, paper settlement.
  • Bookmaker adapters as part of the Agent.

Closed, on purpose

  • The fair-price service and the merge of more than 90 bookmakers.
  • Name matching and its alias database.
  • Signal routing across the network.

This is the moat. None of it is needed to check our numbers.

Release 1

What ships, under which licence, and where it stands.

All of it is built and runs today. The public copies are cleaned: no secrets, no account data, no history. All four are public.

ComponentWhat it isLicenceStatus
manometer-verify1.0.2Checks a scorecard bundle without our servers: receipts, seals, prices, results, bundle root.Apache-2.0public
Protocolcontract v1Proposal contract, market taxonomy, lifecycle, sealing, receipts, scorecard bundles.open specificationpublished
Originator kit1.0.1Seal and send proposals from a browser or from Node, with the catalogue of games and drand rounds.Apache-2.0public
Manometer Agent2.0.6The program that places the bets: placement, read-back, limits, reports. With a developer guide.AGPL-3.0public
AdaptersBookmaker adapters, as part of the Agent.AGPL-3.0with the Agent

AGPL for the Agent means that anyone who runs a modified version as a service has to publish it. The Manometer name and logo are not covered by any of the licences.

Ready for release 1

Open source is only worth something if you can tie it to what you installed.

So every Agent release comes with what you need to check that the program you run is the program in the repository.

Signed builds

Every Agent release is source, checksums and a signature. A small script compares what you installed with the published release, file by file.

What it sends home

One file in the source, PHONE_HOME.md, lists every message the Agent sends and to whom, your balances included. You can read exactly what leaves your machine.

Tests on every commit

Each repository has its own tests, set up to run on every change. A release needs every test green.

Security reports

The Agent had its first security review, and vulnerabilities have a private channel.

Contributions

Developer Certificate of Origin for every contribution, code owners for the sensitive parts, clear rules for issues.

Governance

The repositories start under Manometer and can move to an independent association once there is a community to govern.

The honest limit

What open source does not prove.

It proves what we publish, not what runs on our server. That is why the protection for signal sources comes from the seal, not from the code: before kick-off we only ever hold ciphertext. And that is why every record comes as a bundle that the verifier checks against public drand beacons and Bitcoin, not against anything of ours.

Build on it

Implement the protocol yourself.

The contract is plain JSON over HTTPS. Canonical JSON, Ed25519, RFC 6962 Merkle trees, tlock and OpenTimestamps are open standards with libraries in every common language. A second, independent verifier would make the network stronger, and we would link to it.

Developer documentation