Insights by Bernstein: Read

The question that stalls indie game deals: “Who owns what?”

Marco Barulli — Fri, 06 Nov 2026 00:00:00 GMT

Updated: 2026-11-06

How video game studios protect their IP and prove ownership of code, art, and music. A practical guide to due diligence from prototype to publishing deal.

Imagine a small indie studio about to sign its first publishing deal. The playable demo runs smoothly, the visual style looks sharp, and the publisher wants to move forward. Then comes the due diligence request that stalls everything: show us that you own or control the rights to everything in the game.

The founders wrote most of the code. A freelance artist designed the characters. The soundtrack mixes original tracks with stock audio. Several environment props came from an online marketplace. An early collaborator left six months ago, and the agreement covering their work sits buried somewhere in an old email thread.

The team can demo the game in ten minutes. Proving who made what, and under which terms, can take weeks.

IP questions come up throughout production. A competitor might copy a character, a contractor might dispute how their work is used, or a confidential prototype might leak online. Preparing for these moments means keeping a clear, dated record of the work, the contracts attached to it, and every version shared outside the team.

What, exactly, are you protecting?

A video game is not a single piece of intellectual property; it combines several kinds. Code, art, dialogue, and music usually fall under copyright. Game titles and logos involve trademark rules. Proprietary tools and game-balancing formulas may count as trade secrets, while certain novel technical systems might qualify for a patent. As WIPO’s overview of video games and IP points out, these rights and requirements vary depending on the country and the asset.

For a studio, the best place to start is with the files themselves: 3D models, animation clips, dialogue scripts, audio tracks, and source code for core mechanics. Each asset has an author, a creation date, and terms that dictate how the studio can use it.

The difference between an idea and its expression is just as important. The U.S. Copyright Office notes that copyright protects original creative expression, never raw concepts, systems, or game mechanics. Pitching “a cooperative survival game on a derelict space station” gives no exclusive right to that setup. The actual code, art, audio, and written words may qualify for protection. A verified timestamp can establish that specific work existed by a recorded time; it cannot turn a generic game idea into exclusive property.

Connect assets to the people and agreements behind them

Consider the freelance character artist. The studio has the finished model and a paid invoice. But does the contract grant full ownership, or only a license? Does it allow sequels, merchandising, or engine ports? Was the character built from scratch, or adapted from an existing base model?

A folder named after a contributor shows where the file came from, but it leaves the legal relationship unproven.

In Mastering the Game (p. 248), WIPO discusses the importance of agreements covering ownership when hiring contractors. The rights acquired depend on the applicable law and contract. A payment receipt or invoice is not a substitute for a signed contract.

A practical studio archive keeps the legal paperwork right next to the delivery. For commissioned work, store the signed contract, assignment of rights, acceptance emails, and source files together. For marketplace assets, save the specific license terms and purchase receipts. For departing team members, retain the agreements establishing which rights the studio holds in their contributions. A digital certificate can prove the date and integrity of these files, but it will not fix missing permissions or vague contracts.

Preserve the development history before you need it

If a distinctive creature from your demo turns up in another game, the finished model is only part of your evidence. Early concept sketches, discarded drafts, 3D sculpt iterations, and commit logs tell a much stronger story of how your design took shape.

The same trail protects you if another company accuses your studio of copying. Showing your internal work step by step can support an account of independent creation and clarify which third-party assets you used under license. The real value comes from records made during day-to-day work, rather than evidence scrambled together after a dispute begins.

There is no need to change your daily workflow. Keep using your regular version control and project tools. Alongside that stream, save dated snapshot packages at key milestones - such as the first playable build, approved character sets, investor pitch builds, and release candidates.

When preparing a package for a publisher, include the build, key source files, a design document, and a short summary of third-party libraries and licenses. Package what a reviewer will actually need; copying an entire project directory without context creates clutter instead of clarity.

Keep the exact files behind the evidence

A digital timestamp or certificate is only helpful if the studio can produce the exact file that matches it.

Game production makes this tricky. An artist re-exports a model with new settings, an audio track gets re-rendered, textures are recompressed, or the project moves to an updated engine version. The game may look identical on screen, but the file’s underlying bytes have changed. Its digital fingerprint (hash) will no longer match the version recorded months earlier.

To avoid this trap, keep the exact files sent to partners in safe, read-only storage alongside your everyday repositories. Active code repositories show ongoing work, but the preserved milestone packages provide the static baseline needed if ownership is ever challenged. Regular backups, secure key storage, and checks that files can still be opened help keep your evidence usable without relying on a single laptop or drive.

Record what leaves the studio

Different pitches require different levels of access. A publisher pitch might only need a short video and a pitch deck. Technical due diligence might expose source code and engine tools, while a co-development partner might need raw art assets.

Treat each disclosure as its own package. Note exactly which build was sent, who received it, what organization they represent, and which non-disclosure agreement (NDA) covers the exchange. If confidential material leaks later, this log can help investigate the disclosure history. Preserve the signed NDA or recorded acceptance of terms alongside it.

Keep in mind that technical tools have limits. Email verification establishes control of the designated email address; it does not establish the person’s identity or authority to sign an agreement for their employer. Once someone downloads a build, access logs cannot stop them from copying it to another drive. Signed contracts and technical tracking must work together.

Start with your next milestone

Getting organized does not require pausing production to audit years of old files. Start with the next milestone. Assemble the exact build, design notes, and key art ready for your next submission. Match those assets with their contractor agreements and marketplace licenses, timestamp the package before sharing it, and log who receives it. Repeating this simple routine at each major milestone turns due diligence from a panic into a quick, routine review.

How Bernstein supports this process

Managing evidence, version histories, and confidential disclosures by hand takes time that small teams rarely have. The Bernstein platform supports this process alongside the tools a studio already uses:

Certification with independent time evidence: Bernstein fingerprints your files and encrypts them in your browser before upload. Only the fingerprints are anchored on the Bitcoin blockchain. Qualified EU timestamps and timestamps from a Chinese authority are also available, depending on the plan. These separate certificates provide independently verifiable evidence of existence and integrity at the recorded times, as explained in How Bernstein works.
Encrypted, versioned storage: To prevent the file-mismatch problem, Bernstein pairs time-stamping with zero-knowledge encrypted storage. Files are encrypted client-side before upload, preserving the exact bit-for-bit originals needed to verify certificates years down the line. Studios can export certificates and verification materials for independent validation. They must retain the corresponding original files and the keys needed to access any encrypted copies.
Secure sharing for pitches and milestones: When sending confidential builds, design documents, or pitch decks to publishers and external partners, Bernstein Secure Sharing links access directly to a certified version. It verifies control of the designated recipient email address, can require acceptance of your NDA before unlocking files, and logs download events.
Complementary to legal advice: Bernstein provides the technical evidence trail - records of existence, integrity, and disclosure. It does not replace contracts or legal advice, but gives your lawyers and publishers verifiable records to assess alongside the agreements and other evidence supporting ownership.

Sources

David Greenspan, S. Gregory Boyd and Jas Purewal. Video Games and IP: A Global Perspective. 30 April 2014
U.S. Copyright Office. What Does Copyright Protect?. Accessed 6 November 2026
World Intellectual Property Organization. Mastering the Game. Discussion of employees and independent contractors, p. 248.

When Institutions Play Startup: The Cautionary Tale and Demise of WIPO PROOF

Marco Barulli — Wed, 04 Nov 2026 00:00:00 GMT

Updated: 2026-11-04

A post-mortem on why a UN agency’s commercial timestamping service collapsed after 20 months, and what it teaches the IP ecosystem about digital evidence.

Migrating from WIPO PROOF?

To ensure your legacy evidence remains permanent and fully protected ahead of the January 2027 sunset, Bernstein is offering an exclusive transition discount and dedicated migration support for former WIPO clients. We’ll help you securely organize your original files and existing tokens into zero-knowledge Bernstein projects. Contact the Bernstein team today.

On May 27, 2020, the World Intellectual Property Organization (WIPO), a specialized agency of the United Nations, stepped outside its traditional multilateral boundaries to launch WIPO PROOF, a commercial digital timestamping service pitched as an impartial “digital notary” for the data economy. Designed to produce cryptographic proof of existence for unregistered intellectual assets—trade secrets, raw data sets, algorithms, and design drafts—the service was billed as an essential digital bridge for global innovation.

Twenty months later, the experiment was over. On January 31, 2022, token generation was halted, and the service was formally decommissioned on February 1, 2022.

The demise of WIPO PROOF is a classic study in institutional mission creep: what happens when an intergovernmental body attempts to operate as a commercial software vendor in a mature, competitive technology market. The service faltered on economic miscalculations, technological commoditization, and legal ambiguities. Ultimately, its closure paved the way for a welcome, disciplined return to core multilateral governance under WIPO’s updated leadership.

The Genesis of an Institutional Mismatch

WIPO PROOF was championed in the twilight of former Director General Francis Gurry’s tenure. The concept appeared visionary on paper: as economic activity shifted from tangible industrial assets to ephemeral digital bits, traditional formal intellectual property registrations (patents, trademarks, industrial designs) felt too slow and expensive for rapid, iterative digital works. WIPO sought to position itself directly in the creative workflow, issuing trusted cryptographic fingerprints that could serve as international evidence of anteriority.

Yet this ambition contained a structural flaw. WIPO’s foundational mandate under its establishing convention is normative and administrative: harmonizing national IP legislation, administering international treaty frameworks like the Patent Cooperation Treaty (PCT) and Madrid System, and providing technical assistance and education. Operating a direct-to-consumer digital utility required an entirely different operational DNA—continuous user acquisition, dynamic software iteration, customer onboarding, API platform engineering, and hyper-competitive pricing. By stepping into the arena of commercial software, an intergovernmental body crossed the line from market facilitator to private-market competitor.

The Commercial Reality: 3,000 Tokens and a Broken Pricing Model

The market’s verdict on WIPO PROOF was swift and unforgiving. During initial feasibility assessments, planners built models anticipating robust enterprise adoption, eyeing volume targets of up to 100,000 tokens annually.

The actual figures disclosed during the 32nd session of WIPO’s Program and Budget Committee told a starkly different story: during its entire first year, WIPO PROOF sold just over 3,000 tokens worldwide. While users registered from 117 countries, adoption was paper-thin.

Metric	WIPO PROOF	Market reality or alternatives
Projected annual sales volume	Baseline: up to 100,000 tokens annually.	Actual sales: just over 3,000 tokens in the first year.
Retail pricing	CHF 20 per single token.	Tens of vendors charging from a few cents to a few euros.
Enterprise bundle pricing	CHF 13 per token when purchasing a bundle of 1,000 tokens.	SaaS flat-rate subscriptions or APIs charging fractions of a cent.
Infrastructure	A centralized RFC 3161 PKI Time Stamping Authority.	Private Qualified Trust Service Providers and decentralized public blockchains.
Statutory legal weight	A standard electronic timestamp, without the eIDAS qualified presumption.	Qualified electronic timestamps carrying a legal presumption across the 27 EU member states.

The primary driver of this commercial failure was an unworkable pricing strategy. WIPO set the price of a single token at 20 Swiss Francs (CHF), offering marginal volume discounts that scaled to CHF 13 per token only if an enterprise committed to purchasing a 1,000-token bundle. This pricing betrayed a fundamental misunderstanding of digital development workflows:

For individual creators and developers, paying CHF 20 each time a software build, CAD revision, or manuscript chapter was updated introduced unsustainable financial and procedural friction.
For R&D enterprises and data science teams, generating thousands of training datasets or iterative code commits per week made a per-token manual fee an operational non-starter.

In the context of WIPO’s broader balance sheet, the product was an irrelevant distraction. WIPO operates on a biennial budget exceeding 790 million Swiss Francs, with more than 95% of its income generated reliably through statutory filing fees from the PCT, Madrid, and Hague systems. WIPO PROOF produced virtually no revenue while consuming ongoing engineering oversight, governance debate, and security compliance costs.

Technical Commoditization and Legal Ambiguities

WIPO PROOF was frequently mischaracterized as a blockchain solution, but it was nothing of the sort. The service relied on standard Public Key Infrastructure (PKI) conforming to the decades-old IETF RFC 3161 protocol. The user’s browser calculated a SHA-256 hash locally, transmitted that hash to WIPO’s servers, and WIPO appended an atomic timestamp signed by its institutional private key to output a .tsr token file.

By offering standard RFC 3161 timestamping, WIPO was attempting to charge a premium for a utility that had long since become a commoditized feature of developer toolchains, operating systems, and commercial document management suites.

Crucially, the service was trapped in an awkward legal position:

Lacking Qualified Legal Presumption: While WIPO attained ISO/IEC 27001 and aligned its procedures with ETSI EN 319 421/422 trust standards, its tokens did not carry the statutory presumption of temporal accuracy and data integrity enjoyed by Qualified Trust Service Providers (QTSPs) under European Union’s eIDAS Regulation. European enterprises needing court-tested certainty could obtain qualified timestamps from domestic QTSPs for a fraction of the cost.
The “Proof of Creation” Mirage: Marketing an electronic timestamp under an intellectual property banner risked confusing unsophisticated creators. Cryptographic timestamps prove possession and integrity of an exact sequence of bytes at a specific date; they do not prove authorship, originality, or ownership. Anyone who illicitly accessed an unreleased codebase or secret design could hash it and receive a genuine WIPO token.
No Substantive Procedural Rights: Unlike formal statutory copyright registration (such as Section 411(a) in the United States) or national administrative envelopes (such as France’s INPI e-Soleau or the Benelux i-DEPOT), a WIPO PROOF token conferred no statutory presumptions, no statutory damages eligibility, and no priority filing date. It was merely private electronic evidence—yet branded with the seal of a UN agency.

The Leadership Course Correction: A Return to Multilateral Focus

The quiet shutdown of WIPO PROOF was not an accident; it was an intentional policy correction. When Daren Tang took office as Director General in late 2020, his administration initiated a comprehensive strategic review during the preparation of WIPO’s Medium-Term Strategic Plan (MTSP) 2022–2026.

Tang articulated a clear, principled vision for the organization’s boundaries. Speaking candidly before intellectual property bodies, including the Chartered Institute of Patent Attorneys (CIPA) Congress, Tang stated directly that WIPO should not be offering services that compete with the private sector.

The new leadership recognized that when an international organization uses its institutional standing and public budget to sell commercial software, it distorts private markets, antagonizes specialized technology providers, and compromises its core identity as an impartial normative body.

At the Program and Budget Committee session in July 2021, the Secretariat reported that market conditions had accelerated rapidly, rendering the continuation of the pilot unviable. Member States ratified the recommendation to end the program during the October 2021 General Assemblies.

Tang’s administration redirected WIPO’s resources where they can deliver authentic, systemic value: administering and modernizing the core international treaty frameworks (PCT, Madrid, Hague), expanding global IP education, training academies, and youth initiatives, and supporting small- and medium-sized enterprises (SMEs) and developing economies in unlocking the value of their intangible assets.

The leadership deserves credit for recognizing an overreach, executing a graceful wind-down, and refocusing WIPO on its essential statutory and educational role.

Lessons for the IP Ecosystem: Where Proof Truly Belongs

WIPO committed to supporting legacy token holders with verification tools through January 31, 2027. Because the service utilized open RFC 3161 standards, existing tokens remain verifiable offline via standard OpenSSL cryptographic utilities using WIPO’s exported public CA certificates. Yet the broader lesson of the WIPO PROOF experiment is unmistakable: institutional centralization is the wrong paradigm for long-term digital proof.

When proof of existence relies on a centralized institutional service, the longevity of that evidence remains vulnerable to changes in administrative policy, budget reallocations, or executive leadership. The moment WIPO discontinued token generation in 2022, private, standards-based timestamping was reaffirmed as the only durable foundation.

For creators, inventors, and enterprises managing valuable trade secrets and code, evidence of creation should never depend on whether an administrative vendor remains in business. Instead, lasting IP defensibility is achieved by anchoring cryptographic commitments to public and reliable blockchains such as Bitcoin, alongside electronic timestamps issued by qualified trust service providers that carry statutory legal value. By pairing immutable, decentralized public ledgers with qualified timestamps, proof of anteriority and integrity becomes permanently verifiable, independent of any operating company, government portal, or intergovernmental organization.

WIPO’s foray into commercial timestamping proved that while digital evidence is vital, building and sustaining that evidence layer belongs in the competitive, standards-driven private market.

Securing Your Legacy Assets Ahead of January 2027

For organizations, inventors, and creative teams holding legacy WIPO PROOF tokens, an important operational date is approaching: January 31, 2027, marks the conclusion of WIPO’s five-year transitional commitment to provide hosted token validation and verification services.

Compounding this transition is a fundamental design reality of the service: WIPO never stored your actual certified data. Files were hashed locally inside the browser and never uploaded to WIPO’s servers. As a result, WIPO held only the .tsr token files, leaving the physical custody and preservation of original source files, design documents, and trade secret datasets entirely to the user. If an original file is lost, altered, or separated from its token, the cryptographic match is broken and the evidentiary chain collapses.

The impending January deadline serves as a timely reminder to audit your archives, consolidate your original assets alongside their tokens, and bring them into an active, resilient environment.

A Permanent Home for Your Evidence:

Bernstein offers the natural destination for this transition:

Centralized Project Workflows: Import your historical files, legacy WIPO tokens, and accompanying documentation directly into structured Bernstein projects, preserving complete evidentiary context across the entire lifecycle of your IP.
Multi-Jurisdictional Legal Defensibility: Besides permanent Bitcoin blockchain anchoring, Bernstein generates at once EU eIDAS qualified electronic timestamps and official Chinese trusted timestamps, providing cryptographic records backed by qualified legal presumptions of temporal accuracy and data integrity across their respective territories.
Decentralized Permanence: Anchor ongoing project iterations to the Bitcoin blockchain, ensuring your proofs of anteriority remain mathematically verifiable forever, completely independent of any institutional website or corporate lifecycle.
Zero-Knowledge Storage: Unlike WIPO’s token-only model that left custody entirely on your shoulders, Bernstein solves the critical vulnerability of asset preservation by securely maintaining your underlying digital files alongside their certificates in an encrypted, versioned vault. Built on a zero-knowledge architecture, all files are encrypted locally in your browser before upload, ensuring your trade secrets, source code, and design files remain accessible exclusively to you.

Sources

WIPO News. WIPO Introduces New Business Service That Provides Evidence of an Intellectual Asset's Existence. May 27, 2020
WIPO Magazine. Introducing WIPO PROOF: an interview with Francis Gurry. June 30, 2020
WIPO News. Discontinuation of the WIPO Proof Token Generation Service. October, 2021
ManagingIP. WIPO Proof to end in 2022 after poor demand. September, 2021
WIPO Magazine. Digital date-and-time-stamping: the evidentiary value and practical significance of WIPO PROOF. January 17, 2021
IP Leaders. WIPO PROOF : Intellectual Property's mark in going digital. May 14, 2021
WIPO. Program of Work and Budget for 2022/23
WIPO. Program and Budget Committee 2021. July 2021
RFC Editor. RFC 3161: Internet X.509 Public Key Infrastructure Time-Stamp Protocol. August 2001

Is your IP ready to be financed? A checklist built on the EUIPO's five priorities

Marco Barulli — Tue, 03 Nov 2026 00:00:00 GMT

Updated: 2026-11-03

The EUIPO's five priorities for IP-backed finance, read as a to-do list for IP owners and their counsel. What to put in place now so your IP qualifies when the instruments arrive.

This is the fourth and final article in our series on IP-backed finance from the innovator’s perspective: a practical guide on how companies and their IP advisers can prepare their assets for financing.

We began this series with a foundational policy document: the EUIPO’s April 2026 report on IP-backed finance, which estimates an annual addressable market of EUR 70-150 billion for European companies leveraging their intellectual property for growth. Over our last three posts, we examined the primary obstacles it identifies: the disclosure paradox, the vicious circle of missing data, and the mixed record of blockchain as a tool for IP-backed markets.

Now, we turn to practical steps. The report establishes five priorities for building a functional IP-backed finance system in Europe. While no one can predict exactly when guarantee schemes, valuation standards, or a central pledge register will be finalized, every priority demands specific readiness from IP owners. Fortunately, most of that groundwork can and should begin today.

Priority 1: Make IP visible

What the report proposes: A voluntary disclosure framework built upon the IP Scan (the subsidized IP check-up for EU SMEs detailed in part 1). This framework would cover registered rights and other relevant intangibles, ensuring IP-rich firms are transparent and easily evaluated by lenders and investors.

What it will ask of you: A structured, comprehensive inventory of your intellectual property, including crucial assets that sit outside formal registries.

What to do now:

If you are an EU-based SME, apply for an IP Scan immediately. It is heavily subsidized and serves as the report’s proposed entry point for the future disclosure framework.
Audit your registered rights to ensure they are in order: confirm renewals are paid, assignments and licenses are formally recorded, and ownership resides in the correct corporate entity.
Catalog the unregistered assets that drive real commercial value (source code, know-how, data sets, designs, and internal processes) and designate clear ownership for each.
For critical unregistered assets, establish a verifiable record of their existence and timeline without exposing their actual content. This is Bernstein’s core utility: by creating a cryptographic fingerprint of your files anchored to Bitcoin, eIDAS-qualified timestamps, and a China TSA, you generate a provable inventory you can safely present to financial counterparties.

Priority 2: Assign credible value to IP

What the report proposes: A European valuation architecture aligned with International Valuation Standards, modular valuation models to reduce costs for SMEs, and digital tools that generate indicative estimates pending professional validation.

What it will ask of you: Verifiable data a valuer can trust. Valuations demand documented proof of identity: when the asset was developed, how it evolved, its cost base, and its commercial application.

What to do now:

Maintain development records continuously, rather than scrambling to compile them when a valuation is commissioned. Immutable, date-stamped revisions of key work demonstrate an asset’s evolution and substantiate both cost- and income-based analyses.
Track the specific development costs of key assets. Under IAS 38 (the accounting standard for intangible assets), development costs can only be capitalized as an asset rather than treated as an expense under strict circumstances, requiring hard evidence that all conditions were met.
Document the direct commercial impact of each asset. Detail which products or services rely on it, the revenue it supports, the costs it reduces, or the advantages it helps maintain. Maintain clear evidentiary links that distinguish the asset’s specific contribution from the broader business operations.
When providing a valuer access to trade secrets, use controlled sharing environments that maintain strict access logs.

Priority 3: Leverage IP value into lending

What the report proposes: Initial risk-sharing through public guarantees for IP-backed loans, dedicated public lending against IP collateral, and the exploration of IP insurance products.

What it will ask of you: The precise documentation a lender’s counsel requires before taking security over an asset: clear definitions, undisputed ownership, proven integrity, and a complete access history.

What to do now:

Secure your chain of title. Verify that all founders, employees, and contractors have executed written IP assignments to the company, and check the execution dates against the development history.
Understand how IP pledges function in your specific jurisdiction. The report explicitly notes that rules are not harmonized across Member States, making this a critical question for your national legal counsel.
Ensure the integrity of your key assets can be audited by a third party independently. Bernstein certificates, for example, can be mathematically verified by external parties without relying on Bernstein itself.

Priority 4: Build the evidence base

What the report proposes: Common data requirements, interconnected registries, a robust dataset of real transaction outcomes, and a central register of IP pledges.

What it will ask of you: Clear transaction records and documentation of every agreement involving your IP.

What to do now:

Maintain a central, up-to-date register of all licenses, options, pledges, and disclosures, complete with executed attachments.
Implement controlled sharing for all sensitive material. Every disclosure to a partner, investor, or acquirer must leave a cryptographic, date-stamped audit trail detailing exactly who received access, under what terms, and when.
Keep your evidence portable. Periodically export your certificates, files, and cryptographic keys to self-hosted storage. Your evidentiary record should never be locked into a single vendor’s ecosystem.

Priority 5: Reinforce coordination

What the report proposes: Cross-border coordination of standards, valuation expertise, digital tools, and training. Notably, the proposed training programs target founders and management teams directly to prevent the early-stage IP errors that most frequently impede fundraising and prepare firms for investor IP due diligence.

What it will ask of you: To have anticipated and mitigated these early-stage errors long before a term sheet arrives.

What to do now: Treat IP due diligence readiness as a continuous operational discipline, not a reactive project.

The one element you cannot retrofit

While most of this checklist can be executed on demand, one critical element cannot be backdated: a timestamp.

A cryptographic timestamp inherently records the exact moment it is generated. Any service claiming to backdate a timestamp is fundamentally worthless. If a lender in 2029 asks whether a vital piece of know-how existed in 2026, a timestamp created in 2026 can help establish that the corresponding files existed at that time. Comparing those files with the timestamped record can also help verify their integrity. Ownership requires separate supporting evidence, such as contracts and assignments, and other contemporaneous records may also help establish the asset’s history.

The policy timeline for European IP-backed finance remains uncertain. It depends on the Savings and Investment Union, guarantee budgets, and banking standards. Your timestamped record, however, begins when you create the timestamp, not automatically when you create the asset.

Closing the series

The EUIPO report makes a compelling case for expanding IP-backed finance in Europe. The capital is mobilizing, and IP-rich firms are driving the continent’s growth. Whether an individual company can capitalize on this shift will depend less on the timing of reforms and more on whether its IP can be cleanly verified, understood, and audited by external capital providers.

This principle has anchored our entire series. Disclose the proof, not the secret. Supply the foundational evidence that only the asset owner can generate. Use blockchain where it provides mathematical certainty as a digital notary, not as a speculative token. And establish your evidentiary record today, because a timestamp created tomorrow cannot establish that the files existed today.

Bernstein has been building these verifiable records for innovators since 2016. Bernstein does not value IP, it simply ensures that when the market is ready to do so, your evidence is available for independent verification.

To see the platform in action, visit bernstein.io.

This checklist is general guidance and not legal advice; consult counsel on the law of your jurisdiction. Bernstein provides evidence and does not replace patents, trademarks or contracts.

Sources

European Union Intellectual Property Office. IP-backed Finance. Executive Summary, p. 5; sections 2.2.2–2.2.3, pp. 39–42; sections 4.1–4.5, pp. 103–109. April 2026
European Union Intellectual Property Office. IP Scan / IP Scan Enforcement voucher 2026. SME Fund 2026, Voucher 1. Accessed 3 November 2026

EU Qualified Ledgers: A Legal Privilege No Technology Earned

Marco Barulli — Thu, 29 Oct 2026 00:00:00 GMT

Updated: 2026-10-29

The EU grants qualified ledgers a legal presumption their technology does not earn. It helps in EU courts, adds little elsewhere, and is no substitute for proof anyone can verify.

The 2024 revision of eIDAS created a new class of evidence: qualified electronic ledgers. The implementing rules published in December 2025 set out what these systems must do (Regulation 2024/1183, Implementing Regulation 2025/2531). A record entered on a certified ledger now carries a statutory presumption of integrity and chronological order in all 27 member states.

In any EU court, even in a dispute between companies from different member states, that presumption moves the burden of proof onto whoever challenges the record. So it is fair to ask what technical breakthrough earned it.

There isn’t one.

The framework does not require decentralization, fault tolerance across independent parties, or open verification. It is perfectly comfortable with a closed system run by a single company. Read past the regulatory vocabulary and the required controls are signatures, hash chains and a protected signing key: the same toolkit engineers have bolted onto ordinary databases for decades.

The EU has not raised the technical bar. It has stamped the existing one and attached a legal privilege to the stamp. For IP owners and the lawyers who defend them, mistaking that stamp for stronger evidence is a costly error. It trades proof that anyone can verify for a label that only works where the label is recognized, and only if the vendor is still around to back it.

A Ledger in Name Only

“Qualified electronic ledger” sounds like distributed, tamper-proof infrastructure. The annex to Implementing Regulation 2025/2531 describes something much plainer:

advanced electronic signatures or seals based on qualified certificates, to show where data came from;
hash lists or hash trees (SHA-256 or stronger) to fix the order of records;
signature-based integrity checks, so that any later change is detectable;
certified hardware (Common Criteria EAL 4 or FIPS 140-3 Level 3) to hold the signing keys.

Nothing on that list needs a blockchain. Distributed ledgers are allowed, with some extra ISO requirements, but they are an option, not a condition. An append-only PostgreSQL table with signed entries, a Merkle root and a hardware security module (HSM, the tamper-resistant device banks use to guard their signing keys) clears the same functional bar.

	Certified “qualified ledger”	Equivalent system, uncertified
Technology	Database + PKI + hash chain	Database + PKI + hash chain (or stronger)
Legal weight in the EU	Statutory presumption (eIDAS Art. 45k)	Must prove its integrity from scratch

Ledger vendors will object that their systems are distributed, pointing to the number of nodes they run. But ten servers under one company’s control are still one company. Whoever holds the root keys, the hosting contracts and the admin console can go bankrupt, be coerced or make a mistake, and all ten nodes go down with them.

The result is a legal hierarchy that ignores engineering. An audited database labelled “qualified” gets the presumption; an identical or better system without the label starts from zero. The law trusts the vendor’s paperwork more than the mathematics of the evidence.

An Audit Is Not a Guarantee

Defenders point to the supervision regime. Qualified trust service providers are audited at least every two years and must keep a termination plan that preserves access to records if they shut down (Implementing Regulation 2025/2530, Article 3).

A termination plan is an intention, not a proof. It works only if, at the moment the provider collapses, there is still money, a willing successor and staff who follow the plan. Insolvency, distressed sales and restructuring are exactly the moments when none of that is certain.

An audit report says a provider passed a checklist on the day of the audit. It cannot bring back an archive that has gone offline, or rebuild a chain of custody halfway through a trial. Suing a bankrupt trust provider will not rescue a claim that has lost its proof.

Evidence Must Outlast the Vendor

Intellectual property can stay valuable, and contested, for decades. Take a company that keeps a process secret instead of patenting it. If a competitor later patents the same idea, the company can keep using its process only by proving it got there first, and that proof must hold for as long as the rival’s patent can be enforced: up to twenty years.

Software companies rarely last that long. Products are discontinued, APIs deprecated, startups acquired or wound down. Meanwhile the disputes that matter (a former supplier reusing your drawings, a new patent covering a process you have run for years) often surface ten or fifteen years after the work was created.

At that point you must prove that the work existed, that it has not changed, and that it was yours. A ledger entry cannot do that on its own if checking it requires the vendor’s closed API, a licence for discontinued software, or an escrow archive nobody has opened in a decade. When the provider goes, the evidence goes with it.

Every IP lawyer should therefore apply one test:

If the ledger vendor disappeared tomorrow, could an independent expert export the raw proofs and verify them in court using only open-source tools and public standards?

If the answer is no, you do not own your evidence. You rent it.

The Presumption Stops at the Border

IP is international. An invention developed in Munich is patented in the US, manufactured in Shenzhen and licensed in Tokyo. Infringers do not pick their jurisdiction to suit Brussels.

The presumption in Article 45k binds EU courts. A US federal judge, a Singapore arbitral panel or the High Court in London owes it nothing. Outside the EU:

admissibility follows local procedure and expert-evidence rules, such as Daubert challenges in the US, where the opposing party asks the judge to exclude expert testimony whose method cannot be independently tested;
an EU certificate does not replace a technical account of how the record was produced and checked;
an expert who has to concede that verification depends on a vendor’s undisclosed, closed-source code invites exclusion, or at best a heavy discount.

Compare an open standard such as RFC 3161 for timestamps. The format and the verification procedure are public, and any competent expert anywhere can check a token with free tools, without a licence and without the issuer’s help. Evidence built that way travels. Evidence that relies on an EU certificate for its weight is strong in EU courts, but everywhere else it has to prove itself from scratch.

Use the Badge, Don’t Build on It

None of this makes qualified ledgers useless. Inside the EU, a statutory presumption is a real procedural advantage, as long as the record stays verifiable for the life of the asset and does not depend on the vendor’s survival. Outside the EU, it adds very little.

So IP owners do not have to choose between local recognition and global verifiability. They should layer the two. Anchor evidence first in open, global infrastructure that anyone can check without asking permission, such as RFC 3161 timestamps or the Bitcoin blockchain. Then, where a dispute is likely to be fought, add the proof that local courts recognize: a qualified ledger in the EU, an accredited timestamping authority in China, a government-accredited timestamp in Japan.

When you decide how your company records its core assets:

Anchor globally first. Use open standards and public infrastructure that any expert, in any jurisdiction, can verify with free tools.
Add local recognition where you may litigate. Treat nationally recognized proofs as a layer on top, not as the foundation.
Keep the data and the proofs. A proof only certifies a hash; without the exact original file, it proves nothing. Keep the certified data, byte for byte, together with self-contained proof packages (raw signatures, hashes and certificate chains), all in your own custody.
Verify without the vendor. Make sure your own team can check any historical record with open-source tools, with the vendor’s platform switched off.

A statutory presumption can win you the argument in one jurisdiction. Proof that anyone can check lets you make the argument anywhere.

Sources

European Parliament and Council of the European Union. Regulation (EU) 2024/1183. Amendments to eIDAS introducing electronic ledgers; Article 45k cited in the article. 2024
European Commission. Implementing Regulation (EU) 2025/2531. Requirements for qualified electronic ledgers; annex. 2025
European Commission. Implementing Regulation (EU) 2025/2530. Article 3: termination plans. 2025
C. Adams, P. Cain, D. Pinkas and R. Zuccherato. Internet X.509 Public Key Infrastructure Time-Stamp Protocol (TSP). RFC 3161. August 2001

Before You Submit: How to Protect Your Architectural Work

Marco Barulli — Wed, 28 Oct 2026 00:00:00 GMT

Updated: 2026-10-28

Before submitting to a tender or competition, preserve evidence of your design, clarify permitted uses and plan any public disclosure to support protection.

Preserve the story of your design before it leaves the studio, and why it matters when a tender goes wrong.

The boards are ready. The model is checked. After weeks of testing layouts and working through revisions, your studio is about to submit its proposal.

You know another practice might win, that is the nature of competitions. What worries you is a different scenario: your proposal is rejected, but a few months later, a distinctly familiar concept appears in the winning project. Or the client asks for “a few more schematic drawings,” only to hand your hard work to a cheaper execution firm.

If this happens, could you prove exactly what your studio created, what you shared, and what the client was allowed to do with it?

These questions are much easier to answer if you prepare while the project is still on your desk. A few deliberate habits can give you a clear, independently verifiable record.

Preserve how the design became yours

A final presentation shows the polished result. But the sketches, study models, and revisions show how your team arrived there.

You don’t need to archive every mouse click, but you should preserve the meaningful milestones. Keep the early study that captures the first appearance of a façade treatment. Save the series of plans showing how you resolved an awkward circulation space. Document consultant contributions and make sure you have agreements on how their work can be used.

Proving ownership is much easier when you can show the actual choices you made. Saying “we proposed a light-filled atrium” holds little weight; showing timestamped CAD files of its specific proportions and spatial relationships changes the conversation.

How Bernstein helps:

Bernstein certifies your project revisions and retains your files in encrypted storage. By combining Bitcoin anchoring with officially recognized EU (eIDAS) and Chinese timestamps, Bernstein gives each revision independent proof that matching files existed by the certified date and haven’t been altered since. This multi-standard timestamping ensures your evidence carries immediate weight and meets local legal standards in European, Chinese, and international contexts, all while your drawings remain strictly private.

Be clear about what submitting allows

Before entering a tender, read the intellectual property clauses as carefully as the design brief. Watch out for predatory “rights grab” clauses. Permission for a jury to assess a proposal is very different from permission to build it.

Look for answers to four practical questions:

Does the studio retain copyright of the submission?
What can the organizer do with unselected entries?
Can the organizer adapt your work or pass it to another practice?
What permissions remain if the project is cancelled?

The Royal Institute of British Architects (RIBA) highlights protecting entrants’ copyright as an essential mark of a well-run competition, while recognizing that organizers usually only need limited rights to promote or exhibit entries. If the wording gives the organizer too much freedom, seek clarification before submitting. Whenever possible, agree in writing that developing your proposal requires a separate contract. (Note: A tiny copyright symbol on your title block will not override the competition’s signed terms).

Keep the exact package that leaves the studio

The night before a deadline is chaotic. A board is re-exported, a render is tweaked, and suddenly the package uploaded to the portal differs slightly from the one in your server’s “Final” folder.

Preserve and certify the exact files submitted, and keep the portal upload receipt or delivery confirmation alongside them. If a dispute ever arises about what was handed over, having certified copies of the identical file bundle eliminates any debate about subsequent tampering or missing pages.

How Bernstein helps:

Certify the full submission bundle - You can certify the complete package that leaves the studio, not just drawings and 3D models, but technical specifications, administrative forms, and qualification documents. This creates an independently verifiable snapshot of the entire submission on that date.
Control delivery with Secure Sharing - When tenders do not require a closed procurement portal, Bernstein’s Secure Sharing allows you to distribute files directly. It tracks who opened your drawings and logs their explicit acceptance of your sharing terms before granting access, creating a record of access through the sharing link and the terms accepted by recipients.

Choose the public reveal deliberately

A strong proposal deserves a public life, even if it doesn’t win. Publishing your work in a portfolio or exhibition brings recognition, and it can also trigger legal protection.

In the European Union, a design that is new and unique can qualify for 3 years of unregistered design protection from the moment it is first disclosed to the EU public. No registration is required. This covers copying the appearance of whole buildings or distinct architectural components.

A quick warning: Check the competition’s confidentiality rules before posting on social media. A private submission to a jury does not count as a public reveal, but once you publish it on your website or in a public exhibition, the three-year protection clock starts ticking.

Connect publication to the work behind it

If you want to protect your work, your public reveal shouldn’t exist in a vacuum. It should be linked directly to your private design process.

How Bernstein helps:

This is the idea behind Bernstein’s planned Defensive Publishing feature. When you decide to reveal a design, you select a version from your project’s private, certified record. The publication becomes the next step in that documented history. It connects your early private sketches to your final public renders, creating a verifiable trail anchored to the Bitcoin blockchain, connecting the published design to its development history and helping document the disclosure on which unregistered design protection depends.

(Note: If your design includes a genuine technical innovation, like a novel façade assembly system, publishing it might prevent you from patenting it later. Decide if you want to file for a patent before sharing the technical details.)

Conclusions

Your studio has to show its work to win work. But before your next submission leaves the office, make sure you have preserved the design’s development, locked down the exact submission package, and understood the terms of sharing.

By making these simple steps a studio habit, you will be in a much stronger position to stand behind your work, control its narrative, and take action if someone uses it without your permission.

Sources

Bernstein. Platform features. Certification process and Secure Sharing tools
Bernstein. Defensive Publishing. Planned feature
Royal Institute of British Architects. Guidance for competition entrants
European Union Intellectual Property Office. FAQ on design protection basics
European Union Intellectual Property Office. Invalidity decision ICD 000001014. Architectural designs
European Union Intellectual Property Office. FAQ on unregistered Community designs. Proving prior disclosure
European Patent Office. Guidelines for Examination. 2026 edition, G-IV, 2: technical disclosure and prior art

Blockchain in IP finance: the lesson of patent NFTs

Marco Barulli — Tue, 27 Oct 2026 00:00:00 GMT

Updated: 2026-10-27

Patent NFTs promised a liquid market for intellectual property. The collapse of IPwe shows why the true value of distributed ledgers lies in durable evidence, not tradable tokens.

An enterprise often spends years quietly engineering proprietary technology before ever approaching a lender. When funding talks finally begin, the dialogue turns quickly from technological promise to documented reality. The innovator must substantiate what it owns, demonstrate how the technology evolved, and prove why its records deserve confidence. In IP-backed lending, the quality of those internal records directly shapes credit terms and underwriting decisions.

In the first two articles of this series, we examined the disclosure paradox and the evidence gap in IP finance. Distributed ledgers enter this discussion because they allow corporate records to be verified independently and objectively. Yet much of the public debate has bypassed this foundational evidentiary role, focusing instead on a far more speculative ambition: turning intellectual property into tradeable tokens.

The EUIPO’s IP-backed Finance report examines that ambition through the rise and fall of IPwe. Its trajectory provides an instructive case study in where distributed ledgers deliver tangible value for an IP owner today.

What happened to the patent NFTs?

IPwe set out to transform intellectual property management by representing patents as non-fungible tokens, or NFTs. Each patent NFT aimed to consolidate key legal and technical data into a single digital record, with the goal of accelerating due diligence and executing licensing transactions through smart contracts.

The concept addressed a genuine market friction. Patent intelligence is fragmented across regional registries, proprietary databases, and internal enterprise archives. Evaluating an unfamiliar portfolio demands substantial diligence, high legal costs, and significant administrative time. Consolidating that information into a standardized digital record promised a shared baseline for owners, prospective buyers, and financing partners alike.

Commercial reality proved far less forgiving. As the EUIPO report recounts, IPwe failed to gain sufficient market traction and entered bankruptcy in 2024. Crucially, the EUIPO report distinguishes between commercial friction and technological failure. It attributes the collapse to weak market demand and unresolved uncertainty regarding the securities-law status of patent NFTs, rather than an inherent defect in distributed ledgers.

That distinction carries an essential lesson. Minting a token is a straightforward technical procedure. Building a functioning, liquid secondary market requires willing buyers, tested transaction structures, clear regulatory boundaries, and a compelling reason for conservative market participants to abandon established legal mechanisms. IPwe showed the immense distance between a working technical proof of concept and a self-sustaining commercial marketplace.

For an innovator preparing intellectual property for financing, the immediate priority lies elsewhere. Before an intangible asset can ever be traded, the company must first build durable, verifiable evidence of what it owns and controls.

A useful record before a tradable asset

Consider an industrial manufacturer developing a proprietary production method. The commercial value of that know-how resides in engineering drawings, laboratory test results, chemical formulations, and iterative operational manuals. Taken together, these materials define the proprietary asset and demonstrate operational control over the trade secret.

Certifying those materials as research progresses produces an objective, tamper-proof audit trail. A cryptographic fingerprint uniquely identifies each source file, and anchoring that fingerprint to Bitcoin establishes a permanent, publicly verifiable reference point. Throughout this process, the underlying trade secrets remain private.

This workflow directly supports claims of ownership and chain of title. The business can connect certified technical milestones to employment agreements, assignment records, and internal project logs, assembling a coherent and verifiable evidentiary package. When a lender, appraiser, or investor examines the portfolio, they work from updated, tamper-proof documentation rather than a hurried retrospective narrative assembled under deadline pressure.

The commercial advantage takes effect immediately. It does not require a novel token exchange to achieve market liquidity, nor does it depend on patent NFTs gaining regulatory approval as financial instruments. Instead, it strengthens the company’s negotiating position inside the conventional financing and licensing transactions it already conducts.

The choice of blockchain matters

The architectural design supporting an IP record determines whether that evidence will remain legally defensible across decades.

IPwe’s platform operated on a hybrid architecture. According to the Hyperledger Foundation’s February 2023 announcement, cited by the EUIPO, the system paired the public Casper blockchain with a private, permissioned Hyperledger Fabric network. This hybrid structure sought to link enterprise data held on a closed consortium ledger with tokenized assets represented on a public chain.

Private, permissioned networks serve specific operational needs when a known group of corporate partners must coordinate workflows and control access to shared information. For an IP owner seeking evidence that remains defensible over the long term, however, private ledgers introduce severe counterparty risks. A permissioned network depends entirely on the consortium members continuing to fund, operate, and maintain the infrastructure. If those members dissolve the partnership, change strategic priorities, or face insolvency, the network and its validation mechanisms can disappear.

The public layer provided similarly fragile assurance. Casper remains operational, but its live explorer showed just 71 active validators on 26 October 2026. Such concentration introduces direct evidentiary risks: following a July 2024 exploit, validators coordinated to halt the network for several days and replace two historical blocks, as Casper’s own incident report documents. When preserving records across decades, the label “public” is not enough on its own. If a small group of operators can pause the ledger and alter recorded history, the network loses the neutral immutability required for durable legal proof.

This vulnerability becomes critical when dealing with assets that possess a long commercial lifespan. A proprietary production process may remain in active use long after its original creators have departed. A patent portfolio might be licensed, assigned, or pledged as collateral fifteen years after its initial filing. The legal evidence must travel with the asset through corporate reorganizations, portfolio sales, and successive rounds of financing.

Bitcoin provides the durability required for that continuity. Its ledger is maintained by a global, decentralized network that has mostly operated without interruption since 2009. Anyone can verify an anchor on Bitcoin independently, without requesting permission from a consortium or relying on the survival of the vendor that registered the initial timestamp. Its decentralization, operational longevity, and open verifiability make Bitcoin an exceptionally dependable foundation for permanent IP records.

Why Bernstein builds on Bitcoin

Bernstein anchors the cryptographic fingerprints of certified IP assets directly to Bitcoin. The public reference point exists on an open ledger, completely outside Bernstein’s internal systems.

Confidentiality is protected at the source. Files are encrypted locally on the owner’s device before any data is transmitted. As a result, sensitive proprietary materials are never disclosed to Bernstein, and trade secrets are never broadcast to a public blockchain.

To ensure broad evidential weight across legal jurisdictions, Bernstein pairs this Bitcoin anchor with certified electronic timestamps from recognized authorities, including EU qualified and China trusted timestamps. Innovators can export their complete cryptographic certificates alongside the original files and the independent verification protocols. With this package secured, the company retains self-contained proof that any court, lender, or auditor can verify independently, even if Bernstein ceased operations tomorrow.

For the manufacturer in our example, every key engineering milestone becomes a certified revision. When debt financing or private equity investment is on the table, the company and its IP counsel can present a clean, chronological dossier of the asset. They can share access with authorized reviewers under appropriate non-disclosure terms, using the certified timestamps as an unalterable, shared baseline throughout due diligence.

Selecting the right underlying infrastructure is practical risk management. An evidence system delivers genuine commercial value only when its legal validity outlives the commercial relationship with the service provider that created it.

Evidence that future markets will also need

The EUIPO report remains optimistic about the future role of distributed ledgers in IP finance. In its analysis of securitisation, the report highlights how distributed ledgers could record ownership histories, track licensing assignments, and support the administration of cash flows within structured finance vehicles.

That EUIPO’s vision aligns directly with the preparatory work companies can undertake today. Whatever form a future financial transaction takes, both lenders and rating agencies will still demand a clear, verifiable picture of the underlying asset. A thoroughly documented development history, clean proof of chain of title, and clearly identified version histories give any transaction a stronger legal and financial footing.

For business owners and IP counsel, the strategic path forward is straightforward and practical. It begins with identifying a core proprietary asset and gathering the materials that establish legal ownership and control, from technical schematics to contributor agreements and assignments. Once that baseline dossier is certified, the team simply maintains the record as the technology evolves, storing the exported cryptographic certificates alongside the original source files.

Over time, this disciplined approach creates an asset that cannot be fabricated retrospectively: an unimpeachable, contemporaneous record built in lockstep with the invention itself. When an investor, commercial partner, or bank asks what the company owns, the verifiable proof is already waiting.

The fourth and final article in this series will translate these principles into a practical readiness checklist, giving innovators and their advisers a step-by-step framework to prepare intangible assets for capital markets.

Explore how Bernstein helps you build a certified, independently verifiable record of your IP.

Sources

European Union Intellectual Property Office. IP-backed Finance. Section 3.1.6, printed pages 68-69, on patent NFTs and IPwe’s bankruptcy; section 3.1.11, printed page 81, on distributed ledgers and IP securitisation. April 2026
Hyperledger Foundation. IPwe Launches Revolutionary Platform and Deployment of 25 Million Patent NFTs on Hybrid Casper Blockchain and Hyperledger Fabric Network. 2 February 2023
Casper Association. Casper Blockchain Security Update: Preliminary Incident Report
Casper Association. Casper Security Incident Has Been Resolved; Network is Fully Operational
Casper live explorer. Active-validator snapshot cited as of 26 October 2026

From first sketch to final collection: building evidence of your designs

Marco Barulli — Wed, 21 Oct 2026 00:00:00 GMT

Updated: 2026-10-21

What a French fashion dispute can teach designers about timestamping, confidential sharing and preserving their work.

When French fashion house AZ Factory took clothing wholesaler Valeria Moda to court over counterfeit garments, it introduced an unconventional piece of evidence: blockchain timestamps proving its design files predated the infringing copies.

The dispute centered on two signature creations, Love from Alber and Hearts from Alber. Valeria Moda challenged both the infringement claims and AZ Factory’s underlying copyright ownership. AZ Factory faced a dual burden: proving its chain of title and establishing an incontrovertible timeline of creation.

On 20 March 2025, the Marseille Judicial Court ruled in AZ Factory’s favor. Central to the decision were two blockchain timestamps registered on 5 May and 15 September 2021. An independent bailiff’s report from 19 October 2022 corroborated these records. In France, a bailiff (commissaire de justice) is an authorized legal officer whose formal observations carry significant evidentiary weight in court; here, the report documented the formal verification of the timestamp records. Alongside evidence of public release under AZ Factory’s name, the court accepted the timestamps as legitimate proof of prior existence. (Read the full EUIPO case summary).

For creators across fashion, jewelry, and furniture design, the takeaway is clear: the strongest defense against infringement is built while the work is taking shape, long before a dispute surfaces. Contemporaneously certifying and preserving your designs as they evolve establishes a verifiable, objective record of what you created and precisely when.

What the timestamp contributed

Digital files are inherently fragile evidence. Operating system metadata—such as file names and local “Date Modified” stamps—carries little weight in court. Files are routinely renamed, moved, duplicated, and re-exported, altering local timestamps in the process. When an infringement dispute arises years later, local file metadata rarely withstands legal scrutiny.

A blockchain timestamp anchors the file to an immutable reference point outside your personal computer.

The process begins with a cryptographic hash, a unique digital fingerprint calculated mathematically from the file’s contents. If a single pixel, curve, or character changes, the hash changes completely. Anchoring this fingerprint into a public ledger like Bitcoin provides tamper-resistant proof that the exact matching file existed on or before that entry was recorded. Beyond verifying existence and integrity, this mechanism also establishes proof of possession: by demonstrating control over the private key used to sign the Bitcoin transaction containing that fingerprint, the owner can provably show they held the file at the time of registration.

Crucially, only the fingerprint is written to the blockchain; the design file itself remains entirely private. This distinction is vital when handling unreleased collections, sensitive client proposals, or proprietary prototypes. You can establish incontrovertible proof of prior existence without exposing commercial assets on a public ledger.

However, you must keep the exact source file. A blockchain certificate cannot reconstruct a misplaced sketch, nor can it validate an export altered after the timestamp was generated. (In this post, we break down three common ways you might inadvertently sabotage your own digital certificates. )

Show how the design evolved

A solitary timestamp answers a narrow question: Did this specific file exist by this date?

In copyright disputes, however, an organic creative trail tells a far more compelling story. A persuasive narrative rarely starts with a polished final export; it begins months earlier with the first rough sketch, pattern experiments, revised color palettes, factory sample revisions, and technical production packs.

By certifying these milestones throughout development and maintaining them within a version-controlled project, you build an unbroken chronology of creation. Each certificate benchmarks a specific iteration. Together with the stored source files, these records allow a judge, adversary, or examiner to trace how a concept matured into a finished design.

This developmental history reinforces your final claim. It proves that distinctive aesthetic features were not copied at the last minute, but evolved organically across revisions. An infringer claiming independent creation will struggle to counter a dated, chronological trail of iterative work. Crucially, this record cannot be retrofitted: certifying a batch of legacy drafts today only proves they exist today, not when they were originally drawn.

Chronological proof must also connect directly to the individuals involved. Always store design briefs, contributor agreements, sign-offs, and delivery emails alongside your certified files. Anyone can timestamp an arbitrary digital file; timestamping someone else’s work does not grant ownership. Regular timestamping does not create copyright—it supplies the verifiable evidentiary foundation needed to enforce it.

Three situations where this matters

Certification and secure storage serve distinct, complementary roles. Certification delivers a legally defensible, verifiable date; storage preserves the exact source files required to substantiate it. Encrypted, versioned storage ensures your confidential iterations remain protected without being overwritten as designs evolve.

Before production begins, you often need to share technical drawings, patterns, or renders with external manufacturers for quoting. The risk of leaks or unauthorized copying is high. Even with a signed non-disclosure agreement (NDA), parties frequently dispute which specific files were covered.

Before sharing, certify the collection and securely store that exact version. Reference the certificate’s unique identifier directly in the NDA or its annex. This binds both parties to an unambiguous, tamper-proof inventory of disclosed files without embedding large, proprietary designs into the contract text itself. Keep an audit trail of what was sent and to whom.

When design revisions occur, update the certified references accordingly. The agreement defines the legal obligations; the certificate and stored files establish the exact subject matter. See our guide on the NDA and contracts use case.

2. Managing fragmented studio workflows

Modern creative workflows are rarely linear. An illustrator sends a draft by email, a colleague adjusts the color scheme, and a freelance CAD specialist delivers the production files. If team members depart or a client questions a design’s provenance months down the road, reconstructing its history across scattered inboxes and shared drives is nearly impossible.

Consolidating versions into a centralized project and certifying them upon arrival preserves the creative chain of custody. Storing contributor identities, copyright assignments, and sign-offs alongside the timestamped files allows you to instantly trace every contribution and defend your intellectual property.

3. Defending against lookalike launches

A competitor debuts a product unmistakably derived from yours. You scramble to assemble evidence, only to find your working directory contains only the latest production export—dated weeks after the competitor’s launch—while earlier working sketches were overwritten or discarded.

If you have systematically certified and stored iterative milestones, you can readily retrieve earlier drafts and their corresponding timestamps. Demonstrating that signature motifs existed in your studio months before the competitor’s release shifts legal leverage decisively in your favor. A timestamp secured today cannot rescue an overwritten file from last year, making proactive archiving essential.

Build the evidence as you work

Bernstein unifies certification, storage, and secure sharing into a single creative workflow. Encrypted, version-controlled storage safeguards your proprietary files as concepts evolve, while Secure Sharing lets you govern access, log recipient consent, and maintain an immutable audit trail. Certificates integrate directly into contractual agreements to identify protected IP unambiguously.

Should you ever need to demonstrate ownership or provenance, every file and its corresponding cryptographic proof are instantly accessible. Using Bernstein’s validator, you, your legal counsel, or opposing parties can independently verify file authenticity without complex technical workflows.

For an in-depth legal analysis of the admissibility of cryptographic proof across international courts, read our open-access study: Blockchain Evidence in Court: A Cross-Jurisdictional Study of Admissibility and Weight.

Sources

European Union Intellectual Property Office. The Court of Marseille recognised blockchain timestamping as legitimate evidence of copyright ownership. Case summary: Tribunal judiciaire de Marseille, First Civil Chamber, RG 23/00046, judgment of 20 March 2025. Accessed 27 October 2026
Marco Barulli and Paul Reboh. Blockchain Evidence in Court: A Cross-Jurisdictional Study of Admissibility and Weight. Working paper, v3, website edition. October 2026

No data, no deals: the evidence gap in IP finance

Marco Barulli — Tue, 20 Oct 2026 00:00:00 GMT

Updated: 2026-10-20

Why do lenders hesitate to accept IP as collateral? The EUIPO describes a vicious circle of missing data. Learn what lenders actually need to see, and how your company can break the cycle by providing verifiable evidence.

In IP-backed finance and the disclosure paradox, we looked at a difficulty facing companies seeking finance against their intellectual property: how to give others enough information to assess an asset while preserving its confidentiality.

This time, we cross to the other side of the table. Suppose the company is ready to share that information. Why do lenders still hesitate?

The EUIPO’s 2026 report on IP-backed finance describes a vicious circle. Too few transactions produce too little data. Without reliable data, lenders remain cautious. And cautious lenders make fewer deals.

Breaking that circle requires coordinated work across the financial system. But part of the answer begins much closer to home, with the company’s records and the advisers who understand its assets.

The vicious circle

A bank considering a loan against machinery has something concrete to work with. There are established markets, comparable sales and experience of recovering value when borrowers default.

For IP, those reference points are harder to find. A patent portfolio, a proprietary process and a body of software may each be valuable, but assessing what could be recovered from them is a different exercise. Their usefulness may depend on particular people, complementary technology or a business that knows how to put them to work.

The report describes the resulting caution: lenders apply substantial discounts to estimated values or leave IP out of their recovery calculations altogether.

That caution is difficult to overcome without experience. Lenders need evidence of how IP-backed loans perform, what happens when borrowers default and how much can ultimately be recovered. Yet each institution has little incentive to build that experience alone.

What the report proposes

The EUIPO proposes public guarantees to share lending risk, better data on repayments and recoveries, and a central register of IP pledges to help lenders assess competing claims.

These measures would give lenders more confidence and better reference points. They require coordination and time. Meanwhile, companies can prepare the information every transaction will need: a clear, verifiable account of the assets being offered.

What a lender needs to know about one asset

Consider a company offering proprietary software or a manufacturing process as part of a financing proposal. Before a lender and its advisers can assess it, they need a clear account of what the company holds.

Four questions provide a useful starting point.

What exactly is it?
A registered right has an entry in a public register. A body of source code, a dataset or a confidential process needs another way to establish its boundaries. Which files, versions and supporting materials make up the asset? A description such as “our production software” leaves considerable room for uncertainty.

Who owns it, and since when?
The history may involve founders, employees, contractors and acquired businesses. Assignment agreements and development records help explain how their contributions became part of the company’s assets. A clear chain of title makes that history easier to examine.

Which version is being assessed?
Software changes, datasets grow and processes improve. The parties need to know which version they reviewed and how later developments relate to it. Keeping a dated history allows them to return to the same reference point.

How has confidential material been shared?
For trade secrets and know-how, the conditions of disclosure matter. Who received access, to which material, and under what agreement? A documented sharing history helps advisers understand how confidentiality has been managed.

The answers also help reveal dependencies. A process may require specialist knowledge to operate; software may rely on components licensed from others. Identifying those connections early gives everyone a more useful picture of the asset.

How Bernstein helps build those answers

Much of the information comes from the company’s daily work: development files, contracts, technical documentation and records of disclosure. Bernstein gives those materials a certified history that the company can present and a lender’s advisers can check.

Its role is concrete in each of the four questions.

Identify the exact asset.
Bernstein creates a cryptographic fingerprint of the files in a certified revision. Counsel can reference that revision in an asset description or supporting agreement, giving the parties a precise set of materials to refer to. Files are encrypted before leaving the owner’s device, so even sensitive code, formulations and process documentation can be included without exposing their contents to Bernstein.

Document its history and support the ownership review.
Bernstein anchors fingerprints to the Bitcoin blockchain and trusted timestamp authorities, including EU qualified timestamps. Certifying development records alongside assignments and other agreements gives counsel dated evidence to examine when reconstructing who contributed what and how the company acquired its rights.

Preserve the version under review.
Bernstein keeps immutable, dated revisions together with the encrypted original files. If the software develops during a financing discussion, the version initially reviewed remains available. The lender’s advisers can check that a file matches its certificate and distinguish it from subsequent revisions.

Control and record disclosure.
When a valuer or lender needs access, Bernstein’s secure sharing provides time-limited links, one-time passwords, contract acceptance before access and verifiable access logs. The company can share the relevant material and retain a record of access through that channel.

Together, these capabilities turn a collection of working files into a verifiable record of the asset’s development and disclosure.

For example, a software company preparing for financing could certify a release together with its technical documentation, preserve the relevant contributor agreements, and give a valuer controlled access to that revision. If development continues during the review, everyone can still identify the version on which the assessment was based.

The evidence also remains usable beyond the immediate transaction. Certificates can be verified independently of Bernstein, and owners can export them with the original files and the materials needed for later verification. Preserving that package allows future reviewers to examine the same evidence.

A role for IP counsel

IP counsel brings two kinds of knowledge to a financing discussion: the technical understanding needed to assess the innovation, and familiarity with the client’s assets and how they were developed.

Together, these help counsel explain what a lender is being asked to assess: which assets underpin a product or process, how they relate to one another, and which agreements and records support the company’s rights. For software, trade secrets and know-how, that context can be particularly valuable because much of it will never appear in a public register.

An adviser who knows the client’s development history can also spot what is missing. A contractor’s contribution may need a clearer assignment. An important process may be poorly documented. The version offered for review may differ from the one described in an earlier agreement. Addressing these questions before the financing discussion makes the subsequent review easier.

Bernstein gives counsel a practical way to preserve and substantiate that work. Counsel determines what belongs in the evidence file, connects the technical materials with their legal history, and decides what a reviewer needs to see. Bernstein certifies the selected records, preserves their versions and supports controlled disclosure.

This makes the adviser’s knowledge easier to share with lenders and valuation specialists. They receive a coherent account of the assets, supported by evidence they can examine directly.

Breaking the circle from the inside

The wider market needs more transactions, better data and institutions willing to share risk. Companies and their advisers can contribute by making the assets behind each proposed transaction easier to understand.

That work can begin well before a loan application: identify the assets, preserve their development history, connect them to the relevant agreements and keep track of disclosure. Bernstein makes certification, preservation and controlled sharing part of that ongoing process.

For IP counsel, it is a natural extension of knowing the client and protecting its innovation. When a financing opportunity arises, the company has a documented history ready for review, rather than a reconstruction to begin.

The next article looks more closely at blockchain’s role in IP finance, from the ambitions surrounding tokenised patents to its practical use in creating verifiable records.

Explore how Bernstein helps you build a certified, independently verifiable record of your IP.

Sources

European Union Intellectual Property Office. IP-backed Finance. Executive Summary; sections 2.1.2, 3.1.2 and 3.1.7; Priorities 3 and 4. April 2026

Your certificate is immutable. Your files are not.

Marco Barulli — Fri, 16 Oct 2026 00:00:00 GMT

Updated: 2026-10-16

How everyday tools can change certified files without an explicit save, and why preserving the exact original matters.

You care about your intellectual property, so you take the proper precautions: you obtain digital timestamps from qualified trust authorities to legally establish that your work existed at a specific point in time.

You store the certificates securely. You keep the files intact. You never intentionally edit or alter them.

Then, when the stakes are high (e.g. defending your copyright or proving prior use in a trademark dispute) you run the verification. It fails.

How does cryptographic proof collapse without any conscious mistake? The answer is subtle: everyday desktop tools routinely alter files in the background without prompting you and without you ever clicking “Save.”

Here are three common scenarios that silently break your chain of custody:

1. Reviewing a PDF in macOS Preview

You open a document, a technical drawing or a schematic. A page is sideways, so you rotate it 90 degrees to read it, then close the window. Because Preview autosaves continuously in the background, closing the window commits that change directly to disk. You never pressed Save, but the underlying file has been rewritten—and the certified hash is permanently broken. (Apple documentation)

2. Rotating a photo in Windows File Explorer

You browse photos of a prototype in Windows. One photo appears sideways, so you click “Rotate right.” The image still shows the exact same invention, but Windows writes that orientation metadata directly into the file structure. Even a “lossless” rotation alters binary data. To human eyes, the image is unchanged; to a cryptographic verification algorithm, it is an entirely different file. (Microsoft documentation)

3. Playing an audio track in iTunes

You import a demo or interview recording into your library to listen to it. If features like Sound Check are enabled, the player can write volume-normalization tags directly into the file’s ID3 metadata. The recorded audio has not changed by a single millisecond, but the container has. The digital fingerprint no longer matches. (ID3 documentation)

Three routine actions: reviewing a document, organizing photos, playing a recording. Three everyday ways to inadvertently sever the link between a certificate and its source file.

A certificate cannot reconstruct the original

A digital certificate anchors a strict cryptographic hash. Change a single bit, even invisible metadata buried in a file header, and the fingerprint mismatch is absolute.

This is true whether your proof is anchored on Bitcoin or issued by a qualified timestamping authority. Neither system can resurrect a lost or modified original; they only attest to the exact sequence of bytes registered at that moment. Overwrite every unaltered copy, and the certificate becomes functionally worthless.

Preserve the version you certified

Your active work shouldn’t have to live under glass. You need to review blueprints, organize design assets, and listen to recordings without accidentally compromising your legal proof.

That is why Bernstein couples cryptographic certification with encrypted, versioned storage. Certified versions remain frozen and verifiable as your project develops, while client-side encryption ensures your proprietary assets remain strictly confidential. See: Bernstein features.

An immutable certificate is only as strong as the file it preserves.

Sources

Apple. Save files in Preview on Mac. Preview User Guide. Accessed 27 October 2026
Microsoft. JpegBitmapEncoder.Rotation Property. System.Windows.Media.Imaging; .NET API documentation. Accessed 27 October 2026
ID3.org. iTunes Normalization settings. COMM: iTunes normalization settings and the iTunNORM tag. Last edited 25 November 2013. Accessed 27 October 2026

IP-backed finance and the disclosure paradox

Marco Barulli — Tue, 13 Oct 2026 00:00:00 GMT

Updated: 2026-10-13

The EUIPO's 2026 report puts 'make IP visible' first on the road to IP-backed finance. For trade secrets and know-how, visibility is the risk. How to disclose the proof without disclosing the secret.

In April 2026 the EUIPO published a foundational report on IP-backed finance: how European companies could use their intellectual property to raise credit and capital, and why today they mostly cannot. It is a long document, 131 pages, written for policymakers and financial institutions. It deserves a wider readership than that.

The figures in the report show why every IP-rich company should pay attention. It estimates the EU’s SME credit gap at up to EUR 365 billion a year, and the share attributable to IP-rich firms at EUR 70-150 billion a year. With the right infrastructure for disclosure, valuation and risk-sharing, it expects IP-backed instruments could mobilise EUR 30-120 billion a year in new financing. IP-intensive industries already generate around 48% of EU GDP. The timing matters too: the Savings and Investment Union is being designed now, and the report’s central argument is that freed capital “flows to where it can be assessed, priced and deployed with confidence.” If IP cannot be assessed, the capital will go elsewhere.

The report maps 18 possible actions across three pillars and orders the most actionable into five priorities: make IP visible, assign it a credible value, leverage that value into lending, build the evidence base, and reinforce coordination. Most of these are jobs for regulators, banks and IP offices, and some will take years.

But every one of them also asks something of the companies that own the IP and of the lawyers who advise them. That side of the story is what this series is about. Over four posts we will read the report from the innovator’s chair:

The disclosure paradox (this post): why the first priority collides with the nature of the asset.
The vicious circle: what a lender actually needs to know about an IP asset, and which part of that you control.
Blockchain in IP finance: what the report gets right about tokenisation, and what it leaves out.
Readiness: a practical checklist for being financeable when the instruments arrive.

Priority 1 runs into a wall

The report’s first priority is to make IP visible. “Before IP can be used for financing, it must be visible, structured and understandable by financial actors.” The starting point is low. Citing earlier EUIPO survey data, the report notes that only 13% of IP right owners have ever tried to obtain financing through their IP assets, and a large majority have never had a professional valuation.

Part of the reason is accounting. IAS 38, the international accounting standard for intangible assets, lets a company show the IP it develops itself as an asset only in narrow cases. Most of that work is booked as an expense, so it never appears on the balance sheet, however valuable it is. The report proposes a voluntary disclosure framework to fill that gap. Its starting point would be the IP Scan, an IP check-up already available to small businesses through the SME Fund, the EUIPO’s grant scheme for EU-based SMEs: an expert designated by the national IP office reviews the company’s business and its IP, and recommends a strategy, with most of the cost reimbursed. The report would turn it into a financing-oriented disclosure tool covering “both registered IP rights and other relevant intangibles.”

The other reason matters most for IP counsel. The report describes innovation finance as a market with severe information asymmetry: investors cannot tell good projects from weak ones, so they price everything as average. Telling them more does not work well, because “innovative ideas can be imitated” and “companies hesitate to share details due to competitive risks, weakening the credibility of their signals.” Elsewhere it notes that disclosure about intangibles “may undermine the firm’s competitive position” and that fear of spillovers to competitors keeps firms quiet.

In other words, the first step towards IP-backed finance asks innovators to do the one thing their IP strategy tells them not to do.

Why it bites hardest on unregistered IP

For registered rights the tension is mild. A granted patent is already public, and the register is the evidence. A lender can look it up.

The problem is everything that is not registered, which in many technology companies is most of the value: source code, process know-how, formulations, training data and models, design files, lab records. Here, secrecy is not a preference. Under the EU Trade Secrets Directive (2016/943), information is protected as a trade secret only if it has been subject to reasonable steps to keep it secret. Each disclosure to a lender, a valuer or an investor is a small erosion of the very thing that makes the asset valuable and protectable.

NDAs help, but an NDA governs how the other side behaves with your information; it does not record what that information was, or when you had it. And a lender asked to accept “we have valuable know-how, trust us” will do what the report says lenders do today: apply a heavy haircut, or leave the asset out altogether.

So the innovator is stuck between two bad options. Disclose, and weaken the asset. Stay quiet, and the asset does not count.

Separate the proof from the content

There is a third option, resting on a simple piece of cryptography. A fingerprint (hash) of a file identifies that exact file. Anyone holding the file can recompute it and check it matches; nobody holding only the fingerprint can work back to the file.

Fix that fingerprint in time with an independent, verifiable timestamp, and you have a sealed envelope with a postmark nobody can forge. It proves that a specific piece of work existed on a specific date and has not changed since, while revealing nothing about its content. Whoever you later allow to open it can check for themselves that it is what you certified.

For IP-backed finance this changes the disclosure step. A company can show a lender a structured inventory of its unregistered assets, each with a certified date and an integrity proof, without handing over a line of the underlying work. When a valuer or the lender’s counsel needs to go deeper, the material can be opened to them alone, with a record of who saw what.

How Bernstein does it

This is what Bernstein has done since 2016. It is an Innovation Evidence Platform: it produces proof of existence, ownership and integrity for digital assets without exposing their content.

Files are encrypted in your browser before they leave your device. Only the fingerprint is used for certification. Bernstein cannot read your content, which is why the evidence can cover your most sensitive material.
The fingerprint is anchored to the Bitcoin blockchain, to EU qualified timestamps under eIDAS, and to a China timestamp authority. For European counsel, the eIDAS anchor carries a legal presumption: under Article 41(2) of the eIDAS Regulation, a qualified electronic timestamp enjoys a presumption of the accuracy of its date and time and of the integrity of the data it is bound to.
Every certification produces a certificate anyone can verify independently, without Bernstein. A lender does not have to trust us, or you.
The certified files themselves are kept, encrypted and versioned. A fingerprint is only useful if you can still produce the exact file it was made from, byte for byte. Over years or decades that is harder than it sounds: files get migrated between systems and re-saved, and some software silently rewrites a PDF’s metadata just by opening it. Change a single byte and the file no longer matches its proof. Bernstein stores the originals exactly as certified, so they are still there, unaltered, when the proof has to be checked.
Revisions are immutable and dated, so the record shows how the work developed, not only that it existed.
Sharing is controlled and logged: time-limited links, one-time passwords, contract acceptance before access, and hash-chained access logs. The same record that supports a valuation also documents the reasonable steps you took to keep the information secret.

What Bernstein does not do is value your IP or decide whether a bank will lend against it. Those remain the work of valuers, lenders and the policy changes the report describes. What it does is remove the reason to stay invisible: you can make an asset legible to a financial counterparty without giving it away.

Disclose the proof, not the secret

The EUIPO is right that IP must become visible before it can be financed. For unregistered IP, the practical way to get there is not more disclosure of content but better disclosure of evidence: what exists, since when, held by whom, and unchanged. That is information a lender can use and a competitor cannot.

In Part 2, we move to the lender’s side of the table. Even when IP is visible, the report finds that banks still discount it heavily, because of a vicious circle in which no transactions means no data, and no data means no transactions. We look at what a lender actually needs to know about a single IP asset, and which part of that answer only the owner can supply.

If you want to see how a certified, verifiable record works in practice, you can find out more at bernstein.io.

Bernstein provides evidence, not legal advice, and does not replace patents, trademarks or contracts.

Sources

European Union Intellectual Property Office. IP-backed Finance. Executive Summary; section 2.1.1 (information asymmetry); section 2.2.2 (identification of intangibles, IAS 38); section 4.1 (Priority 1: make IP visible). April 2026
European Union Intellectual Property Office. IP Scan. SME Fund 2026: IP Scan vouchers

Make employee NDAs more robust with a verifiable record of confidential knowledge

Marco Barulli — Thu, 08 Oct 2026 00:00:00 GMT

Updated: 2026-10-08

Connect employee NDAs to a verifiable record of confidential knowledge, from onboarding through project development to departure, without reproducing sensitive content in employment paperwork.

When an employee joins a company, they need access to knowledge that makes their work possible. When they leave, confidentiality obligations need to remain connected to the information they received and helped develop.

An NDA establishes obligations. Bernstein helps give those obligations an identifiable reference: preserved project files, certified versions, and sharing under expressly accepted conditions.

This connection matters at three moments: onboarding, project development and departure.

Consider Alex, a hypothetical employee joining Acme to work on a technical project.

Onboarding: certify the knowledge that already exists

Before giving Alex access, Acme collects the confidential project materials relevant to their role. These might include source code, technical specifications, experimental results or a documented manufacturing process.

The company uploads and certifies a baseline revision in Bernstein before Alex joins the project.

Files are encrypted client-side before transmission. Their cryptographic fingerprints are anchored to the Bitcoin blockchain and timestamp authorities, creating independently verifiable evidence of the certified content’s existence and integrity at a particular time. The confidential content itself is not published on the blockchain.

Acme now has a preserved reference for the project knowledge that predates Alex’s involvement. If Alex later claims that particular material originated with them during their employment, the company can produce the earlier files and their corresponding certificate. The baseline supports that factual distinction; employment agreements and contribution records establish the surrounding rights.

Refer to confidential collections without reproducing them

The same certified revision can serve as a reference in Alex’s confidentiality agreement.

Acme prepares a collection of the materials it intends to cover. The agreement identifies that collection by its project name and Bernstein certificate ID, and defines the confidentiality and permitted-use obligations attached to it.

The technical content remains in the encrypted repository. There is no need to reproduce formulas, source code or experimental details in the employment paperwork merely to identify the collection.

This is useful when the protected knowledge spans hundreds of files or contains information that should not circulate with ordinary contracts. Those contracts may later pass through legal reviews, audits or due diligence. A certificate reference allows them to point to a fixed collection without carrying its sensitive contents.

Where the intended scope is the entire certified collection, the agreement can say so expressly, subject to its exclusions, such as information already public or independently developed. A dedicated collection makes this simpler than referring to a mixed project archive and trying to describe confidential subsets in the agreement.

Where detailed verification is needed, the underlying materials can be made available to authorized reviewers through controlled sharing. The certificate provides the reference against which those files can be checked.

Acme then shares the certified collection with Alex through Bernstein.

Sharing can require recipient verification and in-app acceptance of confidentiality terms before access. Those terms can define the permitted purpose, restrictions on further disclosure, and responsibilities for handling the information.

Acme keeps the certified collection, the applicable terms and the record of Alex’s acceptance connected in its documentation.

Each element serves a distinct purpose:

The certified revision fixes the content of the collection and provides verifiable evidence of when it existed.
The confidentiality terms define the obligations attached to that collection.
Alex’s acceptance documents their agreement to those conditions.

The resulting arrangement is more concrete than a standalone NDA referring broadly to company information. Alex is given access to an identifiable body of knowledge under explicit conditions, and Acme preserves the version to which those conditions refer.

During employment: keep the record current

A project changes as people work on it. The onboarding baseline should therefore become the first entry in an ongoing record.

Acme establishes a certification routine around meaningful updates: design changes, development milestones, new experimental results or other significant additions. Bernstein’s immutable revisions preserve successive states of the documented content.

This history helps distinguish the knowledge that existed before Alex joined from developments made during their employment.

The company can use these certified references in project acknowledgements, updated confidentiality schedules or agreements concerning new work. When needed, contribution records can be preserved alongside the technical materials.

When additional material is shared, its certified reference can be connected to the confidentiality terms governing that disclosure.

The benefit is continuity. The company’s agreements and its documented knowledge remain connected as the project evolves.

Departure: refer to an identifiable body of confidential information

When Alex leaves, Acme prepares a current certified revision and a confidentiality schedule for the departure documentation.

The schedule identifies the project and the Bernstein certificate IDs corresponding to the covered collections. The departure agreement or acknowledgement refers expressly to that schedule when restating continuing confidentiality and permitted-use obligations.

This provides a fixed reference for the documented project knowledge at departure. If the scope is later disputed, the company can retrieve the preserved files and verify that they match the referenced certification.

Relevant earlier revisions should also be included. Alex may have received an abandoned design, an earlier formulation or a historical analysis that no longer appears in the latest project files. The revision history allows the company to account for that information without relying solely on the project’s final state.

As at onboarding, these references avoid reproducing sensitive technical details in the departure paperwork. The detailed content stays securely preserved, while the agreement identifies the collections to which the continuing obligations apply.

The departure record reinforces the obligations established during employment and makes their subject matter more specific.

Keep the evidence confidential and available

Preserving evidence should not require unnecessary disclosure of the information being protected.

Bernstein combines client-side encryption, immutable revisions and sharing with recipient verification and acceptance of terms. Acme can preserve its confidential project materials and make them available to Alex under defined conditions.

This separation is central to the workflow: agreements refer to identifiable certified collections, detailed content remains protected, and the originals are preserved for verification when required.

Certification fixes the reference. The confidentiality agreement defines the obligations. Neither requires the company to expose its technical knowledge in paperwork that may circulate more widely.

Give confidentiality obligations a concrete reference

With Bernstein, Acme can connect Alex’s employment to a documented sequence:

Certify the project baseline before onboarding.
Share the relevant collection under expressly accepted conditions.
Preserve certified revisions as the project develops.
Reference the relevant certified collections in departure documentation.

The result is a clearer connection between the company’s knowledge, the information made available to the employee, and the obligations attached to it.

That is how Bernstein can make employee NDAs more robust: by giving confidentiality agreements a precise, verifiable reference while keeping the underlying knowledge securely preserved.

Insights by Bernstein: Read

The question that stalls indie game deals: “Who owns what?”

What, exactly, are you protecting?

Connect assets to the people and agreements behind them

Preserve the development history before you need it

Keep the exact files behind the evidence

Record what leaves the studio

Start with your next milestone

How Bernstein supports this process

Sources

When Institutions Play Startup: The Cautionary Tale and Demise of WIPO PROOF

The Genesis of an Institutional Mismatch

The Commercial Reality: 3,000 Tokens and a Broken Pricing Model

Technical Commoditization and Legal Ambiguities

The Leadership Course Correction: A Return to Multilateral Focus

Lessons for the IP Ecosystem: Where Proof Truly Belongs

Securing Your Legacy Assets Ahead of January 2027

A Permanent Home for Your Evidence:

Sources

Is your IP ready to be financed? A checklist built on the EUIPO's five priorities

Priority 1: Make IP visible

Priority 2: Assign credible value to IP

Priority 3: Leverage IP value into lending

Priority 4: Build the evidence base

Priority 5: Reinforce coordination

The one element you cannot retrofit

Closing the series

Sources

EU Qualified Ledgers: A Legal Privilege No Technology Earned

A Ledger in Name Only

An Audit Is Not a Guarantee

Evidence Must Outlast the Vendor

The Presumption Stops at the Border

Use the Badge, Don’t Build on It

Sources

Before You Submit: How to Protect Your Architectural Work

Preserve how the design became yours

Be clear about what submitting allows

Keep the exact package that leaves the studio

Choose the public reveal deliberately

Connect publication to the work behind it

Conclusions

Sources

Blockchain in IP finance: the lesson of patent NFTs

What happened to the patent NFTs?

A useful record before a tradable asset

The choice of blockchain matters

Why Bernstein builds on Bitcoin

Evidence that future markets will also need

Sources

From first sketch to final collection: building evidence of your designs

What the timestamp contributed

Show how the design evolved

Three situations where this matters

1. Sharing unreleased collections with third parties

2. Managing fragmented studio workflows

3. Defending against lookalike launches

Build the evidence as you work

Sources

No data, no deals: the evidence gap in IP finance

The vicious circle

What the report proposes

What a lender needs to know about one asset

How Bernstein helps build those answers

A role for IP counsel

Breaking the circle from the inside

Sources

Your certificate is immutable. Your files are not.

1. Reviewing a PDF in macOS Preview

2. Rotating a photo in Windows File Explorer

3. Playing an audio track in iTunes

A certificate cannot reconstruct the original

Preserve the version you certified

Sources

IP-backed finance and the disclosure paradox

Priority 1 runs into a wall

Why it bites hardest on unregistered IP

Separate the proof from the content

How Bernstein does it

Disclose the proof, not the secret