Timestamp a source-code release or disclosure.
Whether it is a release build, a license boundary, or a coordinated security disclosure, being able to prove this exact code existed at this time — independently — is often worth a great deal.
Why it works here
Git history is trusted within your team but is mutable and self-asserted. An external, tamper-evident timestamp is different: anchoring the hash of a release tarball, a commit tree, or a specific artifact creates evidence that anyone can verify against a public chain, independent of your repository.
This is useful for defensive publication of open-source prior art, proving a release predates a competitor’s claim, fixing the exact bytes shipped for compliance, or timestamping a vulnerability report so the disclosure timeline is provable. Developers can automate it through the REST API, MCP, or A2A in CI.
Common scenarios
Notarize a release artifact
Anchor the SHA-256 of a build so you can later prove exactly what shipped and when.
Timestamp a security disclosure
Prove when a vulnerability report existed to establish a coordinated-disclosure timeline.
Defensive open-source prior art
Timestamp a design or implementation to guard against later patent or ownership claims.
How to notarize for this
Fingerprint your file in your browser, pay $25 in USDC/USDT, and receive a certificate anchored to Base and Bitcoin that anyone can verify independently. Read the full process or the step-by-step guide.