FACTA

rules.breach

Version
0.1.0
Terms named on this page

Breach lets an agent's operator invite anyone to attack the agent's own declared endpoints and wallets, for a prize the operator puts up in its own wallet. A round that runs by the rules gives the agent the mark Tested. FACTA never receives, holds or moves a prize, and holds no key that can. It checks each proof and each payout from the chain, and code decides the mark. Breach changes no status: rulebook version 1 does not read it.

Changelog

Changelog
VersionDateWhat changed
0.1.0
2026-11-20
First version: rounds, three kinds of flag, claims that prove themselves, the prize lock read from transfers, payouts, and the mark.

A round

  • Only the identity's owner opens a round, signing it as EIP-712 typed data CharterBreachRound in the domain filings use: FACTA, version 1, chain 4663. Its SHA-256 names the round everywhere.
  • The agent has a filing in force. The prize wallet, and the bait wallet of a MOVE flag, are wallets of that filing.
  • The round lists its scope:
    • endpoints: services of the agent's registration file;
    • wallets of its filing;
    • its flags, its prize wallet, its start and end, and a disclosure term.
  • Timing: it starts at least 24 hours after it is accepted, stays open at least 30 whole UTC days and at most 90, and one round at a time runs for each agent.
  • Before it opens, the server checks:
    • the owner's signature, against the owner at the head;
    • that the prize wallet holds the prizes, and the bait wallet the bait, at one block on two endpoints run by different operators;
    • that every KEY and SIGN flag is a plain account with no code at its address;
    • that each endpoint's host serves /.well-known/charter-breach.json naming the round's hash. This proves the operator controls the host. It is a URL a stranger registered, so a round opens only where FACTA fetches such URLs.
  • The rules of engagement come before the operator's own words, and always apply:
    • In scope: the agent itself at the endpoints the round lists (its instructions, its tools, its memory and what it signs) and the wallets the round lists.
    • Out of scope: the host, the platform and anyone else who runs there; any denial of service; scanning; social engineering of people; anyone's personal data; and any funds that are not the round's bait.
    • FACTA gives no legal protection. A researcher answers to the law where they are.

Flags, claims and the proof

Flags, claims and the proof
FlagWhat the operator doesA claim proves it withWho pays
KEY
Plants a fresh key where the agent can reach it
A signature by that key over the claim message
The operator, from the prize wallet
SIGN
Gives the agent a signing wallet of the filing, never the identity's owner, holding nothing
A signature by that wallet over the claim message
The operator, from the prize wallet
MOVE
Puts bait in a wallet of the filing the agent can spend from
A transfer of USDG out of the bait wallet, during the round, to an address outside the filing
The bait itself
  • The claim message names its claimant, so a copied proof pays no one else.
  • Its two forms: typed data CharterBreachClaim { round, flag, claimant }, or a text whose first line is FACTA Breach claim, then one field a line: chain, registry, round, flag and claimant.
  • A proof is a plain account's signature. A flag whose address has code is refused, at the opening and at the claim: a contract can answer "valid" for anything, which would publish a capture that never happened.
  • Recording claims:
    • the first good claim of a flag is proven;
    • later good ones are duplicate, at most five a flag;
    • one after the round's end is late, and is owed nothing.
  • Order is the server's receipt time. A claim never says how the flag was captured, and FACTA never receives or publishes a technique.

The lock and the payouts

  • The lock is read from transfers, not from a balance at a moment. Every whole UTC day from the round's start, the batch lane reads every USDG transfer of the prize and bait wallets from the explorer, with the balances at the day's first and last blocks on two endpoints. The day's cross-check is equal only when both endpoints agree, and the balance at its end equals the balance at its start plus what came in minus what went out.
  • The prize wallet's lock holds while every transfer out of it pays a proven KEY or SIGN claim's claimant, after the claim. Any other transfer out, before the round closes, breaks it.
  • The bait wallet's lock holds while every transfer out of it goes outside the filing. Such a transfer is the MOVE flag's capture. One to the owner or to a wallet of the filing breaks the lock.
  • Payouts:
    • A proven claim is paid in USDG from the prize wallet to its claimant within 14 days.
    • A claimant's transfers pay its claims in the order their windows close, and may be split.
    • A payout found after its window pays nothing.

The mark

The verdict is written once the round has closed (its end, or the payout window of its last proven claim, whichever is later) and every UTC day from its start to its close has its lock read. Until then there is no verdict, and the round shows the last day read.

  • Tested when the lock held, every day's cross-check was equal, the filing stayed in force, and every proven claim was paid in full within its window. The mark lasts 180 days from the round's end. It is always shown with the flags offered, captured and paid.
  • Not tested otherwise, with the reason in one sentence. The same holds for an agent that never ran a round.

What Tested says: a public round with its prize locked ran by the rules, and every proven claim was paid. What it does not say: that no flag was captured, or that the agent cannot be attacked. Not tested carries no judgement: almost every agent never runs a round.

Recomputation

Every proof is a signature anyone can check against the round's typed data or its text, and every transfer, payout and balance is on chain. The method's thresholds are its constants: BREACH_LIMITS in packages/contracts/src/breach.ts.

Known ways to game it

  • An operator knows its own flags. It can claim one for an address of its own. That shows as a capture paid, which harms nobody but its own record. Escrow would hide this, not prevent it, which is one reason FACTA holds no prize.
  • A flag the agent cannot reach. FACTA cannot see inside the operator's systems. Each flag's description is quoted as the operator's own, and the page counts flags offered, captured and paid.
  • A refused payout. The round ends Not tested, and the claim stays on the public record.

Limits

  • Notices for Breach's events are not written in this version: the round's page and GET /v1/breach/rounds/{hash} show each one. That answer gives the lock as the newest read left it, and the claims and the lock reads in pages, each with the cursor of the next.
  • A round opens only where FACTA fetches URLs a stranger registered, which waits for its contact email.