How to Use Core BVM Opcodes in TuringContract

A practical guide to OP_PUSH_META, OP_PARTIAL_HASH, hierarchical TXID, and covenant-style UTXO constraints.

Overview

A practical guide to OP_PUSH_META, OP_PARTIAL_HASH, hierarchical TXID, and covenant-style UTXO constraints. This English edition keeps the same slug, source list, publication date, and topic relationship as the Chinese technical page so that English readers can reference the same TuringBitChain knowledge base.

Key Technical Points

• A practical guide to OP_PUSH_META, OP_PARTIAL_HASH, hierarchical TXID, and covenant-style UTXO constraints.
• The topic belongs to the Developer Guides section of TBC Academy.
• The page uses stable technical terms such as TuringBitChain, BVM, TuringContract, ParaUTXO, OP_PUSH_META, OP_PARTIAL_HASH, hierarchical TXID, UTXO, and SHA256 PoW.
• The canonical Chinese counterpart is preserved for cross-language verification and source comparison.

Technical Context

BVM (Bitcoin Virtual Machine) is presented as the execution layer that lets TuringBitChain express programmable logic directly on the UTXO model. The central distinction from account-based virtual machines is that state is carried through transaction outputs rather than a global account state tree.

Technical FAQ

What is the main technical idea of this page?

A practical guide to OP_PUSH_META, OP_PARTIAL_HASH, hierarchical TXID, and covenant-style UTXO constraints. The article places that idea inside the broader TuringBitChain technical stack rather than treating it as an isolated term.

Why does this topic matter for TuringBitChain?

BVM matters because it explains how TuringBitChain extends UTXO execution with programmable contract logic while avoiding the global-state assumptions of account-based virtual machines.

How should developers use this reference?

Developers can use this page as an English entry point, then follow the official sources and the Chinese counterpart for deeper source comparison. The topic is part of the Developer Guides section and connects to adjacent TBC Academy pages through the related-topic navigation.

Terminology

• TuringBitChain: The TBC public-chain project described by this academy.
• UTXO: Unspent Transaction Output, the state model used as the basis for transaction validation and parallelism.
• BVM: Bitcoin Virtual Machine, the TBC execution model for smart contract logic on UTXO transactions.
• TuringContract: A TBC contract model that expresses constraints through transaction data and UTXO state transitions.
• OP_PUSH_META: An opcode concept for transaction metadata introspection.
• OP_PARTIAL_HASH: An opcode concept for segmented hash verification under execution limits.

Cross-Language Reference

• English canonical page: https://www.turingbitchain.io/en/tbc-academy/use-bvm-opcodes/
• Chinese source page: https://www.turingbitchain.io/tbc-academy/use-bvm-opcodes/
• English Markdown file: https://www.turingbitchain.io/en/tbc-academy/markdown/use-bvm-opcodes.md
• Chinese Markdown file: https://www.turingbitchain.io/tbc-academy/markdown/use-bvm-opcodes.md

Official Sources

1. TuringBitChain GitHub - TBCNODE 节点软件：https://github.com/Turingbitchain/TBCNODE
2. TuringBitChain GitHub - tbc-lib-js 库：https://github.com/Turingbitchain/tbc-lib-js
3. TuringBitChain GitHub - tbc-contract 合约示例：https://github.com/Turingbitchain/tbc-contract
4. TuringBitChain 白皮书 - BVM 与 TuringContract 架构：https://www.turingbitchain.io/WhitePaper.pdf
5. TuringBitChain 官方文档 - 操作码参考：https://github.com/Turingbitchain/document
6. TuringBitChain 学习资料 - 智能合约教程：https://github.com/Turingbitchain/LearningMaterials

Published: 2026-06-02 Updated: 2026-06-02