What the bytes were
A cryptographic fingerprint of the exact uploaded bytes identifies each artifact. Change a single byte and the artifact no longer matches its registered fingerprint.
Nitrotick · IP Evidence & Verification
Prove the history behind your intellectual property.
Register high-value digital assets, govern changes, preserve version lineage and verify the cryptographic evidence behind every committed version — for source code, CAD designs, AI models and technical documentation.
The problem
A file proves little about its history
When designs, algorithms, research records and technical documents change hands, organizations need more than a file date or an audit-log entry. They need verifiable evidence of what was registered, which version was approved and what can be independently checked later.
Imagine an algorithm developed in 2026. In 2031 an investor, acquirer, auditor or legal expert asks about one historical version. The original team may have moved on, the repository may have been migrated and the original infrastructure may no longer run. The evidence has to stand on its own.
Why the usual evidence falls short
- Git history aloneIdentifies content inside Git's own data model. It is not independent attestation of when an artifact existed or who approved it.
- File dates and ZIP archivesEasy to change, and they say nothing about the bytes that came before.
- Audit logsOwned and editable by the same operator whose records are in question.
- A single file hashProves that bytes match — but not how versions relate, who approved them or what state they belong to.
How it works
Register. Govern. Commit. Verify.
Four steps turn a valuable artifact into a verifiable history — built on the same durable execution and proof foundation that runs every Nitrotick workflow.
- 1 · RegisterSubmit an artifact or a reference to client-owned storage. Nitrotick records a cryptographic fingerprint of its exact bytes and the proposed metadata.
- 2 · GovernEnterprise identity, review and approval policies decide which version changes are accepted — with explicit human approval before anything is committed.
- 3 · CommitThe approved state is recorded as a new version linked to its predecessor, and a cryptographically signed Nitrotick Proof is issued.
- 4 · VerifyValidate the proof and its commitments, and reconstruct the committed state of any historical version when the inputs are available.
What was approved, and in which order
Each version commits its approved attributes and related document digests, and links to the version before it. Verification can recompute that commitment from the retained inputs and compare it with the original.
Capabilities
Verifiable provenance for high-value intellectual property
Every capability is labelled with its current status, so you know exactly what is available today and what is on the roadmap.
Cryptographic proofs
Every committed version receives a signed Nitrotick Proof that binds its content digests, approved attributes and state commitment.
Version lineage
Each new version points to exactly one predecessor, forming a linear, gap-free history. A forged parent link fails verification.
Human approval
Nothing becomes evidence until an authorized reviewer approves it. Reviewer, approver and uploader are recorded as distinct roles.
Historical state reconstruction
Recompute the committed state of an earlier version and compare it with the recorded commitment — instead of trusting a database administrator.
Client-controlled storage & retention
Pluggable storage backends and governed retention policies, so artifacts can stay in infrastructure you control under your retention rules.
Portable evidence & independent verifier
A versioned evidence bundle and a separately deployable verifier that checks proofs offline — without access to the original Nitrotick runtime.
Qualified electronic timestamps
Optional eIDAS qualified timestamping (QeTS) of finalized proofs, validated against the EU Trusted Lists and reported separately from the proof itself.
Multi-authority approval
n-of-m approval for designated high-value transitions, enforced by backend policy and recorded in the evidence.
Optional public-chain anchoring
An additional public commitment of batched proofs for organizations that want one. Never a prerequisite for a Nitrotick Proof.
Use cases
Built for the artifacts your business depends on
Every artifact is a byte stream plus approved metadata, so one evidence model covers source code, CAD, AI models and documents alike.
Industrial R&D
Research artifacts, experimental results and technical specifications with a provable record of how each one evolved.
CAD & engineering design
Design baselines, drawings and engineering changes, approved by the right principals at each revision.
Software & algorithms
A structured evidence history of proprietary releases, from source-code archives to protocol specifications.
AI models
Model weights, training configurations and algorithm implementations tied to the version that was actually approved.
Technical documentation
Controlled document versions, invention disclosures and approval histories that stay verifiable after migrations.
Contractual design handover
Hand a design to a customer or partner with evidence of exactly which bytes and which approved version were delivered.
Founder's story
Our first client is Nitrotick itself
Before asking enterprises to trust this model, we are applying it to our own most valuable asset: the Nitrotick source code, its release history and its architectural decisions.
That discipline keeps the product honest. It forces the hard questions: what happens if a historical artifact is missing? Can a verifier detect an inconsistent commitment? Can a previous version be reconstructed without relying on the current application database?
The self-registration of Nitrotick's own releases is our first internal acceptance case. We will publish the full technical case study once the end-to-end procedure, including independent verification, is complete.
Intellectual property deserves more than storage. It deserves evidence that can withstand independent examination. — Aleksandar M. Tasevski, Founder & Principal Architect
Trust statement
Exactly what is proven — and what is not
Nitrotick verifies evidence of registered data and recorded decisions. It does not itself determine legal ownership, authorship, patentability or legal admissibility.
| Evidence | What it establishes | What it does not establish |
|---|---|---|
| Content digest | The supplied bytes match the registered artifact | Who created the artifact |
| Version lineage | Which approved version preceded which | That no other copies exist elsewhere |
| Approval record | Which identity approved the change, under which policy | Legal title or inventorship |
| Nitrotick Proof | The committed state has not been altered since it was proven | An external, qualified time attestation (planned add-on) |
| State reconstruction | The retained evidence is consistent with the original commitment | The original file, if it was lawfully deleted under your retention policy |
Ownership and authorship claims are recorded as claims, together with the claimant and the basis of the claim. Legal ownership depends on contracts, employment arrangements, assignments and applicable IP law.
Enterprise deployment
Your IP stays under your control
IP Evidence & Verification is an enterprise B2B product, licensed annually and deployed where your contract requires.
- Tenant isolationEvery asset, proof and export is scoped to your organization.
- Client-owned storageArtifacts can remain in storage you own and operate; custody is defined in the contract.
- Your identity providerApprovals run through your existing enterprise identity and roles.
- Confidentiality firstProofs can be shared without disclosing the underlying source code or design files.
Deployment options
Private cloudOn-premiseSaaS
Encryption, key custody and storage responsibilities are agreed per deployment before any confidential artifact is accepted.
FAQ
IP Evidence & Verification — frequently asked questions
Is Nitrotick IP Evidence a patent registration service?
No. Nitrotick creates and verifies technical evidence about what was registered, which version was approved and how it evolved. It does not register IP rights, and it does not determine ownership, authorship, patentability or legal admissibility.
Does Nitrotick store my original files?
That depends on the contracted deployment. Client-owned storage is a supported design target: your artifacts can stay in your own storage while Nitrotick records their content digests, approved metadata and proofs. The exact custody model is defined in your contract.
Can the evidence be verified without Nitrotick online?
A portable evidence bundle and a separately deployable, offline-capable verifier are on the product roadmap. Until they pass their acceptance tests, verification and reconstruction run in the Nitrotick platform.
Is blockchain required?
No. Nitrotick Proofs do not depend on a blockchain. Public-chain anchoring is an optional, planned extension for organizations that want an additional public commitment.
Does AI decide what becomes evidence?
No. AI-assisted metadata extraction is optional and never authoritative. Only attributes approved by an authorized person under your enterprise policy are committed to the evidence.
Is a qualified electronic timestamp included?
Qualified electronic timestamping (eIDAS QeTS) is a planned, optional integration. It will be offered only after the provider integration and its validation are complete, and every proof will clearly state whether an external timestamp is present.
Enterprise evaluation
Protect the history of what you create
Start with one asset and three versions. Message the founder on LinkedIn with your industry, asset types and deployment requirements — please do not send confidential IP in the first message.