diff options
| author | Jeremy Rubin <j@rubin.io> | 2022-05-23 09:35:04 -0700 |
|---|---|---|
| committer | Jeremy Rubin <j@rubin.io> | 2022-05-23 09:35:04 -0700 |
| commit | c05f4042f47730a2b7f1e6e46f38db08ee774ff9 (patch) | |
| tree | fc9c10d2d179c16307a857da5de1a5df1faa40f3 | |
| parent | b29a3d27bfd51949c6d7a98092b601f6b79abc49 (diff) | |
| download | bips-c05f4042f47730a2b7f1e6e46f38db08ee774ff9.tar.xz | |
[BIP-119] Reword section on fungibility in motivation
| -rw-r--r-- | bip-0119.mediawiki | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/bip-0119.mediawiki b/bip-0119.mediawiki index e043f7d..37cb477 100644 --- a/bip-0119.mediawiki +++ b/bip-0119.mediawiki @@ -43,9 +43,9 @@ Covenants are restrictions on how a coin may be spent beyond key ownership. This is a general definition based on the legal definition which even simple scripts using CSV would satisfy. Covenants in Bitcoin transactions usually refer to restrictions on where coins can be transferred. Covenants can be -useful to construct smart contracts. As covenants are complex to implement and -risk of introducing fungibility discriminants they have not been seriously -considered for inclusion in Bitcoin. +useful to construct smart contracts. Covenants have historically been widely +considered to be unfit for Bitcoin because they are too complex to implement +and risk reducing the fungibility of coins bound by them. This BIP introduces a simple covenant called a *template* which enables a limited set of highly valuable use cases without significant risk. BIP-119 |