Summary Table
Use Cases
| use case | apo | ctv | txhash | tluv | intro | vault | matt |
|---|---|---|---|---|---|---|---|
| Lightning Symmetry | yes | csfs* | csfs* | ? | yes | no | yes |
| Vaults | no | yes | tap* | yes | tap* | yes | yes |
| Payment Pools | no | no | tap* | yes | tap* | no | yes |
| Ark | half | half | yes | no | yes | ~ctv | yes |
| Fraud Proofs | no | no | no | no | no | no | yes |
| Statechains | yes | csfs* | csfs* | ? | yes | no | yes |
| Spacechains | yes | yes | yes | ? | ? | ~ctv | ? |
| Congestion Control | no | yes | yes | no | yes | ~ctv | yes |
Glossary:
- tap*: yes if combined with something that allows turning a script into a Taproot, plus often
also
OP_CAT - csfs*: yes if combined with
OP_CHECKSIGFROMSTACK - ~ctv: yes but only because the
OP_VAULTproposal also includesOP_CTV
Development Status
| proposal | status |
|---|---|
| ANYPREVOUT | BIP and active on Inquisition |
| CTV | BIP and active on Inquisition |
| OP_VAULT | draft BIP and Inquisition patch |
| TLUV | idea |
| TXHASH | draft BIP and Bitcoin Core Implementation |
| Direct Introspection | ideas (but active on Liquid) |
| MATT | very detailed ideas |
| Template Key | early draft BIP |
Developer Support
The bitcoin wiki has a page where certain prominent bitcoin developers have indicated their support for various proposals, some of them adding a rationale behind their support: