Platform & security
Glossary
The terms used across Proofline.
| Term | Meaning |
|---|---|
| Casefile | A submitted report and everything about it. Codes look like CF-1004. |
| Proofline | A Casefile's append-only, hash-chained history of events. |
| Rulebook / program version | An immutable snapshot of a program's scope, impacts, rewards, SLAs and policies, with a SHA-256 fingerprint. |
| Impact | An outcome in the program's table (e.g. IMP-C1 direct theft of funds) with objective conditions. Severity follows from it. |
| Decision ledger | Typed records of every outcome-changing decision, each linked to its Proofline event. |
| Closure proposal | A project's proposed adverse outcome, which must cite a rule and a reason. |
| Final rebuttal | The researcher's one response to a decision, within 48 hours. |
| Mediation | Independent review of a disputed decision, with a published, reasoned ruling. |
| Private duplicate | A duplicate of an earlier report that wasn't public. Neutral for reputation and accuracy. |
| Known-issue commitment | sha256(salt | text) recorded before a report, proving prior knowledge without leaking the issue. |
| Won't Fix | A documented decision not to remediate. The reward stays owed. |
| Obligation | A payable reward. With a vault, it's signed by Proofline and claimable on-chain after its due date. |
| ProoflineVault | A project-owned, non-custodial reward reserve contract. |
| Proof score | A researcher's reputation, based on verified impact rather than volume. |
| Warden | A researcher competing in an audit competition. |
| SLA | A locked response deadline: acknowledgement, triage and payout. |