| Age | Commit message (Expand) | Author | Files | Lines |
|---|
| 2025-02-19 | Re: [bitcoindev] P2QRH / BIP-360 Update | Dustin Ray | 1 | -0/+709 |
| 2024-12-09 | Re: [bitcoindev] Covenants Support - Bitcoin Wiki | Anthony Towns | 1 | -0/+186 |
| 2024-05-12 | [bitcoindev] Penlock, a paper-computer for secret-splitting BIP39 seed phrases | 'Rama Gan' via Bitcoin Development Mailing List | 1 | -0/+187 |
| 2023-11-14 | Re: [bitcoin-dev] Future of the bitcoin-dev mailing list | Ali Sherief | 1 | -0/+143 |
| 2023-10-24 | Re: [bitcoin-dev] Proposed BIP for OP_CAT | Andrew Poelstra | 1 | -0/+146 |
| 2023-08-09 | Re: [bitcoin-dev] Concrete MATT opcodes | Salvatore Ingala | 1 | -0/+182 |
| 2023-05-25 | Re: [bitcoin-dev] bitcoin-dev Digest, Vol 96, Issue 58 | ecurrencyhodler | 1 | -0/+885 |
| 2023-02-04 | Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_... | Aymeric Vitte | 1 | -0/+361 |
| 2022-10-14 | Re: [bitcoin-dev] [Opt-in full-RBF] Zero-conf apps in immediate danger | Peter Todd | 1 | -0/+149 |
| 2022-07-26 | Re: [bitcoin-dev] On a new community process to specify covenants | Antoine Riard | 1 | -0/+238 |
| 2022-05-01 | Re: [bitcoin-dev] BIP proposal: Timelocked address fidelity bond for BIP39 seeds | Chris Belcher | 1 | -0/+103 |
| 2022-04-28 | Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks | Billy Tetrud | 1 | -0/+382 |
| 2022-02-17 | Re: [bitcoin-dev] TXHASH + CHECKSIGFROMSTACKVERIFY in lieu of CTV and ANYPREVOUT | Russell O'Connor | 1 | -0/+123 |
| 2022-02-15 | Re: [bitcoin-dev] TXHASH + CHECKSIGFROMSTACKVERIFY in lieu of CTV and ANYPREVOUT | Rusty Russell | 1 | -0/+75 |
| 2022-02-02 | Re: [bitcoin-dev] non-default ports for automatic connections in Bitcoin P2P ... | Vasil Dimov | 1 | -0/+170 |
| 2022-01-14 | Re: [bitcoin-dev] Bitcoin Legal Defense Fund | Jeremy | 1 | -0/+288 |
| 2021-11-30 | Re: [bitcoin-dev] A fee-bumping model | Antoine Riard | 1 | -0/+1295 |
| 2021-06-24 | Re: [bitcoin-dev] Opinion on proof of stake in future | Billy Tetrud | 1 | -0/+377 |
| 2021-04-22 | [bitcoin-dev] And Then What? Defining a Complete Process for Upgrades | Jeremy | 1 | -0/+1807 |
| 2021-03-02 | Re: [bitcoin-dev] Proposal for new "disabletx" p2p message | John Newbery | 1 | -0/+1384 |
| 2021-02-28 | Re: [bitcoin-dev] Taproot activation meeting 2 - Tuesday 16th February 19:00 UTC | Luke Dashjr | 1 | -0/+195 |
| 2021-02-06 | Re: [bitcoin-dev] BIP32/43-based standard for Schnorr signatures & decentrali... | Pieter Wuille | 1 | -0/+168 |
| 2020-12-31 | Re: [bitcoin-dev] Softchains: Sidechains as a Soft Fork via Proof-of-Work Fra... | Sergio Demian Lerner | 1 | -0/+415 |
| 2020-07-21 | Re: [bitcoin-dev] The Cryptographic Relay: An Electrical Device For Smart Tra... | Andy Schroder | 1 | -0/+495 |
| 2020-04-22 | Re: [bitcoin-dev] Academic research regarding BIP0002 | Shiva Jairam | 1 | -0/+291 |
| 2020-02-26 | Re: [bitcoin-dev] Removing Single Point of Failure with Seed Phrase Storage | Christopher Allen | 1 | -0/+76197 |
| 2019-10-20 | Re: [bitcoin-dev] Trustless hash-price insurance contracts | Lucas H | 1 | -0/+676 |
| 2019-10-09 | Re: [bitcoin-dev] [Lightning-dev] OP_CAT was Re: Continuing the discussion ab... | Andrew Poelstra | 1 | -0/+129 |
| 2019-07-17 | Re: [bitcoin-dev] Secure Proof Of Stake implementation on Bitcoin | ZmnSCPxj | 1 | -0/+99 |
| 2019-06-27 | Re: [bitcoin-dev] Taproot proposal | Russell O'Connor | 1 | -0/+279 |
| 2018-02-13 | Re: [bitcoin-dev] Possible change to the MIT license | Aymeric Vitte | 1 | -0/+325 |
| 2018-02-05 | Re: [bitcoin-dev] Graftroot: Private and efficient surrogate scripts under th... | Gregory Maxwell | 1 | -0/+86 |
| 2018-01-16 | Re: [bitcoin-dev] Proposal to reduce mining power bill | nullius | 1 | -0/+238 |
| 2017-11-20 | Re: [bitcoin-dev] Why SegWit Anyway? | Praveen Baratam | 1 | -0/+212 |
| 2017-11-03 | Re: [bitcoin-dev] Bitcoin Cash's new difficulty algorithm | gb | 1 | -0/+114 |
| 2017-08-22 | Re: [bitcoin-dev] UTXO growth scaling solution proposal | Daniele Pinna | 1 | -0/+77 |
| 2017-06-20 | [bitcoin-dev] Miners forced to run non-core code in order to get segwit activ... | Erik Aronesty | 1 | -0/+95 |
| 2017-05-03 | Re: [bitcoin-dev] Small Nodes: A Better Alternative to Pruned Nodes | Aymeric Vitte | 1 | -0/+281 |
| 2017-04-15 | [bitcoin-dev] Diminishing Signaling Returns | Crypto.Press | 1 | -0/+238 |
| 2017-03-05 | Re: [bitcoin-dev] Unique node identifiers | John Hardy | 1 | -0/+465 |
| 2016-09-21 | Re: [bitcoin-dev] Requesting BIP assignment; Flexible Transactions. | Tom | 1 | -0/+118 |
| 2016-08-10 | Re: [bitcoin-dev] Hiding entire content of on-chain transactions | James MacWhyte | 1 | -0/+144 |
| 2016-06-30 | Re: [bitcoin-dev] BIP 151 | Eric Voskuil | 1 | -0/+141 |
| 2016-06-21 | Re: [bitcoin-dev] Even more proposed BIP extensions to BIP 0070 | Peter Todd | 1 | -0/+110 |
| 2016-04-09 | Re: [bitcoin-dev] p2p authentication and encryption BIPs | Lee Clagett | 1 | -0/+276 |
| 2016-02-17 | Re: [bitcoin-dev] [BIP Proposal] New "feefilter" p2p message | Luke Dashjr | 1 | -0/+66 |
| 2016-02-06 | Re: [bitcoin-dev] BIP proposal: Increase block size limit to 2 megabytes | Luke Dashjr | 1 | -0/+114 |
| 2015-11-02 | Re: [bitcoin-dev] Compatibility requirements for hard or soft forks | Justus Ranvier | 1 | -0/+422 |
| 2015-11-02 | Re: [bitcoin-dev] Ramping up with bitcoin core engineering? | Eric Martindale | 1 | -0/+138 |
| 2015-09-20 | Re: [bitcoin-dev] Scaling Bitcoin conference micro-report | Steven Pine | 1 | -0/+146 |
