Qtum Documentation
  • Qtum Features and Advances
    • Qtum Ordinals
      • Chapter 1: Introduction to ordinals
      • Chapter 2: Understanding Inscriptions in Depth
      • Chapter 3: The Intricacies of Ordinals on the Blockchain
      • Chapter 4: Engineering Ordinals within Qtum's Architecture
      • Chapter 5: Prerequisites for Engaging with Ordinals on Qtum
      • Chapter 6: The Procedure for Inscribing a Satoshi with Ordinals
      • Inscribing Messages on Qtum Testnet
    • Qtum-BIP38
  • Qtum Wallet
    • Qtum-Core Wallet Documentation
      • Qtum Documentation
      • Using Qtum Wallet
      • Linux Repositories
      • Qtum on Raspberry Pi
      • How to Update Qtum
      • Qtum Wallet Best Practices
      • Qtum Wallet Commands
      • Adding Nodes To Qtum Wallet
      • Encrypt & Unlock Qtum Wallet
      • Recovery wallet data with salvagewallet
      • Testnet User Guide
      • Bech32 Addresses support
      • How to Add Options (Config)
      • How to use Bootstrap
  • Staking and Nodes
    • Secure Staking With Qtum Star Network
    • Staking Documentation
      • Qtum Staking
      • Offline Staking
      • Offline Staking Address Delegation - Undelegation Transaction Details
      • Qtum on AWS ec2
      • Staking with a VPS
      • Staking with a Raspberry Pi
  • Other Wallets
    • Wallets Supporting Qtum
      • Electrum
      • Qtum Web Wallet
      • Qtum Lightning Network
  • RPC CALLS AND API
    • QTUM RPC CALLS
    • QTUM RPC API
  • Qtum Deployment
    • Guidance on Qtum Deployment
    • Building Qtum on Linux
    • Guidance for Exchange Deployment
  • Smart Contracts and QRC20 Tokens
    • QRC20 Token integration
    • QRC20 Integration Technical Guide
    • Raw QRC20 Transaction implementation guide
  • WEB3
    • Web3 Compatibility Layer
    • Janus Docker Container
    • Truffle
    • Differences between EVM chains
  • QNEKT
    • QNEKT
    • Why Fork Metamask ?
    • Sideloading Qnekt
    • Setting up QNEKT
    • Working with Testnet Coins on QNEKT
    • Connecting QNEKT to regtest
    • QNEKT Regtest with react-box
  • Research
    • Confidential Assets
    • Data Analytics
Powered by GitBook
On this page
  1. Qtum Features and Advances
  2. Qtum Ordinals

Chapter 4: Engineering Ordinals within Qtum's Architecture

Leveraging Bitcoin's Scripting Capabilities

Bitcoin's scripting language, a stack-based execution system, has evolved over time, gaining features that increase its flexibility without compromising security. Segregated Witness (SegWit) and Taproot are significant advancements that have expanded Bitcoin's capabilities. SegWit, by separating the signature information (witness) from the transaction data, has not only improved scalability but also paved the way for more complex transaction types without altering the underlying blockchain structure. Taproot further enhances this by enabling more privacy and efficiency in smart contracts.

The Taproot Advantage

Taproot plays a crucial role in the implementation of ordinals. It allows for the creation of transactions where the complexity of the spending conditions can remain hidden unless they are required for the transaction. This means that inscriptions can be embedded in transactions without revealing the complexity unless it's explicitly needed for the execution of the contract. The use of Merkleized Abstract Syntax Trees (MAST) within Taproot means that only the relevant parts of the script are revealed when a transaction is spent, maintaining privacy and efficiency.

The Two-Transaction Mechanism

Ordinals operate through a commit-and-reveal process using two separate transactions. The first transaction, the "commit," involves creating a Taproot output that commits to a script containing the inscription content. This content remains hidden within the Taproot structure and is not revealed until the second transaction, the "reveal," occurs. The reveal transaction spends the output created by the commit transaction and discloses the inscription content on the blockchain.

Security and Permanence

This two-phase process not only allows for the secure and immutable storage of inscriptions but also aligns with Bitcoin's security model. Inscriptions are protected by the same rigorous consensus rules and cryptographic verifications that secure all Bitcoin transactions. The permanence of inscriptions is guaranteed by the blockchain, ensuring that once data is embedded, it remains unaltered and retrievable for as long as the network exists.

Technical Implications

The implementation of ordinals on Qtum is a testament to the blockchain's adaptability and the possibilities that emerge from its scripting system. For developers and technical users, understanding the interplay between Bitcoin's scripting, SegWit, Taproot, and the commit-and-reveal process is crucial for leveraging the full potential of ordinals.

PreviousChapter 3: The Intricacies of Ordinals on the BlockchainNextChapter 5: Prerequisites for Engaging with Ordinals on Qtum

Last updated 1 year ago