Cryptographic attestation that the document below was captured in Goblin House's archive at the timestamp shown, with the hash listed. If the original URL goes dark or its content changes, this receipt remains as evidence of what the public record looked like at capture time.
| Title | AI Analysis: Stripe — cross-reference insights |
|---|---|
| Original URL | (none — typed-API result with no web URL) |
| Publication | AI Research Pass |
| Source type | government_disclosure |
| Date | 2026 |
| Entity | Stripe |
| Captured | 2026-04-07T04:51:11.594Z UTC |
| Hash computed at | 2026-04-07T04:51:11.594Z UTC |
| SHA-256 | 92955e2ded27605212e26a6584de2a537827d477b75d850275f26547ced3c8f6 |
| Content length | 1,605 bytes |
```json
{
"facts": [
{
"text": "SEC EDGAR contains multiple filings associated with the name 'Stripe' spanning from 2006 to 2026, suggesting either multiple entities using this name or potentially anomalous filing dates that warrant verification",
"date": null,
"confidence": "inferential"
},
{
"text": "A filing dated 2026-03-27 appears in the SEC records, which is a future date and may indicate a data error, a projected/scheduled filing, or requires verification of the actual filing date",
"date": "2026-03-27",
"confidence": "inferential"
},
{
"text": "The earliest SEC filing (2006-04-18) predates Stripe Inc.'s founding in 2010, suggesting this filing may relate to a different entity named 'Stripe' rather than the payments…
The hash above was computed as:
sha256( coalesce(url, '<no-url>') || '\n' || raw_content )
Anyone with a copy of the original document can verify the match:
url + '\n' + content and SHA-256 it.Or POST the candidate content to /source/2324/verify and our server will compare for you:
curl -X POST https://www.goblinhouse.net/source/2324/verify \ -H "Content-Type: text/plain" \ --data-binary @document.txt
Companion machine-readable receipt: /source/2324/receipt.json