A public, verifiable record of when the Ore concept, website, pitch deck, and SR007 application existed and were submitted to a16z Speedrun. Every artifact in this dossier is sealed by independent RFC 3161 timestamp authorities and corroborated by third-party public archives and DKIM-signed mail.
On 2026-05-17, the SR007 application was submitted to a16z Speedrun before the deadline; the DKIM-signed confirmation from noreply@sr-team.a16z.com carries the server-issued application ID 50413120-d20e-4362-b61a-16109ef11abc and a delivery timestamp of 2026-05-17T17:49:07Z UTC. On 2026-05-18, the production website at ore-team.com, the SR007 pitch deck PDF, and the full text of the Speedrun application portal were captured byte-for-byte and sealed with RSA-2048 timestamp tokens from three unaffiliated commercial Time Stamp Authorities (FreeTSA, Sectigo, DigiCert). The same evidence is mirrored by the Internet Archive Wayback Machine and Archive.today. The package is admissible under FRE 901(b)(9), FRE 902(13), FRE 902(14), ESIGN, and UETA.
| Artifact | Size | SHA-256 |
|---|---|---|
| Website source ore_portfolio_site.tar.gz | 9.13 MB | d3c678a26bd1d646bbb8873798e9628295b273717ce360bb55a787ae2047c34f |
| Pitch deck ore_pitch_deck.pdf | 1.81 MB | 752d049bc62f2a9a13194adcfd702b57f6c0c014c209ae00ba1e2eb888fc88d8 |
| Portal capture sr007_portal.webarchive | 4.64 MB | 060ba53b4cf20cfb4be056fa439771b243c19502bc2fdd84225191889f2e935d |
| Portal print sr007_portal.pdf | 91 KB | 8ff0a4c5463a8854ee4aa2cfb608bbb4e628efe7a0012ff9933dc1a41c022947 |
| a16z submission confirmation sr007_confirmation.eml | 49.6 KB | 23a94342f0547f601c40b9ac4127b47371c709f90cf56957d1822f64084dbe3f |
Eighteen RSA-2048 timestamp tokens, three per seal event, all VERIFIED against their CA roots. Each token cryptographically binds the SHA-512 digest of the artifact to the TSA's signing time.
The deck was re-sealed on 2026-05-18 after a content revision (added evidence link in the footer of every slide and replaced the closing image with the branded specimen-series triptych). The prior-existence proof for the SR007 application itself rests on the original 13:06 site bundle and the 17:49 a16z confirmation email below.
$ openssl ts -verify \
-data ore_pitch_deck_2026-05-18T14-38-55Z.pdf \
-in deck_sectigo_2026-05-18T14-38-55Z.tsr \
-CApath /etc/ssl/certs
Verification: OK
For FreeTSA tokens, replace -CApath /etc/ssl/certs with -CAfile ca/freetsa_cacert.pem -untrusted ca/freetsa_tsa.crt (both files included in the ZIP).
Independent third-party services with their own server clocks captured the live site on the same day:
The submission receipt from noreply@sr-team.a16z.com carries two valid DKIM signatures, both independently verifiable against live DNS records:
| Signer domain | Selector | Algorithm | Status |
|---|---|---|---|
| sr-team.a16z.com | hs1-242173554 | rsa-sha256 (2048) | VERIFIED |
| bf01.na2.hubspotemail.net | hs2 | rsa-sha256 (2048) | VERIFIED |
Google's MX server independently recorded at delivery time: dkim=pass header.i=@sr-team.a16z.com · spf=pass · dmarc=pass (p=REJECT sp=REJECT). a16z publishes a strict DMARC reject policy, so a forged message claiming to originate from this domain would have been refused by Gmail before delivery.
Date: Sun, 17 May 2026 13:49:07 -0400 (17:49:07 UTC)
From: a16z speedrun <noreply@sr-team.a16z.com>
To: cybermediaboy@gmail.com
Subject: We've received your a16z speedrun application!
Message-ID: <1779040145379.28e03eef-7170-4639-98a0-ee63b6949995@bf01.na2.hubspotemail.net>
Application ID (a16z server-issued):
50413120-d20e-4362-b61a-16109ef11abc
Significance: confirms initial submission before the SR007 deadline
of 2026-05-17 23:59 PT (2026-05-18 06:59 UTC).
The package is structured for admissibility under United States federal evidence rules and electronic-signature law:
To fabricate this evidence chain after the fact, an adversary would need to simultaneously compromise:
Any single one of these is already a high bar; the combination is treated by courts as effectively unforgeable.
A US Remote Online Notary session is scheduled. The notary will witness Yevgen Yanovskyy sign an affidavit of authorship and prior existence, with this entire dossier attached as Exhibit A and the portal record as Exhibit B. The notarized PDF will be re-stamped through the same three-TSA pipeline and added to this page upon completion.
RON provider candidates: Proof.com, OneNotary, DocuSign Notary, BlueNotary.
This evidence is structured so that any third party can independently verify every claim above without needing to trust the author. The tools required are openssl (token verification), a DNS resolver (DKIM verification), and a web browser (archive checks). The verification log and command-line examples for every artifact are included inside the ZIP at notarization/PROOFS_INDEX.txt and notarization_portal/MANIFEST_PORTAL_*.txt.