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
  1. Bitcoin SV Blockchain

Writing to Blockchain

PreviousFeatures and BenefitsNextReading from Blockchain
  • Records submitted to the blockchain are not added to the blockchain immediately. Records are contained within transactions which are collected into blocks. These need to be agreed between several blockchain operators ("miners") before the blocks are added to the blockchain.

  • GET location status provides the latest confirmation status of a record being submitted to the blockchain. Depending on the use case, it is good practice to check the location status for the submit operations (Write, Create, Update and Delete) once every 10 minutes (at the most frequent) until the confirmation status is satisfactory.

  • If GET location status reports that the operation has failed, retry the operation.

  • There is no guarantee that a record will be mined and confirmed within any number of blocks.

  • There is also a minute possibility that a record will not be mined at all. If it is not mined within a reasonable time frame, for example 1 hour, retry the submit operation.

  • The update and delete requests are valid only after the preceding record has been mined, otherwise resulting in undefined behaviour.