nChain Event
Back to All
V.1.3.1
V.1.3.1
  • nChain Event User Guide
  • Overview
    • Introduction
      • Target Audience
    • Features and Benefits
      • Independent Operations
      • Web3 Development
    • Core Concepts
    • Encoded and Unencoded Records
  • Using nChain Event
    • Initial Set-Up
  • Independent Records
    • Introduction
    • Functional Description
      • Write Record
      • Read Record
      • Verify Record
    • Use Cases
      • Lucky Number Tickets
      • Internet of Things (IoT) Data
      • Intellectual Property Rights (IPR) Evidence
      • Car Dealership
    • Tutorials
      • Data Integrity
    • API Workflow
      • Write Record
      • Get Location Status
      • Read Record
      • Verify Record
  • Linked Records
    • Introduction
      • Concept - Link Locations
    • Functional Description
      • Create Link Record
      • Read Link Record
      • Update Link Record
      • Delete Link Record
      • Verify Link Record
    • Use Cases
      • Luxury Handbag Provenance
    • Tutorials
      • Collection Integrity
      • Provenance Integrity
    • API Workflow
      • Create Link Record
      • Get Link Location Status
      • Read Link Record
      • Update Link Record
      • Delete Link Record
      • Verify Link Record
  • API Documentation
    • nChain Event API
  • Bitcoin SV Blockchain
    • Features and Benefits
    • Writing to Blockchain
    • Reading from Blockchain
    • Transaction Format
    • Troubleshooting
    • Glossary
Powered by GitBook
On this page
  • Next Event Registration
  • Nth Event Verification
  • Benefits
  1. Linked Records
  2. Tutorials

Provenance Integrity

PreviousCollection IntegrityNextAPI Workflow

A business wants to be assured about the data integrity (accuracy and authenticity) of the provenance (or history of events) of their publicly linked company documents. To achieve that, the business wants to easily verify the provenance of a company document.

This use case is an extension of the Data Integrity use case (described ) and is similar to the Collection Integrity use case (described in the previous section). The solution includes these steps for each company document event:

  • Next event registration – the company document is kept hidden but registered and linked on the blockchain

  • Nth event verification – the company document and links are compared with the blockchain to determine validity

Please be aware that verification always requires the original company document.

We will use the Linked Record REST API class wrapper as described in the previous section.

Next Event Registration

Whenever the company document is updated in the application database, this procedure is performed to register a fingerprint of the new company document on the blockchain, and record all provenance:

  aRecord = "get the latest company document for the documentId"

  aSalt = time.now()

  oldLocation = either 0 or provenance[count-1].location for the documentId

  newLocation = event.upsert(aRecord, aSalt, oldLocation) // Register a fingerprint

  // persist aRecord, aSalt, newLocation in provenance[count] for the documentId

  // increment and persist count for the documentId

Nth Event Verification

At any arbitrary time later, the business can verify the Nth previous version (0 for the latest) of the company document with this procedure:

  nthRecord = provenance[count-1-Nth].record for the documentId

  nthSalt = provenance[count-1-Nth].salt for the documentId

  previousLoc = either 0 or collection[count-1-Nth - 1].location for the documentId

  nthLocation = provenance[count-1-Nth].location for the documentId

  nextLoc = either 0 or collection[count-1-Nth] + 1].location for the documentId

  result = event.verify(nthRecord, nthSalt, previousLoc, nthLocation, nextLoc)

  if result = match // nthRecord and links are verified as valid
  if result = mismatch // nthRecord or links are verified as invalid
  if result = error // try again later

The business can employ iteration to verify a range of versions of the company document.

This example ignores issues like the data retention policy of the business.

Benefits

  • Provides high confidence of the validity of verified company documents for the business

  • Provides high confidence to auditors/users who verify the original company document of its validity.

here