Progress pill
Fundamentals

Fundamentals of Elements

Liquid Bootcamp Essentials

Fundamentals of Elements

  • Elements: The Foundation of Liquid
  • Privacy via Confidential Transactions
  • Development and RPC Workflow

Elements: The Foundation of Liquid

Elements is an open-source, blockchain platform derived from the Bitcoin Core codebase. It extends Bitcoin’s functionality by enabling sidechains—independent blockchains that can transfer assets to and from Bitcoin. While Bitcoin Core powers the Bitcoin network, Elements is the software engine behind the Liquid Network and other custom sidechains.
The relationship is straightforward: Liquid is a specific "instance" of an Elements sidechain, configured for production use with a federated consensus model. Developers familiar with Bitcoin will find Elements intuitive, as it retains the same RPC (Remote Procedure Call) interface and command-line structure (elements-cli, elements-d, elements-qt). The key difference lies in the configuration: setting chain=liquidv1 connects a node to the main Liquid network, while chain=elementsregtest spins up a local regression testing environment where developers can generate blocks instantly and test without external dependencies.

Asset Issuance

A standout feature of Elements is native asset issuance. Unlike Ethereum, where tokens are complex smart contracts, assets in Elements are first-class citizens created via a simple RPC command (issueasset).
  • Unique Identifiers: Each asset gets a unique 64-character hexadecimal ID.
  • Reissuance Tokens: Issuers can optionally create reissuance tokens, which grant the holder the right to mint more of the asset later (useful for stablecoins or security tokens).
  • Asset Registry: Since hex IDs are not human-readable, the Blockstream Asset Registry maps these IDs to names and tickers (e.g., "USDT"), similar to a DNS for assets.

Privacy via Confidential Transactions

Elements addresses one of the primary limitations of public blockchains: the lack of commercial privacy. On Bitcoin, every transaction amount is visible to the world. Elements introduces Confidential Transactions (CT), which cryptographically blind the amount and asset type while still allowing the network to verify the transaction's validity.
This is achieved using Pedersen Commitments and Range Proofs.
  • Pedersen Commitments replace the visible amount with a cryptographic commitment. Due to homomorphic encryption, validators can check that Input Commitments = Output Commitments + Fees without ever seeing the actual values.
  • Range Proofs prevent a user from creating money out of thin air (e.g., by using negative numbers) by proving mathematically that the hidden value is a positive integer within a valid range.
To an outside observer, a Confidential Transaction shows valid inputs and outputs but obscures what is being sent and how much. Only the sender and receiver (who possess the blinding keys) can view the cleartext data.

Development and RPC Workflow

Interacting with an Elements node is primarily done through its JSON-RPC interface. This allows applications written in Python, JavaScript, or Go to communicate with the blockchain.
  • Setup: A developer typically starts in regtest mode. This allows for the instant generation of blocks (generateblock) to confirm transactions immediately, bypassing the 1-minute block time of the live network.
  • Commands: Standard Bitcoin commands like getblockchaininfo are available, alongside Elements-specific commands like dumpblindingkey (for auditing CTs) or pegin (for moving BTC into the sidechain).
  • Aliases: To manage multiple nodes (e.g., a "sender" and "receiver" for testing), developers often use shell aliases like e1-cli and e2-cli pointing to different data directories, simulating a peer-to-peer network on a single machine.
This architecture empowers developers to build sophisticated financial applications—such as securities platforms or private payment gateways—using the robust and familiar tooling of the Bitcoin ecosystem.
Quiz
Quiz1/5
What prevents users from creating money out of thin air in Elements' Confidential Transactions system?