Document disputes during a funding round turn on a single question: which version of which document governed at the moment it was shared and relied upon — and no standard tool produces an independent, contemporaneous record of the answer.
A funding round is a document-intensive process that unfolds over weeks or months. A term sheet is negotiated across multiple iterations. A SAFE or convertible note is drafted, revised, and circulated for review. A shareholder agreement goes through tracked-changes versions. A cap table model is updated after each conversation about valuation, option pool size, and dilution. By the time a round closes, both sides may have received ten or more versions of the same document.
The cap table is the legal record of who owns what. Every funding event — a SAFE, a convertible note, a priced round — changes the cap table, and every change must be backed by a controlling document: a board consent, a stock purchase agreement, a SAFE, a note, or an option grant. The relationship between the cap table and its underlying documents is the legal foundation of the company's ownership structure.
The scale of what is at stake grows with each round. UK startups deployed £24 billion across 5,887 deals in 2025, according to Beauhurst and Mercia Ventures, confirmed by HSBC's UK Innovation Update. European startups raised $51 billion in 2024, according to Crunchbase data, and the pace of deal activity across both markets creates a corresponding volume of funding documents — term sheets, SAFEs, convertible loan agreements, shareholder agreements, and cap table models — each of which may exist in multiple versions across a round.
When the ownership structure is later disputed — an investor asserts that conversion terms were different from what the founder understood at the time of the note; a co-founder disputes the option pool percentage agreed at the seed round; a new investor finds that the cap table does not match the underlying SAFEs — the dispute turns on a simple question: what did the document say at the moment it was shared and relied upon? That question cannot be answered by any of the tools the parties used to manage the round. It can only be answered by a record that was made at the time.
Founders and investors already use a range of tools to manage documents through a funding round. Each does its job well. None of them, individually or together, produces what a version dispute requires.
Cap table platforms track ownership accurately and maintain a single source of truth for equity structure. They are excellent at showing who owns what at any given moment. They do not independently anchor the underlying documents — the SAFEs, notes, and agreements that support the ownership entries — at the moment those documents were shared.
Data rooms control access and log every access event. They record who viewed which document and when, in a format investors expect and trust. They do not independently verify what that document contained at the moment of access — if a document was subsequently updated, the access log records the event but not the version that was seen.
E-signature platforms timestamp execution and create an audit trail of the signing process. They establish when a document was signed. They do not establish what the document contained at the moment earlier versions were shared, reviewed, and relied upon during negotiation — which is precisely the period when version disputes arise.
Version histories and shared folder platforms record that documents changed and when. They are useful for reconstructing a timeline. They are maintained on the vendor's own infrastructure, and their integrity depends on the vendor's own attestation. They are not independently anchored, legally qualified records.
Carta data shows that SAFEs comprised 90 per cent of all pre-seed deals on its platform in 2024, and US pre-seed startups raised through more than 25,000 convertible instruments on Carta in the same year. Across that volume of instruments, the document-version problem scales with the round: each additional SAFE, each revision to a convertible note term, each update to a cap table model is a new version that may later be disputed. The tools that circulate those documents produce no record of what each version contained at the moment of sharing.
Each existing tool was built for one job and does it well. What none of them produces — individually or in combination — is an independent, contemporaneous, verifiable record of what a document contained at the specific moment each version was shared and relied upon.
The evidential standard for proving what a document contained at a specific moment has three properties. Every tool described above falls short on at least one of these properties.
Independent — the record must be created by a third party with no stake in the outcome. A cap table platform's own records are maintained on its infrastructure. A shared folder's version history is produced by the vendor. A founder's sent emails are produced by the party with an interest in the outcome. An investor's download history is produced by the opposing party. None of these is independent.
Contemporaneous — the record must be made at or near the time the document existed in the version being relied upon. Email metadata can be contested. File system timestamps reflect activity on a specific device. Platform version histories record that a file was uploaded, not that its contents at that moment match what is now being relied upon.
Verifiable — the record must be in a form that cannot be altered after the fact and can be confirmed using independent tools, by any party, without reference to the originating platform. A record held on a vendor's infrastructure depends on that vendor's own attestation of its integrity. It cannot be confirmed independently of the platform that produced the record.
When those three properties are absent, disputes over document versions become credibility contests rather than factual determinations. In the United States, federal trade secret case filings reached 1,203 in 2023, according to the Lex Machina 2024 Trade Secret Litigation Report — and the central question in the overwhelming majority of commercial IP and contract disputes is the same one that arises in cap table document conflicts: what did the document say, and when?
The EU Trade Secrets Directive (2016/943), implemented across all member states, and the UK's equivalent framework both require a claimant to establish that confidential information existed in a specific form at a specific time. A record that meets all three properties answers that question. No existing tool provides one.
This is not a criticism of any individual tool. It is a description of a structural gap that no existing tool was designed to fill — because filling it is not their job. Their job is to organise, share, execute, or track documents. Producing a qualified, externally anchored record of document contents at the moment of sharing is a different function entirely.
A vault deposit made before a document enters circulation during a funding round produces all three evidential properties for that document. Four mutually-reinforcing layers are assembled into a single qualified certificate.
SHA-256 hash — a unique cryptographic fingerprint of the exact file at that moment. A single character change anywhere in the document produces an entirely different fingerprint. The fingerprint cannot be reverse-engineered to reveal the document's contents. This is the mechanism that makes every other layer meaningful: without it, there is no way to prove the document has not changed.
RFC 3161 timestamp — the fingerprint is timestamped by an accredited Trust Service Provider, creating a cryptographically signed record of the exact moment that version of the document existed. This is not a platform-generated timestamp; it is issued by an accredited third party operating under an internationally recognised standard.
eIDAS Article 41 qualification — the timestamp is qualified by an accredited Qualified Trust Service Provider (QTSP). In EU member states the certificate carries a legal presumption of accuracy. Under UK law it is treated as strong electronic evidence. In the United States, Federal Rule of Evidence 901 provides for the admissibility of electronic records where integrity is established through a documented, reproducible process — which the certificate provides. This qualification is the distinction between a timestamp anyone can generate for free and one that carries a legal presumption of accuracy.
Bitcoin blockchain anchoring via OpenTimestamps — the fingerprint is anchored on the Bitcoin blockchain, creating a permanent public record that does not depend on any single party's continued operation to remain verifiable. Even if the issuing platform ceased to exist, the record would remain independently verifiable on the blockchain.
These four layers together produce a vault certificate — a downloadable PDF recording the file name, the SHA-256 fingerprint, the qualified eIDAS timestamp, and the Bitcoin blockchain anchor. Bound together into a single qualified certificate — retrievable, independently verifiable, and admissible years later without either party having to reconstruct or explain a folder of loose files — this is the record a version dispute requires.
Used across every document shared during a funding round — term sheets, SAFEs, convertible loan agreements, cap table models, shareholder agreements — this creates a complete, anchored document history of the round. Each version is dated by an accredited third party at the moment of deposit. The full sequence is verifiable at any future point without relying on any party's own records.
The EUIPO's 2023 Trade Secrets Litigation Trends report found that commercial information — the category covering business strategies, financial terms, and ownership structures disclosed during fundraising — accounted for 62 per cent of the 695 EU trade secret proceedings analysed between 2017 and 2022. A complete anchored document record addresses the evidential gap that sits beneath every one of those disputes.
A complete document record of a funding round changes the position of both parties before any dispute arises. For founders, it establishes what terms were offered, in which version, and when. If an investor later asserts that the conversion terms were different from what the founder understood, the deposit certificate answers the question. The document that was shared, and the moment it was shared, are matters of independent fact rather than competing assertion.
For investors, the same record confirms that the cap table and its underlying documents are consistent with what was represented during due diligence. Investors conducting due diligence on a startup's equity structure are asking for exactly this assurance — that the cap table matches the documents, and that the documents reflect what was agreed. An independently anchored document record provides that in a form no self-certified folder of files can match.
Insurance policies covering business losses and disputes often require the policyholder to establish what was agreed and when. Legal action over disputed funding terms requires the same foundation. The EUIPO's 2023 Trade Secrets Litigation Trends report found that the success rate for trade secret infringement claims across the EU stands at approximately 27 per cent — a figure that reflects, in part, the difficulty of proving what a document contained and when, without a record made at the time.
Without a contemporaneous document record, both insurance claims and legal actions are harder to pursue and easier to resist. Cryptographic prior proof is not insurance — it is the evidence that makes a claim provable, a legal action actionable, and a dispute resolvable from a position of fact rather than assertion.
If you have built a company worth funding — and spent months negotiating the terms of that funding — the question is not whether an independent document record is worth establishing. It is whether you can afford to close a round without one. Its absence is not measured in legal fees. It is measured in disputes that cannot be resolved, terms that cannot be proved, and investments that cannot be defended.
This post provides general information about the role of cryptographic evidence. It is not legal advice. For advice on a specific matter, consult a qualified lawyer in your jurisdiction.
Related Reading
Cap Table Management Best Practices — LTSE
The Data Room as Evidence: Proving What Investors Saw Before They Committed
Pitch Deck Evidence: Prove What You Shared Before a Term Sheet
James Snell is the founder of Provlyn, a platform providing cryptographic prior proof of IP ownership. provlyn.com