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.
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.
The Agent, the Originator Kit, the protocol and the verifier are public on GitHub.
This is the moat. None of it is needed to check our numbers.
All of it is built and runs today. The public copies are cleaned: no secrets, no account data, no history. All four are public.
| Component | What it is | Licence | Status |
|---|---|---|---|
| manometer-verify1.0.2 | Checks a scorecard bundle without our servers: receipts, seals, prices, results, bundle root. | Apache-2.0 | public |
| Protocolcontract v1 | Proposal contract, market taxonomy, lifecycle, sealing, receipts, scorecard bundles. | open specification | published |
| Originator kit1.0.1 | Seal and send proposals from a browser or from Node, with the catalogue of games and drand rounds. | Apache-2.0 | public |
| Manometer Agent2.0.6 | The program that places the bets: placement, read-back, limits, reports. With a developer guide. | AGPL-3.0 | public |
| Adapters | Bookmaker adapters, as part of the Agent. | AGPL-3.0 | with 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.
So every Agent release comes with what you need to check that the program you run is the program in the repository.
Every Agent release is source, checksums and a signature. A small script compares what you installed with the published release, file by file.
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.
Each repository has its own tests, set up to run on every change. A release needs every test green.
The Agent had its first security review, and vulnerabilities have a private channel.
Developer Certificate of Origin for every contribution, code owners for the sensitive parts, clear rules for issues.
The repositories start under Manometer and can move to an independent association once there is a community to govern.
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.
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