Audit Trails v0.1.0
What's Changed
This release introduces Audit Trails, the second component of the IOTA Notarization Toolkit, alongside the already known Single Notarization.
Audit Trails provides governed, append-only record histories as shared on-chain objects. Use it when you need structured, sequential entries with role-based access control — for example compliance logs, supply-chain histories, or multi-party process records.
Highlights
AuditTrailon-chain object — sequential record storage with immutable and updatable trail metadata- Role-based access control — define roles with fine-grained permission sets and issue capability objects, optionally bound to an address or a validity window
- Locking — trail-wide locking configuration restricting writes and deletions to records and the whole trail
- Record tags — tag registry with per-role tag restrictions that can additionally be used to manage record access
- Lifecycle events — events emitted for trail and record lifecycle changes across all layers
Packages
| Layer | Package |
|---|---|
| Move | IotaAuditTrails (audit-trail-move) — deployed on mainnet, testnet, and devnet |
| Rust | audit-trail-rs — AuditTrailClient / AuditTrailClientReadOnly with builder-based transaction APIs |
| WASM/TypeScript | @iota/audit-trails — JS/TS bindings for Node.js and browsers |
Getting Started
Runnable examples covering trail creation, records, metadata, locking, access management, and deletion are available under examples/audit-trail, including real-world scenarios.
Full documentation will soon be available here: IOTA Notarization Toolkit docs.
Full Changelog: v0.1.21...trails-v0.1.0