Immutable Version Chains

Create immutable Parent-TX version chains, compare revisions, and preserve permanent document history for audit, rollback, and legal review.

Every file mutation creates a new Arweave transaction with a Parent-TX link embedded as a protocol tag. The chain of versions lives on the blockchain — queryable, permanent, tamper-proof.

Turn every revision into a durable record with lineage that outlives your infrastructure.

Versioning is one of the clearest reasons to use permanent storage at all. It transforms changes, amendments, and reissues into a public, reconstructable timeline.

Value

Give legal and compliance teams a stronger audit trail

Each revision is linked, timestamped, and permanently addressable without relying on mutable buckets or database rows.

Support high-trust document workflows

Contracts, reports, certificates, and software artifacts can all keep a verifiable lineage across revisions.

Reduce arguments about which file was final

The latest version, prior chain, and semantically labeled releases are all queryable from the same system.

Use cases

Contract Lifecycle

Track every amendment as an immutable version. Legal counsel can compare any two TX IDs without downloading files — metadata diff only.

Regulatory Filings

SEC, FINRA, and MiFID II require immutable records with provable timestamps. The Parent-TX chain satisfies auditor requirements for version lineage.

Software Artefacts

Tag builds by semver and link them via Parent-TX. Every release is cryptographically timestamped and permanently retrievable by version string.

For operators

  • Create new versions by linking to the previous transaction rather than mutating an existing record.
  • Combine with Search and Version Diff to make old states discoverable instead of merely preserved.
  • Use Traceability when the file revision should also live inside a broader process chain.

For buyers

  • Strong fit for sectors where retained history matters as much as current state.
  • Makes platform demos feel materially different from ordinary file storage with overwrite semantics.
  • Supports commercial messaging around permanence, evidence, and defensible change history.

Can I delete a specific version?

No. Arweave transactions are immutable by protocol. You can deprecate a version by creating a new one without the Parent-TX link, but the old data remains permanently accessible via its original TX ID.

How do I query the full version history?

Use GET /files/versions/:fileId or query the Arweave GraphQL endpoint filtering by App-Name and File-Name tags. The version chain is traversable via Parent-TX links.

Is the version label semantic or arbitrary?

Arbitrary — you pass any string as the version value. We recommend semantic versioning (1.0.0, 1.1.0) for clarity, but the system does not enforce a format.