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. Use Cases

Lucky Number Tickets

PreviousUse CasesNextInternet of Things (IoT) Data

Last updated 5 months ago

A lucky number ticket operator wants to publish the randomly generated winning tickets for transparency and to avoid possible disputes.

  1. The operator draws a lucky number winning ticket (picks a random number).

  2. They write the ticket to the blockchain using nChain Event as unencoded records , obtaining the record location which they publish.

  3. Anyone with the location can read the winning ticket number and see when the draw was taken.

  4. Any holder of a ticket can verify whether theirs is the winning ticket.

Benefits

  • The returned result is proof of what data an organisation submitted to the blockchain and when.

  • Verifiable: The original data and time can be verified.

  • Transparent: The Records are publicly accessible, and the result is readable from the blockchain.

  • Irrefutable: A record of the data exists on the blockchain (tamperproof & cannot be repudiated).

  • Trust and Fairness are established by using the blockchain, a decentralised independent arbiter.

Extended Lucky Number Scenario

The lucky number creator can create tickets by writing records to the blockchain, and using the resultant record location as the ticket number (since it is effectively a large random number).

Anyone can view their ticket on the blockchain and the set of potential winners can be fully transparent up to the time of the draw.

To make the draw, a ticket can be picked at random by using the low-order bits of the location of a written transaction as the random ticket selector.

The tickets, the winning ticket selection, the picker’s identifier and the winning ticket number can be written to the blockchain using nChain Event.

A Lucky Number demo application for nChain Event is available from the Product Suite Platform. See .

See about persistent GUIDs and for more details of this extended screnario.

🔏
here
here
here
Internet of Things (IoT) Data
‡
†