Builder's Guide
  • Welcome to the Builder's Guide to the LND Galaxy!
  • The Lightning Network
    • Overview
    • Payment Channels
      • Lifecycle of a Payment Channel
      • Watchtowers
      • Understanding Sweeping
      • Etymology
    • The Gossip Network
      • Identifying Good Peers on the Lightning Network
    • Pathfinding
      • Finding routes in the Lightning Network
      • Channel Fees
      • Multipath Payments (MPP)
    • Lightning Network Invoices
      • Understanding Lightning Invoices
    • Making Payments
      • The Payment Cycle
      • Timelocks
      • ⭐Hashed Timelock Contract (HTLC)
      • Payment Etymology
      • ⭐What Makes a Good Routing Node
      • Understanding Submarine Swaps
      • Instant Submarine Swaps
    • Liquidity
      • ⭐Understanding Liquidity
      • Managing Liquidity on the Lightning Network
      • Liquidity Management for Lightning Merchants
      • How to Get Inbound Capacity on the Lightning Network
      • Lightning Service Provider
    • L402: Lightning HTTP 402 Protocol
      • Macaroons
      • L402
      • 📋Protocol Specification
      • Implementations and Links
    • Taproot Assets
      • Taproot Assets Protocol
      • Taproot Assets on Lightning
      • Edge Nodes
      • Taproot Assets Trustless Swap
      • FAQ
      • Glossary
  • Lightning Network Tools
    • LND
      • 🛠️Get Started
      • lnd.conf
      • First Steps With LND
      • Wallet Management
      • Sending Payments
      • Atomic Multi-path Payments (AMP)
      • Receiving Payments
      • Unconfirmed Bitcoin Transactions
      • Channel Fees
      • Inbound Channel Fees
      • Macaroons
      • Configuring Watchtowers
      • Pathfinding
      • Blinded Paths
      • Key Import
      • Secure Your Lightning Network Node
      • Configuration of a Routing Node
      • Quick Tor Setup
      • Configuring Tor
      • Enable ‘Neutrino mode’ in Bitcoin Core
      • Send Messages With Keysend
      • Partially Signed Bitcoin Transactions
      • Bulk onchain actions with PSBTs
      • Sweeper
      • Debugging LND
      • Fuzzing LND
      • LND API documentation
      • Channel Acceptor
      • RPC Middleware Interceptor
      • HTLC Interceptor
      • NAT Traversal
      • Recovery: Planning for Failure
      • Migrating LND
      • Disaster recovery
      • Contribute to LND
    • Lightning Terminal
      • What is Lightning Terminal?
      • 🛠️Get litd
      • Run litd
      • Integrating litd
      • Demo: Litd Speed Run
      • Connect to Terminal
      • Recommended Channels
      • Rankings
      • Health Checks
      • Liquidity Report
      • Opening Lightning Network Channels
      • Managing Channel Liquidity
      • Autofees
      • AutoOpen
      • LND Accounts
      • Loop and Lightning Terminal
      • Loop Fees
      • Pool and Lightning Terminal
      • Command Line Interface
      • Troubleshooting
      • Lightning Node Connect: Under the hood
      • LNC Node Package
      • LITD API Documentation
      • Privacy and Security
      • Privacy Policy
      • Terms of Use
    • Loop
      • 🛠️Get Started
      • The Loop CLI
      • Autoloop
      • Static Loop In Addresses
      • Instant Loop Outs
      • Peer with Loop
      • Loop API Documentation
    • Pool
      • Overview
      • Quickstart
      • 🛠️Installation
      • First Steps
      • Accounts
      • Orders and Asks
      • Sidecar Channels
      • Zero-confirmation Channels
      • Channel Leases
      • Batch Execution
      • Account Recovery
      • Pool API Documentation
      • FAQs
    • Taproot Assets
      • Get Started
      • First Steps
      • Taproot Assets Channels
      • Asset Decimal Display
      • Become an Edge Node
      • RFQ
      • Collectibles
      • Universes
      • Asset Loop
      • Debugging Tapd
      • Multisignature
      • Minting Assets With an External Signer
      • Lightning Polar
      • Operational Safety Guidelines
      • Taproot Assets API Documentation
    • Aperture
      • ⚒️Get Aperture
      • LNC Backend
      • LNC Mailbox
      • Pricing
    • Faraday
      • 🛠️Get Started
      • The Faraday CLI
      • Faraday API Documentation
  • LAPPs
    • Guides
      • Use Polar to Build Your First LAPP
        • Setup: Local Cluster with Polar
        • Setup: Run the Completed App
        • Setup: Run the App Without LND
      • Add Features
        • Feature 1: Connect to LND
        • Feature 2: Display Node Alias and Balance
        • Feature 3: Sign and Verify Posts
        • Feature 4: Modify Upvote Action
      • Make Your own LNC-powered Application
    • Next Steps
  • Community Resources
    • Resource List
    • Lightning Bulb 💡
    • Glossary
    • FAQ
Powered by GitBook
On this page
  • Anchor
  • Asset group
  • Asset ID
  • Asset tag
  • Batch
  • Burn
  • Collectibles
  • Collections
  • Commitment
  • Fungible tokens
  • Genesis point
  • Group key
  • Internal key
  • Issuer
  • Leaf
  • Lightning Polar
  • Merkle root
  • Merkle sum tree
  • Merkle tree
  • Meta data
  • Mint
  • Non-fungible token
  • Normal asset
  • Proof file
  • PSBT
  • Sparse merkle tree
  • Supply
  • Tapd
  • Taproot
  • Taproot Asset address
  • Taproot Assets
  • Taproot Assets Channel
  • Tapscript
  • Tapscript sibling
  • Unique asset
  • Universe
  • vPSBT
  • vUTXO

Was this helpful?

  1. The Lightning Network
  2. Taproot Assets

Glossary

Taproot Assets make use of several novel concepts, all of which we attempt to briefly define here.

PreviousFAQNextLND

Last updated 1 year ago

Was this helpful?

Anchor

The anchor transaction is the Bitcoin transaction that mints or transfers a Taproot Asset.

Asset group

An asset group describes a series of assets, as identified by their asset ID, for which new assets can be added by the issuer.

Asset ID

The asset ID is used to identify an asset. It is the hash of the , the and the data. It is a globally unique identifier. If an asset is , each minted series contains its own asset ID.

Asset tag

The asset tag is equivalent to the name of an asset. Other information is collected as part of the .

Batch

A batch is a set of Taproot Asset mints or transfers that are contained in a single Bitcoin-level UTXO.

Burn

Burning an asset means irrevocably removing it from the circulating supply.

Collectibles

A collectible, unique or non-fungible asset, unlike a normal asset, cannot be divided or aggregated, as there are no other units of its kind. It can however be put into a collection with other similar collectibles.

Collections

Commitment

A commitment is typically the hash of data that is to be permanently recorded to have existed at a certain point in time, and in a certain utxo.

Fungible tokens

Genesis point

The genesis point is the first input of the transaction that mints a Taproot Asset.

Group key

The group key identifies normal and collectible assets that do not have a fixed supply. When new assets of this group are minted, a signature using this key must be present.

Internal key

The internal key is the key that is able to spend the Taproot Bitcoin UTXO.

Issuer

The issuer of an asset is whoever creates and publishes the mint transaction. The issuer of a grouped asset is identified using the group key.

Leaf

Lightning Polar

Lightning Polar is software that helps you simulate a regtest Lightning environment in which you can easily add multiple nodes. It can also be used to test Taproot Assets mints and transactions.

Merkle root

The Merkle root is the hash at the very top of the Merkle tree. If a single value in the Merkle tree changes, the root also changes.

Merkle sum tree

Merkle tree

Meta data

The asset meta data can be used to commit to any arbitrary data. Most commonly it describes the asset and its terms or represents the asset itself.

Mint

The action of issuing an asset. Also see -> issuer.

Non-fungible token

Also see -> .

Normal asset

A normal or fungible asset is one that is divisible into a predefined set of units. Each unit is expected to be valued the same as any other unit of the same asset. Normal assets can be fixed in total supply, or be part of an -> asset group.

Proof file

The proof file contains information about the asset, when and how it was minted as well as previous transfers. it is needed to verify ownership over an asset.

PSBT

A partially signed Bitcoin transaction is a file format that lets two wallets communicate only specific details about a new transaction, for example only its inputs, or only its outputs. These PSBTs can be used to sign transactions with external signing devices, or allow multiple parties to contribute inputs to one transaction.

Sparse merkle tree

A sparse merkle tree is a merkle tree over all numbers of a given space. A sparse merkle tree over 2^256 for example theoretically contains 2^256 leafs. It can be computed because by default all leafs are empty. Sparse merkle trees help with exclusion proofs, e.g. proving something is not present in a merkle tree.

Supply

The supply of an asset is the total amount of units of that asset in circulation. For -> grouped assets, this supply can be increased later. For all assets, it can be reduced by -> burning a portion of the supply.

Tapd

Taproot Assets Protocol Daemon is the reference implementation for Taproot Assets.

Taproot

Taproot is a Bitcoin transaction type. Bitcoin sent to taproot scripts can be unlocked either using the -> internal key or a predefined set of conditions, the -> tapscript.

Taproot Asset address

A Taproot Assets address is created by the recipient of an asset to be able to receive an asset. Such addresses are specific to an asset and an amount and should not be reused.

Taproot Assets

Taproot Assets leverages Taproot transactions to commit to newly created assets and their transfers in an efficient and scalable manner.

Taproot Assets Channel

Taproot Assets can be deposited into Lightning channels. These channels are referred to as Taproot Asset Channels.

Tapscript

Tapscript is a feature of -> Taproot transactions that allows to create various conditional spending conditions. Taproot Assets and their merkle trees are stored in the Tapscript.

Tapscript sibling

The Tapscript sibling is the hash in the leaf next to the data in question. The sibling is needed to compute the -> Merkle root.

Unique asset

See also -> Collectibles.

Universe

A universe is a server that serves information about assets and their transfers. Universes can also be used to transfer proof files between users.

vPSBT

Virtual partially signed Bitcoin transactions achieve what -> PSBTs achieve, but on the Taproot Assets layer. Using vPSBTs, it becomes easier to batch Taproot Asset transactions, use external signing devices or assemble transactions between the Taproot asset and Bitcoin layer.

vUTXO

A vUTXO is a Taproot Assets utxo. As the Taproot Assets themselves are not perfectly synonymous with the Bitcoin UTXO that they are anchored in, vUTXOs are used to reference them.

A collection is a of collectibles. While every item in the collection is unique, they can still be identified as part of the same collection using the group key.

See also .

A leaf is the lowest level in a . They typically contain the data that the Merkle tree commits to.

A merkle sum tree is a Merkle tree that for each leaf contains a numerical value, which is sumed up in each node. The sum at the is equal to the sum of values at the leafs.

In a merkle tree a pair of items is hashed, the pair then hashed with other pairs until only a single hash is left, the . This helps to cheaply commit to large amounts of arbitrary data and check whether anything has changed.

Read more: Collectibles
Read more: Lightning Polar and Taproot Assets
Read more: Install tapd
Read more: Taproot Assets protocol
Read more: Taproot Assets on Lightning
group
normal assets
Merkle tree
Merkle root
Merkle root
genesis outpoint
asset tag
asset meta
grouped
meta data
Read more: Sparse merkle trees in Taproot Assets
Read more: Minting asset groups
Read more: Burn assets
Read more: Generate Taproot Asset addresses