📖
Mel docs
HomeOld docs
  • A post-blockchain Web3
  • Conceptual wiki
    • Data model
    • Consensus
    • MEL: trustless sound money
    • Governance-free neutrality
    • Covenants
    • Light clients
    • Network architecture
    • Melnet: the P2P layer
    • What belongs on-chain?
  • Developer guides
    • Overview
    • 🛠️Gibbername: your first off-chain composable protocol
      • melprot: a quick intro
      • Design
      • Implement
      • Use
      • Next steps
    • 💰Wallets
      • Setup and installation
      • Sending money
      • Swapping tokens
    • 🪙Getting tokens
      • Melmint overview
      • Using melminter
      • Melmint arbitrage
    • 🤖Run a full node
      • Melnode quick start
      • Basic replica node
      • Setting up a local simnet
  • 🌉Szaldi guide
    • Bridge your coins
    • Architectural overview
  • Resources
    • Yellow Paper
    • Frequently asked questions
    • MelVM spec
Powered by GitBook
On this page
Edit on GitHub
  1. Conceptual wiki

Covenants

PreviousGovernance-free neutralityNextLight clients

Last updated 2 years ago

In Mel's , every coin/UTXO is locked by a covenant, or a program that constrains what sort of transaction can spend it. Common covenants include:

  • Checking that a transaction is signed by a particular public key

  • Checking that a transaction is signed by some subset of keys (a multisig covenant)

  • Encoding arbitrary stateful logic using self-propagating covenants

On the blockchain level, covenants are written in the low-level language, but in practice covenants are programmed using the high-level language. More info on specific programming patterns can be found in the .

data model
MelVM
Melodeon
Melodeon guide