nChain Event
Back to All
V.1.4.3
V.1.4.3
  • nChain Event User Guide
  • 📔Overview
    • Introduction
    • Configuration Symbols
    • Features and Benefits
    • Core Concepts
    • Encoded and Unencoded ‡ Records
  • 🤔Using nChain Event
    • How to Use 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
      • Blockchain Unique Identifiers
    • API Workflow
      • Configure API
      • Write Record
      • Get Location Status
      • Read Record
      • Verify Record †
  • 🔗Linked Records §
    • Introduction
    • Functional Description
      • Create Link Record §
      • Read Link Record §
      • Update Link Record §
      • Delete Link Record §
      • Verify Link Record § †
      • Navigate Linked Record § ¶
    • Use Cases
      • Luxury Handbag Provenance
      • Random Prize Draw
    • Tutorials
      • Collection Integrity
      • Provenance Integrity
    • API Workflow
      • Configure API
      • Create Link Record §
      • Get Link Location Status §
      • Read Link Record §
      • Update Link Record §
      • Delete Link Record §
      • Verify Link Record § †
      • Navigate Link Record § ¶
  • ⚙️API Documentation
    • nChain Event API
  • ⛓️Bitcoin SV Blockchain
    • Features and Benefits
    • Writing to Blockchain
    • Reading from Blockchain
    • Transaction Format
  • ⁉️Troubleshooting
    • Troubleshooting
    • Error Codes
    • Glossary
    • Contact Us
Powered by GitBook
On this page
  1. 🔏Independent Records
  2. Functional Description

Verify Record †

PreviousRead RecordNextUse Cases

The Verify Record † operation enables you to get nChain Event to verify whether the local copy of your record matches the one on the blockchain. It provides proof of what was written to the blockchain and when it was published (using the timestamp of the block containing the transaction).

Anyone who has the original record and its location on the blockchain can find out whether there is any discrepancy. This may be just be the record creator or any third-party, depending on the use case.

If there is a discrepancy, this is a good indication that the local record has become altered or corrupted and must be recovered from its backup.