[bitcoin-dev] `OP_EVICT`: An Alternative to `OP_TAPLEAFUPDATEVERIFY`
2022-02-19 1:17 UTC (10+ messages)
[bitcoin-dev] [Pre-BIP] Fee Accounts
2022-02-19 0:38 UTC (14+ messages)
[bitcoin-dev] Stumbling into a contentious soft fork activation attempt
2022-02-18 23:41 UTC (2+ messages)
[bitcoin-dev] Thoughts on fee bumping
2022-02-18 21:09 UTC (24+ messages)
` [bitcoin-dev] Sponsor transaction engineering, was "
[bitcoin-dev] CTV Signet Parameters
2022-02-18 11:13 UTC (2+ messages)
[bitcoin-dev] TXHASH + CHECKSIGFROMSTACKVERIFY in lieu of CTV and ANYPREVOUT
2022-02-18 7:34 UTC (35+ messages)
` [bitcoin-dev] Recursive covenant opposition, or the absence thereof, was "
[bitcoin-dev] A suggestion to periodically destroy (or remove to secondary storage for Archiving reasons) dust, Non-standard UTXOs, and also detected burn
2022-02-18 3:36 UTC (9+ messages)
[bitcoin-dev] Thoughts on fee bumping
2022-02-18 2:08 UTC
[bitcoin-dev] Thoughts on fee bumping
2022-02-18 0:54 UTC
[bitcoin-dev] Lightning and other layer 2 projects with multiple RBF policies
2022-02-14 17:59 UTC (5+ messages)
` [bitcoin-dev] [Lightning-dev] "
[bitcoin-dev] Recursive covenant opposition, or the absence thereof, was Re: TXHASH + CHECKSIGFROMSTACKVERIFY in lieu of CTV and ANYPREVOUT
2022-02-14 2:40 UTC
[bitcoin-dev] Advancing the security of Neutrino using minimally trusted oracles
2022-02-11 2:39 UTC (3+ messages)
[bitcoin-dev] Improving RBF Policy
2022-02-09 17:57 UTC
[bitcoin-dev] CTV Meeting Notes #3
2022-02-09 8:53 UTC
[bitcoin-dev] Improving RBF Policy
2022-02-08 4:58 UTC (9+ messages)
[bitcoin-dev] BIP-119 CTV Meeting #3 Draft Agenda for Tuesday February 8th at 12:00 PT
2022-02-07 19:10 UTC (2+ messages)
[bitcoin-dev] CTV dramatically improves DLCs
2022-02-07 2:30 UTC (10+ messages)
` [bitcoin-dev] [dlc-dev] "
[bitcoin-dev] CHECKSIGFROMSTACK/{Verify} BIP for Bitcoin
2022-02-03 6:17 UTC (9+ messages)
` [bitcoin-dev] Unlimited covenants, was "
[bitcoin-dev] CTV Meeting #2 Summary & Minutes
2022-02-02 20:04 UTC
[bitcoin-dev] non-default ports for automatic connections in Bitcoin P2P network
2022-02-02 13:30 UTC (2+ messages)
[bitcoin-dev] Improving RBF Policy
2022-02-02 10:21 UTC (3+ messages)
[bitcoin-dev] Why CTV, why now? Was RE: Stumbling into a contentious soft fork activation attempt
2022-02-02 1:43 UTC (3+ messages)
` [bitcoin-dev] Why CTV, why now?
[bitcoin-dev] Improving RBF policy
2022-02-01 19:44 UTC (5+ messages)
[bitcoin-dev] PathCoin
2022-01-30 15:39 UTC (6+ messages)
[bitcoin-dev] BIP-119 CTV Meeting #2 Agenda for Tuesday January 25th at 12:00 PT
2022-01-24 3:36 UTC
[bitcoin-dev] Renaming full nodes
2022-01-23 13:06 UTC (2+ messages)
[bitcoin-dev] Covenants and capabilities in the UTXO model
2022-01-22 0:19 UTC (8+ messages)
[bitcoin-dev] Bob-Pays-For-Transaction
2022-01-21 23:45 UTC
[bitcoin-dev] CTV BIP review
2022-01-21 17:36 UTC (11+ messages)
[bitcoin-dev] Bitcoin Legal Defense Fund
2022-01-21 14:36 UTC (11+ messages)
[bitcoin-dev] Take 2: Removing the Dust Limit
2022-01-21 12:16 UTC
[bitcoin-dev] Highlighting Taproot implementation gotchas
2022-01-20 12:58 UTC
[bitcoin-dev] On the regularity of soft forks
2022-01-19 2:26 UTC (2+ messages)
[bitcoin-dev] CTV BIP review
2022-01-18 22:20 UTC
[bitcoin-dev] [Bitcoin Advent Calendar] Decentralized Coordination Free Mining Pools
2022-01-18 18:15 UTC (4+ messages)
[bitcoin-dev] bip39
2022-01-18 16:33 UTC (4+ messages)
[bitcoin-dev] On the regularity of soft forks
2022-01-18 16:00 UTC (2+ messages)
[bitcoin-dev] SASE Invoices
2022-01-18 1:48 UTC
[bitcoin-dev] BIP proposal: Pay-to-contract tweak fields for PSBT (bip-psbt-p2c)
2022-01-17 5:55 UTC (2+ messages)
[bitcoin-dev] CTV and ANYPREVOUT vault designs
2022-01-15 17:19 UTC
[bitcoin-dev] Documenting the lifetime of a transaction during mempool congestion from the perspective of a rational user
2022-01-13 21:06 UTC
[bitcoin-dev] Bitcoin Legal Defense Fund
2022-01-13 19:25 UTC (3+ messages)
[bitcoin-dev] OP_PUSH_KEY_* & BIP-118 0x01 Pun
2022-01-13 1:45 UTC (2+ messages)
page: next (older) | prev (newer) | latest
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox