DVOLD Platform
Define what an asset is. Prove what happens to it.
DVOLD is the shared infrastructure beneath a product, document, vehicle or installation. Digital identity, evidence, roles, validations and lifecycle data come together in one auditable place. Organisations use it through DVOLD interfaces, integration with existing systems or an experience under their own brand.
One shared foundation for registration, collaboration and transfer, with clear provenance and controlled access.
Identity
- Asset ID
- AW-GMT-0841
- Type
- Product
- Issuer
- Alpine Watch Co.
- Current status
- Issued
Roles involved
- Issuing organisationIssuance
- Owner or userOwn record
- Service providerShared action
- Validator or expertAssigned scope
Events
- 12 Jan 2026Digital passport issuedIssuing organisationIssued
- 3 Mar 2026Purchase evidence addedOwner or userAdded
- 18 Apr 2026Service event recordedService providerAdded
- 22 May 2026Condition and authenticity reviewedValidator or expertValidated
Linked documents
- Certificate of issuanceIssued
- Purchase evidenceAdded
- Service reportAdded
- Review reportValidated
DVOLD Integrity Layer
Validation nodes
- Node 01
- Node 02
Always at least two
Possible destinations
- Chain 01
- Chain 02
- Chain 03
Multichain, no fixed chain. Configured per application.
Why a platform is needed
Asset data lives in systems that do not trust each other.
A product, object or document often moves through several organisations and processes. Product data sits in an ERP system. Purchase information sits in a point-of-sale system. Certificates are sent by email. Maintenance is recorded elsewhere. Ownership and transfer disappear into yet another record.
Each party therefore maintains its own version of reality. Data is entered repeatedly, evidence becomes separated from the asset and the history breaks at transfer. When an organisation later needs to prove who issued, reviewed, maintained or transferred something, the process takes time and leaves room for dispute.
DVOLD brings those data points and actions together around one digital asset identity, without giving every participant access to all information. What is a search through emails and separate records today becomes an auditable question with a direct answer: who did what, when and with which status.
Fragmented data
Product data, documents, status and ownership are spread across systems and organisations.
Unclear provenance
It is not always clear who added, issued or validated information.
Broken history
Relevant context is lost during service, sale, transfer or recycling.
Too much access or too little collaboration
Parties need to exchange data, but do not need to see each other's complete records.
Source systems per organisation
Each organisation maintains its own part of reality.
Brand or manufacturer
- ERPProduct data
- CertificatesEvidence
Retail and sales
- Point of salePurchase information
- EmailLoose attachments
Service and ownership
- MaintenanceService history
- Ownership recordTransfer
Relevant events and evidence come together around the same identity.
- Events
- Evidence
- Roles
- Status
DVOLD does not automatically replace the source systems. It adds a shared layer for identity, evidence, roles and status.
The shared foundation
One digital identity. One auditable history. Multiple authorised parties.
DVOLD gives a product, object, document, component or other recordable asset a unique digital identity. Data, evidence, statuses and events are connected to that identity, with visible provenance and a clear roles model.
A brand can issue a passport. A qualified expert can validate specific information. A maintenance provider can add a service event. An insurer can review relevant data with permission. A new owner can receive the asset passport without automatically receiving personal information or separate contracts.
Every contribution receives context: who acted, in which role, at what time and with which status. This creates a useful and auditable record around the asset rather than a loose collection of documents.
Authorised organisations
- Issuing organisationIssuance and product data
- Validator or expertAssigned review
- Service providerShared action
- Owner or userOwn record and transfer
Asset core
Event history
| Source | Actor | Action | Status |
|---|---|---|---|
| Issuance | Issuing organisation | Passport issued | Issued |
| Own contribution | Owner or user | Evidence added | Added |
| Service action | Service provider | Maintenance recorded | Added |
| Review | Validator or expert | Data confirmed | Validated |
Append-only. A correction is added as a new event, never by overwriting.
Connected processes
- Service and maintenanceAdds a service event without opening the complete record.
- Insurance and financeReviews the data that was shared, with permission.
- Inspection and certificationRecords the scope the review applied to.
- Ownership transferTransfers while preserving the relevant asset history.
Access is selective: permissions are connected to the organisation, role, asset, data category and action.
Principles
- One digital identity for each asset or recordable entity.
- Data and evidence remain connected to the correct context.
- Important actions and status changes remain traceable.
- The infrastructure connects to existing processes and interfaces.
- The DVOLD Integrity Layer is multichain and is not tied to one blockchain.
What the platform enables
The building blocks for auditable asset processes.
Digital asset identity
Give every product, object, document, component or other recordable item a unique digital identity with configurable metadata, status and relationships.
Issuance, evidence and validation
Connect information to the party that issued or added it. Show what was validated, by whom and when.
Lifecycle records
Build a chronological history of purchase, use, maintenance, inspection, appraisal, insurance, claims, status changes and transfer.
Composition and relationships
Record how assets, components, materials, documents and other entities relate to each other.
Ownership and transfer
Record current ownership status and support transfer while preserving relevant asset history.
Roles and controlled access
Define per organisation and action who may view, add, issue, validate or manage information.
Audit and status
Keep it traceable which party performed an action. Relevant events are recorded append-only.
Integration and white-label
Use DVOLD through dedicated user interfaces, integrate platform capabilities or provide a selected experience under the organisation's own brand.
Not every organisation needs the same capabilities. Platform functions are configured for the application, role and process.
Trust without false certainty
Not all data carries the same level of assurance. DVOLD shows the difference.
DVOLD makes provenance, role and status visible. This allows an organisation to distinguish between information added by a user, information issued by a known party and data reviewed and validated by an authorised party.
Added
- Actor
- User or organisation
- Source
- Own contribution
- Moment
- Time of the contribution
- Scope
- The added item
What it means
A user or organisation added information, a document or an event. The source is visible, but the content has not automatically been reviewed by an independent party.
Not automatically established
An independent review of the content.
Issued
- Actor
- Known issuing organisation
- Source
- The issuer itself
- Moment
- Time of issuance
- Scope
- The issued information or passport
What it means
A known organisation issued the information or digital passport itself. The relationship with the issuer is auditable, without automatically suggesting that every possible claim was externally validated.
Not automatically established
External validation of every possible claim.
Validated
- Actor
- Authorised party
- Source
- The review performed
- Moment
- Time of the review
- Scope
- The reviewed data
What it means
An authorised party reviewed and confirmed specific data. The record makes clear what was reviewed, who performed the review and when.
Not automatically established
Anything outside the recorded scope.
These three lanes are three kinds of provenance, not a ranking of quality. Which one carries most weight depends on the question being asked.
Trust does not come from one generic label. It comes from transparency about the source, action and review performed.
Collaboration without sharing everything
Each party receives precisely the role the process requires.
An asset record can be used by several organisations without giving each party access to view or manage the entire record. Permissions are connected to the organisation, role, asset, data category and action.
Depending on the configuration, with permission and within an assigned scope. The matrix shows what a role can do, not a fixed authorisation: permissions are configurable per application.
- Possible within this role
- Not part of this role
| Role | View | Add | Issue | Validate | Maintain | Manage |
|---|---|---|---|---|---|---|
| Owner or userScopeOwn assets and environmentManages their own environment, shares relevant information and can transfer ownership where the process allows it. | Possible within this role | Possible within this role | Not part of this role | Not part of this role | Not part of this role | Possible within this role |
| Issuing organisationScopeOwn issued assetsIssues product information, certificates or digital passports from its own role and responsibility. | Possible within this role | Possible within this role | Possible within this role | Not part of this role | Not part of this role | Not part of this role |
| Validator or expertScopeAssigned reviewReviews specific data, documents or the condition of an asset and records the scope of the validation. | Possible within this role | Possible within this role | Not part of this role | Possible within this role | Not part of this role | Not part of this role |
| Service providerScopeShared action or requestReceives only the information shared for a specific service, application or assessment. | Possible within this role | Possible within this role | Not part of this role | Not part of this role | Possible within this role | Not part of this role |
| Partner administratorScopeOwn organisation environmentManages users, roles, products, configurations and integrations within the organisation's own environment. | Possible within this role | Not part of this role | Not part of this role | Not part of this role | Not part of this role | Possible within this role |
| DVOLD administrationScopePlatform-wide governanceManages platform-wide governance, roles, exceptions, monitoring and audit. | Possible within this role | Not part of this role | Not part of this role | Not part of this role | Not part of this role | Possible within this role |
Contribution does not require complete read access. A party can add its own event or evidence without automatically seeing all earlier data.
The data model follows the asset
A timeline for what happens. A structure for what something contains.
Not every asset requires the same type of record. DVOLD supports two fundamental patterns that can be used separately or together.
Layers around one asset
- Asset identityOne identity per assetStays fixed
- Current stateStatus and attributesChanges with version history
- EventsEvery action as a new stepGrows append-only
- Documents and evidenceOff-chain, with permissionChanges with version history
- Roles and accessPer organisation and actionChanges with version history
- ReferencesHash, event ID or registrationGrows append-only
Two patterns on the same layers
Chronological record
Events, evidence and contributions build over time around one asset or record. Examples include issuance, maintenance, inspections, appraisals, claims and ownership transfers. Supports real estate, maintenance, legal records, vehicles, product service and certification.
Core valueThe current status and complete version history remain demonstrable, even when several parties contribute at different moments. Every correction remains a new, traceable step.
Composition and relationships
An asset can consist of components, subcomponents, materials, documents or other related entities. Each layer can have its own identity, status, value, provenance and lifespan. Supports product structures, supply chains, digital product passports, maintenance of complex installations and circularity.
Core valueThe system records not only the finished asset, but also its underlying composition and relationships.
Urban Mining shows how a single asset record can branch into materials, components, locations and subsequent steps while preserving provenance and context at every layer.
The lifecycle
Every event adds context to the same asset identity.
Issue or add
An organisation issues a passport or information, or a user adds an asset and available evidence.
RoleIssuing organisation or owner
Structure
Metadata, categories, documents, relationships and roles are connected to the correct asset identity.
RoleDepends on the configuration
Validate
An authorised party reviews specific data and makes clear what was checked.
RoleValidator or expert
Use and expand
Parties use the record for service, insurance, finance, inspection, reporting or compliance. New events continue to build on the existing history.
RoleService provider
Transfer
Ownership or management can change while relevant asset history is preserved. Personal data and separate contracts do not transfer automatically.
RoleOwner or user
What does not happen
- Earlier events are not overwritten.
- A correction is recorded as a new event.
- Transfer does not remove the earlier history.
Transfer is one moment in the lifecycle, not the purpose. The value comes from keeping the asset record auditable as it continues to grow through use and across owners.
Connect to your organisation
Your processes remain in control. DVOLD adds the auditable foundation.
DVOLD does not need to replace existing systems. It adds a shared layer for identity, evidence, roles, status and events.
DVOLD interfaces
What it involvesUse the consumer app, validator interface, service-provider interface or partner administration environment when an existing DVOLD interface fits the process.
Where users workAn existing DVOLD interface
Best suited toAn application that wants to use existing user journeys and roles.
API integration
What it involvesConnect selected platform capabilities to existing ERP, CRM, POS, PLM, logistics or sector-specific systems. The exact API scope, authentication and data flows are determined for each implementation.
Where users workThe organisation's existing systems
Best suited toOrganisations that want to retain their current systems and user experience.
White-label
What it involvesUse the same platform core with a dedicated brand layer, configuration and defined user journey. Available functions and tenant design are determined for each application.
Where users workA dedicated brand environment on the platform core
Best suited toOrganisations that want to provide DVOLD capabilities under their own name.
The same core. Different processes.
From product issuance to long-running records.
DVOLD supports a wide range of processes around the same auditable core. A few examples:
- Asset identity
- Visible provenance
- Roles and access
- Append-only history
- Brands and retaildigital passports, service and transfer connected to the same item.
- Insurance and financeassessment based on visible provenance and status, with the service provider responsible for acceptance and terms.
- Maintenance and certificationadd inspections, service and certification without opening the complete record.
- Supply chain and logisticsprovenance, status and transfer moments from each participant.
- Real estate and installationsan ongoing record with permits, maintenance, appraisals and ownership moments.
- Public recordsseveral authorised parties issuing, reviewing and updating data within clearly defined roles.
- Circularity and Urban Miningmake relationships between assets, components and materials visible.
Every application uses the same core and is configured for its roles and processes. They are configurations, not separate DVOLD products.
Auditable without making everything public
Transparency around actions. Protection for sensitive information.
DVOLD is not tied to one blockchain. The DVOLD Integrity Layer uses multichain infrastructure and validates relevant events through multiple nodes, always at least two. An existing on-chain registration cannot be changed or deleted. Corrections and the outcomes of off-chain conflict resolution are added as new events and shown as a new status in the wallet.
On-chain
- Append-only events
- Protected by hash, event ID or registration
- Corrections as a new event
- Never personal data
Personal data is never stored on-chain. The exact allocation of other metadata, documents and events between on-chain and off-chain storage is documented separately in the technical design.
Off-chain
- Editable with the required permission
- Every earlier value preserved
- Documents and evidence
- Personal data and tenant context
Off-chain metadata can be updated by parties with the required permission. Every earlier value and every change remains preserved in an append-only log. Each log step is protected through a hash, event ID or on-chain registration, preventing changes from being silently removed or rewritten.
Governance
- Organisations, roles and permissions determine who may perform a correction or status change.
- The source, actor, action, time and status remain traceable.
- An incorrect or potentially fraudulent passport is not deleted, but can receive a visible notice or changed status.
- A service provider receives only the data required for a specific shared action.
- White-label environments share the platform core but require clear tenant and data separation.
- Privacy, retention, revocation, expiry, duplicate handling and data rights are developed legally and technically for each application.
Phased development
One platform direction. Several build phases.
DVOLD is being developed in phases. The existing beta and product visuals show parts of the consumer, validator and service-provider experience. The broader platform architecture also contains functions, portals and integrations that still need to be built or technically confirmed.
Status categories
Available or demonstrated
Included only after the current beta and source code have been checked again.
In development
Functions and environments whose operation has been designed and is actively being built.
To be validated
Capabilities, integrations or applications whose scope, technical execution or legal design still need confirmation.
How something is placed in a categoryThe preview communicates only what is demonstrably available, in development or still to be validated.
FAQ
Questions that come up often.
8 questions about infrastructure, roles, data and what still needs confirmation.
Is DVOLD tied to one blockchain?
No. The DVOLD Integrity Layer is multichain. The underlying chain configuration can differ by application. Sensitive data and complete records do not need to be published on a blockchain.
Does our organisation have to use the DVOLD app?
Not necessarily. Depending on the application, an organisation can use DVOLD interfaces, integrate capabilities through an API or provide a defined white-label experience.
Can several parties contribute to one record without seeing everything?
That is a central principle of the roles and permissions model. Precise permissions are configured for each application.
Is all information in DVOLD automatically validated?
No. DVOLD distinguishes between added, issued and validated information.
Can DVOLD register components and materials?
The platform architecture supports relationships between assets, components, materials, documents and other entities.
Can a registration be changed or deleted?
An existing on-chain registration cannot be changed or deleted. Corrections are added as new events.
Does DVOLD automatically comply with digital product passport regulation?
No automatic compliance claim is made. Legal and technical conformity must be assessed separately for each product group and application.
Is the full platform already available?
DVOLD is being developed in phases. Some user journeys exist in concept or beta form, while other parts still need to be built or confirmed.
Give every asset an auditable digital lifecycle.
From issuance and validation to maintenance, collaboration and transfer. DVOLD connects data and actions around the same asset identity, while roles determine who can view or add what.