Chain of custody receipt

Source #44856

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.

TitleSEC EDGAR: filing — Marine Corps Systems Command (2009-03-26)
Original URLhttps://efts.sec.gov/LATEST/search-index?q=%22Marine%20Corps%20Systems%20Command%22&dateRange=custom&forms=4,SC%2013D,SC%2013G,DEF%2014A,10-K,10-Q
PublicationSEC EDGAR
Source typesec_filing
Date2009-03-26
EntityMarine Corps Systems Command
Captured1970-01-01T00:00:00.000Z UTC
Hash computed at2026-05-13T05:01:59.649Z UTC
SHA-256c44a78190451a826e25570f746b4a69a57a98f98a2478340def4ba507b28ce34
Content length563 bytes
Content preview (first 800 chars) 
{
  "ciks": [
    "0001032863"
  ],
  "period_ending": "2008-12-31",
  "file_num": [
    "001-33253"
  ],
  "display_names": [
    "FORCE PROTECTION INC  (CIK 0001032863)"
  ],
  "xsl": null,
  "sequence": 1,
  "root_forms": [
    "10-K"
  ],
  "file_date": "2009-03-26",
  "biz_states": [
    "SC"
  ],
  "sics": [
    "3790"
  ],
  "form": "10-K",
  "adsh": "0001047469-09-003229",
  "film_num": [
    "09707221"
  ],
  "biz_locations": [
    "Ladson, SC"
  ],
  "file_type": "10-K",
  "file_description": "10-K",
  "inc_states": [
    "NV"
  ],
  "items": []
}

Verifying this receipt

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:

  1. Take the URL field and the original document content.
  2. Concatenate url + '\n' + content and SHA-256 it.
  3. Compare to the SHA-256 row above.

Or POST the candidate content to /source/44856/verify and our server will compare for you:

curl -X POST https://www.goblinhouse.net/source/44856/verify \
  -H "Content-Type: text/plain" \
  --data-binary @document.txt

Companion machine-readable receipt: /source/44856/receipt.json