Skip to content
Basis Desk
Tech & Protocols · 2 min read

Bitcoin Researchers Outline Functional Encryption Covenants to Bypass Soft Forks

A cryptographic design by developer Jeremy Rubin enforces spending restrictions inside signing keys, eliminating the need to alter Bitcoin base-layer consensus rules.

Editorial oversight: Julian Mercer, Chief Editor
Neutral
Bitcoin Researchers Outline Functional Encryption Covenants to Bypass Soft Forks

At a glance

What happened
Bitcoin researchers outlined a functional encryption framework based on a May 2024 paper by Jeremy Rubin that enforces covenants via restricted signing keys [1].
Why it matters
The architecture allows Bitcoin users to execute covenant spending logic using standard OP_CHECKSIG verification without coordinating a network soft fork [1].
Who is affected
Bitcoin protocol engineers, application developers, and users seeking programmable spending policies [1].
What's next
No next step announced [1].
Primary source
cointelegraph.com: Bitcoin Covenants Part 6: FE Covenants — Enforcing covenants through cryptographically restricted signing keys

Key points

  • Functional encryption covenants enforce spending conditions inside restricted signing keys rather than requiring changes to Bitcoin Script 1.
  • Standard Bitcoin nodes verify the resulting transactions using existing OP_CHECKSIG operations, eliminating the requirement for a soft fork 1.
  • Deployment currently requires a trusted setup authority to destroy master keys and faces computational overhead constraints 1.

Bitcoin developers are exploring functional encryption as an alternative route to activate covenants without modifying the network's consensus rules 1. The architecture, detailed in an ongoing technical series examining Bitcoin covenants, adapts research published by developer Jeremy Rubin in May 2024 titled FE'd Up Covenants 1. The model moves spending restrictions out of Bitcoin Script and directly into the signing key, allowing standard $BTC verification mechanisms to enforce covenant rules without requiring network-wide soft forks 1.

Under standard public-key cryptography, a holder of a private key can sign any transaction payload 1. In a functional encryption (FE) model, signing keys are mathematically restricted to producing signatures only for predefined transactions that satisfy specific spending policies 1. The construction relies on multi-input functional encryption, taking an encrypted private key alongside an encrypted transaction to produce a standard Bitcoin signature via a designated signing function 1. Bitcoin nodes subsequently validate the spend using the existing OP_CHECKSIG operation, leaving base-layer validation rules unchanged 1. Similar to other non-fork design concepts like shielded Bitcoin transfers, the approach sidesteps the coordination hurdles that historically slow base-layer upgrades 1.

Trusted Setup and Practical Roadblocks

Despite the architectural advantage of bypassing a soft fork, the implementation faces practical constraints 1. Creating an FE covenant system requires a setup authority to generate the initial key material, publish the functional keys, and securely destroy both the master secret and the base private key 1. If the authority fails to destroy these secrets, it retains the ability to produce signatures that violate the covenant's programmatic constraints 1. Additionally, user spending addresses rely on a 2-of-2 script requiring both an FE signature and a standard user key to prevent unauthorized third parties from broadcasting valid transactions 1.

Cryptographic overhead also remains a barrier to production use 1. While functional encryption theory was formalized in 2011 and grounded in standard cryptographic assumptions in 2021, computing arbitrary functions still involves resource overheads exceeding current consumer hardware capacity 1. At the time of writing, Bitcoin traded around $63,953 amid broader market hesitation, as developer discussions continue to weigh the trade-offs between complex off-chain cryptographic primitives and dedicated consensus proposals such as BIP-119 1.

Questions this story raises

What is an FE-based Bitcoin covenant?
An FE-based covenant uses functional encryption to issue signing keys that can only generate valid signatures for transactions that conform to a predefined spending policy, verified onchain with existing OP_CHECKSIG rules.
Why do FE covenants avoid a soft fork?
Because the spending restrictions are enforced mathematically within the functional signing key itself, resulting in a standard transaction signature that existing Bitcoin nodes can validate without consensus modifications.
What are the primary drawbacks of this design?
The scheme requires a trusted setup authority to destroy master cryptographic keys and currently faces heavy computational overhead.

Sources

  1. [1] Bitcoin Covenants Part 6: FE Covenants — Enforcing covenants through cryptographically restricted signing keys — cointelegraph.com, November 18, 2026

Written by Basis Desk's newsroom system from the primary sources above and machine-verified against them before publication. Market figures marked "at the time of writing" come from live exchange data. Report an error: corrections@basisdesk.news · corrections policy.

Community read
How do you read this story for the assets involved? One vote a day, anonymous.
Be the first to vote

The Daily Brief, in your inbox at 07:00 ET

Five stories, the numbers that moved, what to watch. Three minutes. No hype, no advice, unsubscribe in one click.

Not financial advice. Basis Desk publishes information, not recommendations. Crypto assets are volatile and you can lose what you invest.