Scoops and verdicts
What a crawler brings home, how it is checked, and how a wrong one is corrected.
A scoop
| Field | What it holds |
|---|---|
accession | The EDGAR accession as a uint64, without dashes |
stock | The stock token address on this chain |
form | The form type: 4, 8-K, 10-Q ... |
items | The 8-K items as a bitmask; bit 4 is 2.02 (results), bit 13 is 5.02 (officers) |
acceptedAt | The SEC's acceptance time |
docHash | keccak256 of the primary document's bytes, exactly as EDGAR serves them |
payloadHash | keccak256 of the canonical JSON the parser produces |
headline | Form 4: net open-market value in USD cents, buys positive. 10-Q and 10-K: revenue. Otherwise 0 |
flags | 1 10b5-1, 2 amendment, 4 officer, 8 director, 16 10% owner, 32 after hours |
crawlerId | The crawler that brought it in |
The parser
liquidcrawl-parse v1 is pinned and deterministic: the same bytes always give the same payload. The full record (every Form 4 row, the 8-K items, XBRL headline facts, links) is canonical JSON with sorted keys and no whitespace. Text fields keep the filing's characters exactly as filed, XML entities included; the site decodes them for display only.
docHash = keccak256(documentBytes)
payloadHash = keccak256(utf8(canonicalJson(parse(documentBytes, meta))))Validity
- The accession exists on EDGAR and its filer or subject is the crawler's company.
- docHash equals keccak256 of the primary document's bytes.
- payloadHash equals the hash of the parser's output for that document.
- The form, items, headline and flags match that output.
- The scoop was posted after the SEC accepted the filing.
Who decides
A contract cannot fetch sec.gov. One verifier run by the house decides every verdict and publishes its evidence on the scoop's page; the hash of that evidence goes onchain with the verdict. Everything the verdict rests on can be checked by anyone; the verdict itself is decided by one party.
Corrections
A scoop that does not reproduce the document is rejected and can be posted again correctly, at most three entries per filing. A parser fix supersedes a record without taking back what was paid for it. Summaries are machine-made, labelled as such, and can be wrong; anyone can flag one on the scoop's page, and the page keeps the history.