Bitcoin Development Mailinglist
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
			download mbox.gz: |
 601. Re: [bitcoin-dev] Testing censorship resistance of bitcoin p2p network
      - by Peter Todd @ 2023-02-18  0:03 UTC [0%]

 602. Re: [bitcoin-dev] Testing censorship resistance of bitcoin p2p network
      - by Andrew Poelstra @ 2023-02-17 23:35 UTC [2%]

 603. Re: [bitcoin-dev] Testing censorship resistance of bitcoin p2p network
      - by vjudeu @ 2023-02-17 14:56 UTC [3%]

 604. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Anthony Towns @ 2023-02-17 12:49 UTC [3%]

 605. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-17 10:56 UTC [1%]

 606. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Claus Ehrenberg @ 2023-02-16 19:59 UTC [2%]

 607. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-16 18:23 UTC [1%]

 608. Re: [bitcoin-dev] Unenforceable fee obligations in multiparty protocols with Taproot inputs
      - by Antoine Riard @ 2023-02-15  3:33 UTC [0%]

 609. [bitcoin-dev] Testing censorship resistance of bitcoin p2p network
      - by alicexbt @ 2023-02-13 12:34 UTC [2%]

 610. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-12 16:23 UTC [1%]

 611. Re: [bitcoin-dev] Unenforceable fee obligations in multiparty protocols with Taproot inputs
      - by Yuval Kogman @ 2023-02-10 19:35 UTC [1%]

 612. Re: [bitcoin-dev] Unenforceable fee obligations in multiparty protocols with Taproot inputs
      - by Antoine Riard @ 2023-02-08  0:56 UTC [0%]

 613. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Aymeric Vitte @ 2023-02-07 12:17 UTC [2%]

 614. Re: [bitcoin-dev] Unenforceable fee obligations in multiparty protocols with Taproot inputs
      - by Nadav Ivgi @ 2023-02-07  9:36 UTC [0%]

 615. Re: [bitcoin-dev] Unenforceable fee obligations in multiparty protocols with Taproot inputs
      - by Lloyd Fournier @ 2023-02-07  4:38 UTC [0%]

 616. [bitcoin-dev] Unenforceable fee obligations in multiparty protocols with Taproot inputs
      - by Yuval Kogman @ 2023-02-07  2:49 UTC [1%]

 617. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Erik Aronesty @ 2023-02-06 18:05 UTC [2%]

 618. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Claus Ehrenberg @ 2023-02-06 17:31 UTC [4%]

 619. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Erik Aronesty @ 2023-02-06 16:39 UTC [2%]

 620. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Russell O'Connor @ 2023-02-05 18:12 UTC [1%]

 621. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Andrew Poelstra @ 2023-02-05 18:06 UTC [1%]

 622. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-05 12:47 UTC [1%]

 623. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Peter Todd @ 2023-02-05 12:06 UTC [1%]

 624. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-05 11:40 UTC [1%]

 625. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Peter Todd @ 2023-02-05  2:01 UTC [1%]

 626. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Peter Todd @ 2023-02-05  0:04 UTC [1%]

 627. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Russell O'Connor @ 2023-02-05  0:11 UTC [1%]

 628. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-04 23:09 UTC [1%]

 629. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Christopher Allen @ 2023-02-04 22:18 UTC [1%]

 630. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-04 20:55 UTC [1%]

 631. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Christopher Allen @ 2023-02-04 18:54 UTC [1%]

 632. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-04 17:01 UTC [1%]

 633. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Kostas Karasavvas @ 2023-02-04 14:25 UTC [5%]

 634. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Kostas Karasavvas @ 2023-02-04 14:11 UTC [4%]

 635. Re: [bitcoin-dev] Purely off-chain coin colouring
      - by alicexbt @ 2023-02-04 13:02 UTC [4%]

 636. Re: [bitcoin-dev] Purely off-chain coin colouring
      - by Aymeric Vitte @ 2023-02-04 11:36 UTC [0%]

 637. Re: [bitcoin-dev] Purely off-chain coin colouring
      - by Anthony Towns @ 2023-02-04 10:38 UTC [3%]

 638. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Melvin Carvalho @ 2023-02-03 19:56 UTC [2%]

 639. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Christopher Allen @ 2023-02-03 18:47 UTC [4%]

 640. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-03 11:15 UTC [1%]

 641. Re: [bitcoin-dev] Purely off-chain coin colouring
      - by Casey Rodarmor @ 2023-02-03  6:39 UTC [3%]

 642. Re: [bitcoin-dev] Purely off-chain coin colouring
      - by Aymeric Vitte @ 2023-02-02 16:06 UTC [1%]

 643. Re: [bitcoin-dev] Purely off-chain coin colouring
      - by Peter Todd @ 2023-02-02 14:30 UTC [1%]

 644. Re: [bitcoin-dev] Purely off-chain coin colouring
      - by alicexbt @ 2023-02-02 14:22 UTC [3%]

 645. Re: [bitcoin-dev] Purely off-chain coin colouring
      - by Rijndael @ 2023-02-02 13:46 UTC [0%]

 646. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Rijndael @ 2023-02-02 13:25 UTC [1%]

 647. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-02 12:24 UTC [1%]

 648. Re: [bitcoin-dev] Purely off-chain coin colouring
      - by Aymeric Vitte @ 2023-02-02 12:19 UTC [1%]

 649. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Peter Todd @ 2023-02-02 11:49 UTC [1%]

 650. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-02 11:45 UTC [1%]

 651. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Peter Todd @ 2023-02-02 11:22 UTC [1%]

 652. [bitcoin-dev] Purely off-chain coin colouring
      - by Anthony Towns @ 2023-02-02  9:15 UTC [3%]

 653. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Andrew Poelstra @ 2023-02-01 14:02 UTC [1%]

 654. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-01 12:59 UTC [1%]

 655. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Peter Todd @ 2023-02-01 12:51 UTC [1%]

 656. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Kostas Karasavvas @ 2023-02-01  8:36 UTC [2%]

 657. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Christopher Allen @ 2023-02-01  2:22 UTC [1%]

 658. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Peter Todd @ 2023-02-01  2:07 UTC [1%]

 659. [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Christopher Allen @ 2023-02-01  0:46 UTC [2%]

 660. Re: [bitcoin-dev] A Universal Coin Swap system based on bitcoin and a Bitcoin NFT system
      - by Aymeric Vitte @ 2023-01-31 18:36 UTC [1%]

 661. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Erik Aronesty @ 2023-01-31  8:58 UTC [2%]

 662. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Robert Dickinson @ 2023-01-29 10:34 UTC [2%]

 663. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Aymeric Vitte @ 2023-01-28 16:47 UTC [2%]

 664. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by alicexbt @ 2023-01-28 10:58 UTC [4%]

 665. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Robert Dickinson @ 2023-01-28  4:26 UTC [5%]

 666. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Aymeric Vitte @ 2023-01-27 15:43 UTC [3%]

 667. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Andrew Poelstra @ 2023-01-27 13:21 UTC [2%]

 668. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by rot13maxi @ 2023-01-27 12:58 UTC [5%]

 669. [bitcoin-dev] Ordinal Inscription Size Limits
      - by Robert Dickinson @ 2023-01-27 12:44 UTC [6%]

 670. [bitcoin-dev] A Universal Coin Swap system based on bitcoin and a Bitcoin NFT system
      - by Aymeric Vitte @ 2023-01-26 20:15 UTC [1%]

 671. Re: [bitcoin-dev] Using OP_VAULT to improve DLCs
      - by Billy Tetrud @ 2023-01-19 22:42 UTC [0%]

 672. [bitcoin-dev] Using OP_VAULT to improve DLCs
      - by Ben Carman @ 2023-01-12 12:32 UTC [1%]

 673. Re: [bitcoin-dev] A Bitcoin NFT System
      - by Aymeric Vitte @ 2023-01-05 10:46 UTC [1%]

 674. Re: [bitcoin-dev] Announcement: Full-RBF Miner Bounty
      - by 0xB10C @ 2022-12-10 11:59 UTC [0%]

 675. Re: [bitcoin-dev] Announcement: Full-RBF Miner Bounty
      - by Peter Todd @ 2022-12-09 21:16 UTC [1%]

 676. Re: [bitcoin-dev] Announcement: Full-RBF Miner Bounty
      - by 0xB10C @ 2022-12-09 16:04 UTC [1%]

 677. Re: [bitcoin-dev] On mempool policy consistency
      - by email @ 2022-11-10 14:38 UTC [0%]

 678. Re: [bitcoin-dev] On mempool policy consistency
      - by email @ 2022-11-09 12:05 UTC [0%]

 679. Re: [bitcoin-dev] brickchain
      - by mm-studios @ 2022-11-08 16:31 UTC [0%]

 680. Re: [bitcoin-dev] brickchain
      - by Erik Aronesty @ 2022-11-08 15:49 UTC [0%]

 681. Re: [bitcoin-dev] On mempool policy consistency
      - by email @ 2022-11-08 14:54 UTC [1%]

 682. Re: [bitcoin-dev] brickchain
      - by mm-studios @ 2022-11-08 14:25 UTC [0%]

 683. Re: [bitcoin-dev] brickchain
      - by Erik Aronesty @ 2022-11-08 14:16 UTC [0%]

 684. Re: [bitcoin-dev] On mempool policy consistency
      - by AdamISZ @ 2022-11-08  9:28 UTC [0%]

 685. Re: [bitcoin-dev] On mempool policy consistency
      - by Erik Aronesty @ 2022-11-07 14:47 UTC [0%]

 686. Re: [bitcoin-dev] On mempool policy consistency
      - by Peter Todd @ 2022-11-07 14:32 UTC [1%]

 687. Re: [bitcoin-dev] [Lightning-dev] Taro: A Taproot Asset Representation Overlay
      - by Johan Torås Halseth @ 2022-11-07 13:51 UTC [0%]

 688. Re: [bitcoin-dev] Preventing/detecting pinning of jointly funded txs
      - by Anthony Towns @ 2022-11-07 11:46 UTC [1%]

 689. Re: [bitcoin-dev] [Lightning-dev] Taro: A Taproot Asset Representation Overlay
      - by Olaoluwa Osuntokun @ 2022-11-05  0:35 UTC [1%]

 690. Re: [bitcoin-dev] On mempool policy consistency
      - by email @ 2022-11-03 21:06 UTC [1%]

 691. Re: [bitcoin-dev] On mempool policy consistency
      - by Anthony Towns @ 2022-10-30  2:24 UTC [1%]

 692. Re: [bitcoin-dev] On mempool policy consistency
      - by Antoine Riard @ 2022-10-27 20:29 UTC [0%]

 693. Re: [bitcoin-dev] On mempool policy consistency
      - by Greg Sanders @ 2022-10-27 19:00 UTC [0%]

 694. Re: [bitcoin-dev] On mempool policy consistency
      - by Luke Dashjr @ 2022-10-27 18:17 UTC [0%]

 695. Re: [bitcoin-dev] On mempool policy consistency
      - by Greg Sanders @ 2022-10-27 17:44 UTC [0%]

 696. Re: [bitcoin-dev] On mempool policy consistency
      - by Suhas Daftuar @ 2022-10-27 17:35 UTC [0%]

 697. Re: [bitcoin-dev] On mempool policy consistency
      - by Anthony Towns @ 2022-10-27 17:21 UTC [1%]

 698. Re: [bitcoin-dev] On mempool policy consistency
      - by Anthony Towns @ 2022-10-27 15:37 UTC [2%]

 699. Re: [bitcoin-dev] On mempool policy consistency
      - by Greg Sanders @ 2022-10-27 13:49 UTC [0%]

 700. Re: [bitcoin-dev] On mempool policy consistency
      - by Gloria Zhao @ 2022-10-27 12:36 UTC [1%]

 701. Re: [bitcoin-dev] On mempool policy consistency
      - by John Carvalho @ 2022-10-27  9:56 UTC [0%]

 702. [bitcoin-dev] On mempool policy consistency
      - by Anthony Towns @ 2022-10-26 23:52 UTC [1%]

 703. Re: [bitcoin-dev] [Opt-in full-RBF] Zero-conf apps in immediate danger
      - by alicexbt @ 2022-10-23 20:51 UTC [1%]

 704. Re: [bitcoin-dev] Relaxing minimum non-witness transaction size policy restriction
      - by Greg Sanders @ 2022-10-21  0:07 UTC [0%]

 705. Re: [bitcoin-dev] Does Bitcoin require or have an honest majority or a rational one? (re rbf)
      - by Jeremy Rubin @ 2022-10-20 23:54 UTC [0%]

 706. Re: [bitcoin-dev] Relaxing minimum non-witness transaction size policy restriction
      - by Peter Todd @ 2022-10-20 23:21 UTC [1%]

 707. Re: [bitcoin-dev] brickchain
      - by mm-studios @ 2022-10-19 22:53 UTC [0%]

 708. Re: [bitcoin-dev] brickchain
      - by mm-studios @ 2022-10-19 22:47 UTC [0%]

 709. Re: [bitcoin-dev] brickchain
      - by G. Andrew Stone @ 2022-10-19 21:34 UTC [1%]

 710. Re: [bitcoin-dev] brickchain
      - by mm-studios @ 2022-10-19 16:03 UTC [0%]

 711. Re: [bitcoin-dev] brickchain
      - by Erik Aronesty @ 2022-10-19 14:24 UTC [0%]

 712. Re: [bitcoin-dev] brickchain
      - by angus @ 2022-10-19 13:40 UTC [0%]

 713. [bitcoin-dev] brickchain
      - by mm-studios @ 2022-10-19  9:04 UTC [1%]

 714. Re: [bitcoin-dev] Relaxing minimum non-witness transaction size policy restriction
      - by Greg Sanders @ 2022-10-11 13:14 UTC [0%]

 715. [bitcoin-dev] Relaxing minimum non-witness transaction size policy restriction
      - by Greg Sanders @ 2022-10-11 12:50 UTC [1%]

 716. Re: [bitcoin-dev] Spookchains: Drivechain Analog with One-Time Trusted Setup & APO
      - by Antoine Riard @ 2022-09-30  2:00 UTC [0%]

 717. Re: [bitcoin-dev] Packaged Transaction Relay
      - by Eric Voskuil @ 2022-09-27 19:21 UTC [0%]

 718. Re: [bitcoin-dev] Packaged Transaction Relay
      - by alicexbt @ 2022-09-27  9:29 UTC [0%]

 719. Re: [bitcoin-dev] Packaged Transaction Relay
      - by eric @ 2022-09-26 21:19 UTC [1%]

 720. [bitcoin-dev] Spookchains: Drivechain Analog with One-Time Trusted Setup & APO
      - by Jeremy Rubin @ 2022-09-14 18:31 UTC [1%]

 721. Re: [bitcoin-dev] Multipayment Channels - A scalability solution for Layer 1
      - by ZmnSCPxj @ 2022-09-05  3:17 UTC [0%]

 722. [bitcoin-dev] Multipayment Channels - A scalability solution for Layer 1
      - by Ali Sherief @ 2022-09-04 22:31 UTC [1%]

 723. [bitcoin-dev] BIP Draft: Revocable Proof-of-Burn Transaction Template
      - by Велеслав @ 2022-08-25 19:24 UTC [1%]

 724. Re: [bitcoin-dev] Regarding setting a lower minrelaytxfee
      - by Billy Tetrud @ 2022-08-04  1:21 UTC [0%]

 725. Re: [bitcoin-dev] Regarding setting a lower minrelaytxfee
      - by Aaradhya Chauhan @ 2022-08-03 18:22 UTC [0%]

 726. Re: [bitcoin-dev] Regarding setting a lower minrelaytxfee
      - by vjudeu @ 2022-08-03 17:07 UTC [0%]

 727. Re: [bitcoin-dev] Regarding setting a lower minrelaytxfee
      - by Aaradhya Chauhan @ 2022-08-03 15:40 UTC [0%]

 728. Re: [bitcoin-dev] Regarding setting a lower minrelaytxfee
      - by Peter Todd @ 2022-08-01 13:37 UTC [0%]

 729. Re: [bitcoin-dev] Regarding setting a lower minrelaytxfee
      - by aliashraf.btc At protonmail @ 2022-08-01 13:19 UTC [1%]

 730. Re: [bitcoin-dev] New BIP: Private Payments
      - by Alfred Hodler @ 2022-08-01 11:38 UTC [1%]

 731. Re: [bitcoin-dev] How to do Proof of Micro-Burn?
      - by Peter Todd @ 2022-07-19 23:13 UTC [0%]

 732. Re: [bitcoin-dev] How to do Proof of Micro-Burn?
      - by Ruben Somsen @ 2022-07-19 22:23 UTC [1%]

 733. Re: [bitcoin-dev] How to do Proof of Micro-Burn?
      - by Ruben Somsen @ 2022-07-17 20:40 UTC [1%]

 734. [bitcoin-dev] How to do Proof of Micro-Burn?
      - by Велеслав @ 2022-07-17 13:28 UTC [1%]

 735. Re: [bitcoin-dev] [BIP proposal] Private Payments
      - by Alfred Hodler @ 2022-07-11 10:28 UTC [0%]

 736. Re: [bitcoin-dev] Bitcoin covenants are inevitable
      - by Corey Haddad @ 2022-07-07 22:02 UTC [0%]

 737. Re: [bitcoin-dev] Bitcoin covenants are inevitable
      - by John Carvalho @ 2022-07-07 13:24 UTC [1%]

 738. Re: [bitcoin-dev] [BIP proposal] Private Payments
      - by Alfred Hodler @ 2022-07-01 12:41 UTC [1%]

 739. Re: [bitcoin-dev] [BIP proposal] Private Payments
      - by Clark Moody @ 2022-06-29 22:33 UTC [1%]

 740. Re: [bitcoin-dev] [BIP proposal] Private Payments
      - by Alfred Hodler @ 2022-06-28 12:40 UTC [0%]

 741. Re: [bitcoin-dev] [BIP proposal] Private Payments
      - by Alfred Hodler @ 2022-06-28 12:35 UTC [1%]

 742. Re: [bitcoin-dev] [BIP proposal] Private Payments
      - by Ruben Somsen @ 2022-06-27 20:35 UTC [0%]

 743. Re: [bitcoin-dev] [BIP proposal] Private Payments
      - by Ruben Somsen @ 2022-06-27 20:30 UTC [0%]

 744. Re: [bitcoin-dev] [BIP proposal] Private Payments
      - by Bryan Bishop @ 2022-06-27 20:20 UTC [1%]

 745. [bitcoin-dev] [BIP proposal] Private Payments
      - by Alfred Hodler @ 2022-06-27 18:17 UTC [1%]

 746. Re: [bitcoin-dev] bitcoin-dev Digest, Vol 85, Issue 4
      - by Billy Tetrud @ 2022-06-15  4:02 UTC [0%]

 747. Re: [bitcoin-dev] Why OpenTimestamps does not "linearize" its transactions
      - by Undiscussed Horrific Abuse, One Victim of Many @ 2022-06-14 17:15 UTC [1%]

 748. Re: [bitcoin-dev] Why OpenTimestamps does not "linearize" its transactions
      - by Peter Todd @ 2022-06-14 15:34 UTC [0%]

 749. Re: [bitcoin-dev] Why OpenTimestamps does not "linearize" its transactions
      - by digital vagabond @ 2022-06-14 15:06 UTC [0%]

 750. Re: [bitcoin-dev] Why OpenTimestamps does not "linearize" its transactions
      - by Bryan Bishop @ 2022-06-14 13:55 UTC [1%]

 751. Re: [bitcoin-dev] Why OpenTimestamps does not "linearize" its transactions
      - by Undiscussed Horrific Abuse, One Victim of Many @ 2022-06-14 12:45 UTC [1%]

 752. Re: [bitcoin-dev] BIP47 Prague Discussion
      - by Paul Sztorc @ 2022-06-11 14:30 UTC [0%]

 753. [bitcoin-dev] BIP47 Prague Discussion
      - by Ruben Somsen @ 2022-06-11 10:01 UTC [1%]

 754. Re: [bitcoin-dev] bitcoin-dev Digest, Vol 85, Issue 4
      - by Billy Tetrud @ 2022-06-08  4:05 UTC [0%]

 755. Re: [bitcoin-dev] Bitcoin covenants are inevitable
      - by Erik Aronesty @ 2022-06-06 13:02 UTC [0%]

 756. Re: [bitcoin-dev] bitcoin-dev Digest, Vol 85, Issue 4
      - by Luke Kenneth Casson Leighton @ 2022-06-05 12:31 UTC [1%]

 757. Re: [bitcoin-dev] Bitcoin covenants are inevitable
      - by alicexbt @ 2022-06-04 16:12 UTC [1%]

 758. Re: [bitcoin-dev] Bitcoin covenants are inevitable
      - by Keagan McClelland @ 2022-06-04 13:48 UTC [0%]

 759. Re: [bitcoin-dev] Bitcoin covenants are inevitable
      - by John Carvalho @ 2022-06-04 12:27 UTC [1%]

 760. [bitcoin-dev] CTV BIP Meeting #9 Notes
      - by alicexbt @ 2022-05-19 15:57 UTC [1%]

 761. Re: [bitcoin-dev] ANYPREVOUT in place of CTV
      - by Nadav Ivgi @ 2022-05-01 14:25 UTC [0%]

 762. Re: [bitcoin-dev] ANYPREVOUT in place of CTV
      - by Greg Sanders @ 2022-04-30 11:15 UTC [0%]

 763. Re: [bitcoin-dev] ANYPREVOUT in place of CTV
      - by Nadav Ivgi @ 2022-04-30  8:09 UTC [1%]

 764. Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks
      - by micaroni @ 2022-04-28  8:03 UTC [0%]

 765. Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks
      - by Nadav Ivgi @ 2022-04-28  0:16 UTC [0%]

 766. Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks
      - by Keagan McClelland @ 2022-04-27 18:32 UTC [0%]

 767. Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks
      - by Jeremy Rubin @ 2022-04-27 17:54 UTC [0%]

 768. Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks
      - by micaroni @ 2022-04-27 17:22 UTC [0%]

 769. Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks
      - by Billy Tetrud @ 2022-04-27 16:17 UTC [0%]

 770. Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks
      - by Erik Aronesty @ 2022-04-27 14:28 UTC [0%]

 771. Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks
      - by Chris Riley @ 2022-04-27 14:01 UTC [0%]

 772. Re: [bitcoin-dev] What to expect in the next few weeks
      - by alicexbt @ 2022-04-27  5:59 UTC [1%]

 773. Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks
      - by Billy Tetrud @ 2022-04-27  3:04 UTC [0%]

 774. Re: [bitcoin-dev] Towards a means of measuring user support for Soft Forks
      - by Bryan Bishop @ 2022-04-26 20:39 UTC [0%]

 775. [bitcoin-dev] Towards a means of measuring user support for Soft Forks
      - by Keagan McClelland @ 2022-04-26 19:37 UTC [1%]

 776. Re: [bitcoin-dev] Automatically reverting ("transitory") soft forks, e.g. for CTV
      - by Antoine Riard @ 2022-04-22 19:57 UTC [0%]

 777. Re: [bitcoin-dev] CTV Signet Parameters
      - by Jeremy Rubin @ 2022-04-21 15:05 UTC [1%]

 778. Re: [bitcoin-dev] Automatically reverting ("transitory") soft forks, e.g. for CTV
      - by alicexbt @ 2022-04-21  3:10 UTC [0%]

 779. Re: [bitcoin-dev] Automatically reverting ("transitory") soft forks, e.g. for CTV
      - by Luke Dashjr @ 2022-04-21  2:05 UTC [0%]

 780. [bitcoin-dev] Automatically reverting ("transitory") soft forks, e.g. for CTV
      - by David A. Harding @ 2022-04-21  1:04 UTC [1%]

 781. Re: [bitcoin-dev] [Pre-BIP] Fee Accounts
      - by Peter Todd @ 2022-04-10 19:32 UTC [0%]

 782. Re: [bitcoin-dev] [Lightning-dev] Taro: A Taproot Asset Representation Overlay
      - by Alex Schoof @ 2022-04-07 19:11 UTC [0%]

 783. Re: [bitcoin-dev] Taro: A Taproot Asset Representation Overlay
      - by Ruben Somsen @ 2022-04-07 17:14 UTC [1%]

 784. Re: [bitcoin-dev] Silent Payments – Non-interactive private payments with no on-chain overhead
      - by Ruben Somsen @ 2022-03-31 10:48 UTC [0%]

 785. Re: [bitcoin-dev] Silent Payments – Non-interactive private payments with no on-chain overhead
      - by Billy @ 2022-03-30 16:09 UTC [0%]

 786. Re: [bitcoin-dev] Silent Payments – Non-interactive private payments with no on-chain overhead
      - by Billy @ 2022-03-30  5:58 UTC [0%]

 787. Re: [bitcoin-dev] Silent Payments – Non-interactive private payments with no on-chain overhead
      - by Ruben Somsen @ 2022-03-29 15:36 UTC [0%]

 788. Re: [bitcoin-dev] Silent Payments – Non-interactive private payments with no on-chain overhead
      - by Billy @ 2022-03-29 14:57 UTC [0%]

 789. [bitcoin-dev] Silent Payments – Non-interactive private payments with no on-chain overhead
      - by Ruben Somsen @ 2022-03-28 15:27 UTC [1%]

 790. Re: [bitcoin-dev] Speedy Trial
      - by Jorge Timón @ 2022-03-24 18:30 UTC [0%]

 791. Re: [bitcoin-dev] Speedy Trial
      - by Anthony Towns @ 2022-03-22 23:49 UTC [1%]

 792. Re: [bitcoin-dev] Speedy Trial
      - by vjudeu @ 2022-03-22 16:37 UTC [1%]

 793. Re: [bitcoin-dev] Beyond Jets: Microcode: Consensus-Critical Jets Without Softforks
      - by Russell O'Connor @ 2022-03-22 16:28 UTC [0%]

 794. Re: [bitcoin-dev] Beyond Jets: Microcode: Consensus-Critical Jets Without Softforks
      - by ZmnSCPxj @ 2022-03-22 16:22 UTC [0%]

 795. Re: [bitcoin-dev] Speedy Trial
      - by Billy Tetrud @ 2022-03-22 15:19 UTC [0%]

 796. Re: [bitcoin-dev] Beyond Jets: Microcode: Consensus-Critical Jets Without Softforks
      - by Russell O'Connor @ 2022-03-22 15:08 UTC [1%]

 797. [bitcoin-dev] Beyond Jets: Microcode: Consensus-Critical Jets Without Softforks
      - by ZmnSCPxj @ 2022-03-22  5:37 UTC [1%]

 798. Re: [bitcoin-dev] Speedy Trial
      - by vjudeu @ 2022-03-21 15:56 UTC [1%]

 799. Re: [bitcoin-dev] OP_RETURN inside TapScript
      - by Kostas Karasavvas @ 2022-03-21 11:00 UTC [1%]

 800. Re: [bitcoin-dev] Speedy Trial
      - by Billy Tetrud @ 2022-03-21  3:41 UTC [1%]


Results 601-800 of ~3000   |  | reverse | options above

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox