Skip to content
Market MoodExtreme Fear11
Market Cap: $2.18T −4.28%24h Vol: $71.41BBTC: $63,581 −1.63%
NewsMarketsBitcoinEthereumAltcoinsAsiaWeb3EventsAbout Us
LanguageENRU
Subscribe Pro
Bitcoin

Functional encryption could enable Bitcoin covenants without a soft fork

Researchers propose using functional encryption to enforce Bitcoin covenants via signing keys, avoiding consensus changes.

· 2 min read
three round gold-colored Bitcoin tokens
Photo by Dmytro Demidko on Unsplash

Key takeaways

  • Jeremy Rubin’s FE‑based design moves covenant enforcement from script to the signing key.
  • The scheme relies on a trusted setup authority that generates and then destroys the master private key.
  • If practical, FE covenants could be verified by OP_CHECKSIG without requiring a soft‑fork.

A new academic proposal suggests that Bitcoin could enforce transaction covenants without altering its consensus rules. The design, outlined by Jeremy Rubin – the original author of the OP_CTV proposal (BIP‑119) – leverages functional encryption (FE) to restrict signing keys to a predefined set of valid transactions, allowing nodes to verify covenant compliance using the existing OP_CHECKSIG opcode.

BitcoinBTC · 24h
$63,581−1.63%

How functional encryption changes covenant enforcement

Functional encryption extends traditional public‑key encryption by issuing subordinate keys that reveal only a specific function of the encrypted data. Rubin’s paper, titled “FE’d Up Covenants,” adapts this concept so that the function f computes a Bitcoin signature that is valid only for transactions meeting a particular spending policy. Unlike ordinary private keys, which can sign any message, the FE‑derived key can sign only those transactions that satisfy the covenant’s rules.

Trusted setup and key management

The scheme requires a one‑time trusted setup authority. This entity creates a Bitcoin key pair (k, P) and an FE key pair (master secret msk, public mpk). It publishes the public Bitcoin key P, the FE public key mpk, an encryption of k under mpk, and the functional key for f derived from msk. After publishing, the authority must destroy both k and msk; otherwise it could forge signatures that break the covenant. Once the setup is complete, each covenant receives its own tweaked key pair derived from the original key and the hash of the covenant’s policy.

Practical workflow for covenant spends

To spend funds locked by an FE‑based covenant, a user encrypts the intended transaction to mpk, then evaluates f using the encrypted transaction, the encrypted base key, and the functional key. The function internally tweaks the base private key with the policy hash and produces a signature that verifies against the tweaked public key. Because the signature is only valid for the specific policy‑derived key, any transaction that deviates from the covenant cannot be signed, or the function can outright reject it. In practice, the receiving address would embed a 2‑of‑2 script requiring both the user’s regular signature and the FE‑generated signature, adding an extra layer of protection.

What to watch next

The proposal remains theoretical; functional encryption constructions are still computationally intensive and rely on multilinear maps that have only recently become practical. Future research will need to demonstrate that the overhead is manageable for Bitcoin nodes and that the trusted‑setup model can be decentralized or mitigated. If successful, FE‑based covenants could expand Bitcoin’s scripting capabilities without triggering a soft fork, a development that would be closely monitored by developers, miners, and institutional users across Asia and beyond.

Sources

  • Cointelegraph: Bitcoin Covenants Part 6: FE Covenants — Enforcing covenants through cryptographically restricted signing keys

Not financial advice. Crypto assets are volatile and you can lose money. Read our Financial Risk Disclosure.

functional encryptionBitcoin covenantsJeremy RubinOP_CTVcryptographyAsia
Newsletter

Get the BitcoinEast Daily

Top crypto news, analysis, and market insights, delivered every day.