Bitcoin Development Mailinglist
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
			download mbox.gz: |
 401. Re: [bitcoindev] Redefine packages to discourage address reuse
      - by Peter Todd @ 2024-10-29 16:43 UTC [0%]

 402. Re: [bitcoindev] Redefine packages to discourage address reuse
      - by /dev /fd0 @ 2024-10-24  3:43 UTC [2%]

 403. Re: [bitcoindev] Re: Proposing a P2QRH BIP towards a quantum resistant soft fork
      - by Hunter Beast @ 2024-09-25 12:04 UTC [1%]

 404. Re: [bitcoindev] OP_CAT Research Fund sponsored by StarkWare
      - by Greg Tonoski @ 2024-08-29 13:43 UTC [1%]

 405. Re: [bitcoindev] Keyless Anchors Are Vulnerable To Replacement Cycling Attacks
      - by Antoine Riard @ 2024-08-27 19:39 UTC [1%]

 406. Re: [bitcoindev] BIP 8.5: Flag day activation based on nlocktime signaling
      - by /dev /fd0 @ 2024-08-22 11:43 UTC [0%]

 407. Re: [bitcoindev] Re: Proposing a P2QRH BIP towards a quantum resistant soft fork
      - by Antoine Riard @ 2024-08-22  6:20 UTC [1%]

 408. Re: [bitcoindev] BIP 8.5: Flag day activation based on nlocktime signaling
      - by Murch @ 2024-08-20 18:05 UTC [1%]

 409. Re: [bitcoindev] BIP 8.5: Flag day activation based on nlocktime signaling
      - by /dev /fd0 @ 2024-08-19 17:50 UTC [1%]

 410. Re: [bitcoindev] BIP 8.5: Flag day activation based on nlocktime signaling
      - by /dev /fd0 @ 2024-08-19 17:50 UTC [1%]

 411. Re: [bitcoindev] A "Free" Relay Attack Taking Advantage of The Lack of Full-RBF In Core
      - by Antoine Riard @ 2024-08-16  4:20 UTC [1%]

 412. Re: [bitcoindev] Re: Proposing a P2QRH BIP towards a quantum resistant soft fork
      - by Hunter Beast @ 2024-08-15  5:05 UTC [0%]

 413. Re: [bitcoindev] Re: Proposing a P2QRH BIP towards a quantum resistant soft fork
      - by Hunter Beast @ 2024-08-06 17:37 UTC [1%]

 414. Re: [bitcoindev] Public disclosure of 2 vulnerabilities affecting Bitcoin Core < v22.0
      - by 'hashnoncemessage' via Bitcoin Development Mailing List @ 2024-08-04  6:41 UTC [1%]

 415. Re: [bitcoindev] Re: A "Free" Relay Attack Taking Advantage of The Lack of Full-RBF In Core
      - by Garlo Nicon @ 2024-08-01  5:57 UTC [1%]

 416. Re: [bitcoindev] Mining pools, stratumv2 and oblivious shares
      - by Anthony Towns @ 2024-07-31 18:00 UTC [1%]

 417. Re: [bitcoindev] Re: A "Free" Relay Attack Taking Advantage of The Lack of Full-RBF In Core
      - by Antoine Riard @ 2024-07-24  0:35 UTC [1%]

 418. Re: [bitcoindev] Re: Proposing a P2QRH BIP towards a quantum resistant soft fork
      - by Antoine Riard @ 2024-07-13  1:34 UTC [1%]

 419. Re: [bitcoindev] Re: Proposing a P2QRH BIP towards a quantum resistant soft fork
      - by hunter @ 2024-06-17 20:27 UTC [1%]

 420. Re: [bitcoindev] The Future of Bitcoin Testnet
      - by Garlo Nicon @ 2024-05-01 15:30 UTC [1%]

 421. Re: [bitcoindev] Signing a Bitcoin Transaction with Lamport Signatures (no changes needed)
      - by Ethan Heilman @ 2024-04-30 13:25 UTC [0%]

 422. Re: [bitcoindev] Signing a Bitcoin Transaction with Lamport Signatures (no changes needed)
      - by Matthew Zipkin @ 2024-04-30 12:32 UTC [0%]

 423. [bitcoindev] Signing a Bitcoin Transaction with Lamport Signatures (no changes needed)
      - by Ethan Heilman @ 2024-04-29  0:30 UTC [1%]

 424. Re: [bitcoindev] The Future of Bitcoin Testnet
      - by Garlo Nicon @ 2024-04-09 18:28 UTC [1%]

 425. Re: [bitcoindev] Time for an update to BIP2?
      - by Pieter Wuille @ 2024-04-03 19:44 UTC [0%]

 426. [bitcoindev] Time for an update to BIP2?
      - by Tim Ruffing @ 2024-04-02 13:17 UTC [1%]

 427. [bitcoindev] Re: [bitcoin-dev] CheckTemplateVerify Does Not Scale Due to UTXO's Required For Fee Payment
      - by 'jlspc' via Bitcoin Development Mailing List @ 2024-02-20 23:13 UTC [1%]

 428. [bitcoindev] bitcoin-dev Mailing List Migration (Action Required)
      - by Bryan Bishop @ 2024-02-09 20:34 UTC [1%]

 429. Re: [bitcoin-dev] One-Shot Replace-By-Fee-Rate
      - by Peter Todd @ 2024-01-27  7:19 UTC [1%]

 430. Re: [bitcoin-dev] One-Shot Replace-By-Fee-Rate
      - by Peter Todd @ 2024-01-24  4:44 UTC [1%]

 431. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Brad Morrison @ 2024-01-04 13:50 UTC [0%]

 432. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Erik Aronesty @ 2024-01-03 13:05 UTC [2%]

 433. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Brad Morrison @ 2024-01-03  9:11 UTC [2%]

 434. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Erik Aronesty @ 2024-01-01 16:08 UTC [2%]

 435. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Brad Morrison @ 2024-01-01 13:33 UTC [3%]

 436. Re: [bitcoin-dev] Lamport scheme (not signature) to economize on L1
      - by yurisvb @ 2023-12-31 17:42 UTC [0%]

 437. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Erik Aronesty @ 2023-12-30  9:58 UTC [3%]

 438. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Nagaev Boris @ 2023-12-29 19:01 UTC [2%]

 439. Re: [bitcoin-dev] Scaling Lightning Safely With Feerate-Dependent Timelocks
      - by David A. Harding @ 2023-12-29 18:11 UTC [1%]

 440. Re: [bitcoin-dev] Ordinal Inscription Size Limits
      - by Greg Tonoski @ 2023-12-29 12:27 UTC [4%]

 441. Re: [bitcoin-dev] Lamport scheme (not signature) to economize on L1
      - by yurisvb @ 2023-12-29  0:30 UTC [0%]

 442. Re: [bitcoin-dev] Scaling Lightning Safely With Feerate-Dependent Timelocks
      - by jlspc @ 2023-12-28 18:19 UTC [0%]

 443. Re: [bitcoin-dev] Scaling Lightning Safely With Feerate-Dependent Timelocks
      - by jlspc @ 2023-12-28 18:06 UTC [0%]

 444. Re: [bitcoin-dev] Lamport scheme (not signature) to economize on L1
      - by yurisvb @ 2023-12-23  0:26 UTC [0%]

 445. Re: [bitcoin-dev] Scaling Lightning Safely With Feerate-Dependent Timelocks
      - by Nagaev Boris @ 2023-12-22 16:36 UTC [1%]

 446. Re: [bitcoin-dev] Lamport scheme (not signature) to economize on L1
      - by yurisvb @ 2023-12-22 15:32 UTC [0%]

 447. Re: [bitcoin-dev] Lamport scheme (not signature) to economize on L1
      - by G. Andrew Stone @ 2023-12-22  4:52 UTC [0%]

 448. Re: [bitcoin-dev] Scaling Lightning Safely With Feerate-Dependent Timelocks
      - by jlspc @ 2023-12-22  1:25 UTC [0%]

 449. Re: [bitcoin-dev] Lamport scheme (not signature) to economize on L1
      - by yurisvb @ 2023-12-21 16:07 UTC [0%]

 450. Re: [bitcoin-dev] Lamport scheme (not signature) to economize on L1
      - by Nagaev Boris @ 2023-12-20 21:33 UTC [0%]

 451. Re: [bitcoin-dev] Lamport scheme (not signature) to economize on L1
      - by yurisvb @ 2023-12-19 21:22 UTC [1%]

 452. Re: [bitcoin-dev] Addressing the possibility of profitable fee manipulation attacks
      - by alicexbt @ 2023-12-18  6:26 UTC [2%]

 453. Re: [bitcoin-dev] Scaling Lightning Safely With Feerate-Dependent Timelocks
      - by Antoine Riard @ 2023-12-17 23:01 UTC [1%]

 454. [bitcoin-dev] Scaling Lightning Safely With Feerate-Dependent Timelocks
      - by jlspc @ 2023-12-14 17:07 UTC [1%]

 455. Re: [bitcoin-dev] bip-0127 "Simple Proof-of-Reserves Transactions"
      - by Ademan @ 2023-12-12 18:21 UTC [1%]

 456. Re: [bitcoin-dev] Ordinals BIP PR
      - by Kostas Karasavvas @ 2023-11-22 11:27 UTC [0%]

 457. Re: [bitcoin-dev] Ordinals BIP PR
      - by vjudeu @ 2023-11-21 23:10 UTC [1%]

 458. Re: [bitcoin-dev] Ordinals BIP PR
      - by Kostas Karasavvas @ 2023-11-21 12:13 UTC [1%]

 459. Re: [bitcoin-dev] Ordinals BIP PR
      - by vjudeu @ 2023-11-20 22:20 UTC [1%]

 460. Re: [bitcoin-dev] Purely off-chain coin colouring
      - by vjudeu @ 2023-11-20 19:47 UTC [1%]

 461. Re: [bitcoin-dev] Purely off-chain coin colouring
      - by Anthony Towns @ 2023-11-17  7:58 UTC [3%]

 462. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Overthefalls @ 2023-11-14 15:32 UTC [0%]

 463. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Ali Sherief @ 2023-11-14 12:32 UTC [1%]

 464. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by alicexbt @ 2023-11-13 18:51 UTC [0%]

 465. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Overthefalls @ 2023-11-13 15:05 UTC [1%]

 466. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Antoine Riard @ 2023-11-13  2:58 UTC [0%]

 467. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by vjudeu @ 2023-11-11 10:54 UTC [1%]

 468. Re: [bitcoin-dev] Ordinals BIP PR
      - by Claus Ehrenberg @ 2023-11-09 22:32 UTC [0%]

 469. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by William Casarin @ 2023-11-09  4:03 UTC [1%]

 470. Re: [bitcoin-dev] Ordinals BIP PR
      - by Casey Rodarmor @ 2023-11-09  2:15 UTC [2%]

 471. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Emil Pfeffer @ 2023-11-08 14:29 UTC [1%]

 472. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by email @ 2023-11-08  9:05 UTC [0%]

 473. Re: [bitcoin-dev] bitcoin-dev Digest, Vol 102, Issue 15
      - by Luke Kenneth Casson Leighton @ 2023-11-08  2:00 UTC [1%]

 474. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Peter Todd @ 2023-11-07 23:08 UTC [1%]

 475. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by ponymontana @ 2023-11-07 22:10 UTC [0%]

 476. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Tao Effect @ 2023-11-07 20:57 UTC [1%]

 477. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Ademan @ 2023-11-07 20:15 UTC [1%]

 478. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Andrew Chow @ 2023-11-07 18:14 UTC [0%]

 479. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Ademan @ 2023-11-07 17:03 UTC [0%]

 480. Re: [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Andrew Chow @ 2023-11-07 16:12 UTC [1%]

 481. [bitcoin-dev] Future of the bitcoin-dev mailing list
      - by Bryan Bishop @ 2023-11-07 15:37 UTC [1%]

 482. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by ArmchairCryptologist @ 2023-11-04  9:58 UTC [2%]

 483. Re: [bitcoin-dev] The Pinning & Replacement Problem Set
      - by Antoine Riard @ 2023-11-03 19:57 UTC [1%]

 484. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Melvin Carvalho @ 2023-11-03 10:39 UTC [1%]

 485. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Brad Morrison @ 2023-11-03 10:15 UTC [1%]

 486. Re: [bitcoin-dev] Ordinals BIP PR
      - by Alexander F. Moser @ 2023-10-27  9:39 UTC [1%]

 487. Re: [bitcoin-dev] Ordinals BIP PR
      - by Christopher Allen @ 2023-10-24 23:08 UTC [1%]

 488. Re: [bitcoin-dev] Ordinals BIP PR
      - by alicexbt @ 2023-10-24  1:28 UTC [1%]

 489. Re: [bitcoin-dev] Ordinals BIP PR
      - by Ryan Breen @ 2023-10-23 17:26 UTC [2%]

 490. Re: [bitcoin-dev] New BIP to align descriptors, xpub derivation and miniscript
      - by Antoine Poinsot @ 2023-09-11 12:03 UTC [0%]

 491. [bitcoin-dev] New BIP to align descriptors, xpub derivation and miniscript
      - by Dr Maxim Orlovsky @ 2023-09-10 17:13 UTC [1%]

 492. Re: [bitcoin-dev] Concern about "Inscriptions"
      - by vjudeu @ 2023-09-06  8:00 UTC [5%]

 493. Re: [bitcoin-dev] Concern about "Inscriptions"
      - by Peter Todd @ 2023-09-05 17:49 UTC [6%]

 494. Re: [bitcoin-dev] Concern about "Inscriptions"
      - by vjudeu @ 2023-09-03 16:01 UTC [5%]

 495. Re: [bitcoin-dev] Concern about "Inscriptions"
      - by Erik Aronesty @ 2023-08-23 17:34 UTC [2%]

 496. Re: [bitcoin-dev] Concern about "Inscriptions"
      - by GamedevAlice @ 2023-08-22 14:18 UTC [5%]

 497. [bitcoin-dev]  Concern about "Inscriptions"
      - by martl.chris @ 2023-08-22  5:15 UTC [4%]

 498. Re: [bitcoin-dev] Concern about "Inscriptions"
      - by symphonicbtc @ 2023-08-21 22:34 UTC [2%]

 499. Re: [bitcoin-dev] Concern about "Inscriptions"
      - by John Tromp @ 2023-08-21 16:28 UTC [6%]

 500. Re: [bitcoin-dev] Concern about "Inscriptions"
      - by rot13maxi @ 2023-08-21 14:58 UTC [2%]

 501. Re: [bitcoin-dev] Concern about "Inscriptions"
      - by Russell O'Connor @ 2023-08-21 14:47 UTC [4%]

 502. [bitcoin-dev]  Concern about "Inscriptions"
      - by martl.chris @ 2023-08-18 20:43 UTC [2%]

 503. [bitcoin-dev] Full-RBF testing: at least 31% of hash power, over at least 4 pools, is mining full-RBF right now
      - by Peter Todd @ 2023-08-16 10:25 UTC [1%]

 504. Re: [bitcoin-dev] Pull-req to remove the arbitrary limits on OP_Return outputs
      - by Murch @ 2023-08-09 13:06 UTC [1%]

 505. Re: [bitcoin-dev] Pull-req to remove the arbitrary limits on OP_Return outputs
      - by ZmnSCPxj @ 2023-08-08  1:34 UTC [2%]

 506. Re: [bitcoin-dev] Pull-req to remove the arbitrary limits on OP_Return outputs
      - by John Light @ 2023-08-06 20:35 UTC [5%]

 507. Re: [bitcoin-dev] Concern about "Inscriptions".
      - by leohaf @ 2023-08-03 16:03 UTC [5%]

 508. Re: [bitcoin-dev] Concern about "Inscriptions".
      - by GamedevAlice @ 2023-08-03 13:33 UTC [2%]

 509. [bitcoin-dev] Pull-req to remove the arbitrary limits on OP_Return outputs
      - by Peter Todd @ 2023-08-03 11:42 UTC [1%]

 510. Re: [bitcoin-dev] Concern about "Inscriptions"
      - by Luke Dashjr @ 2023-08-02 15:46 UTC [2%]

 511. Re: [bitcoin-dev] Concern about "Inscriptions". (Keagan McClelland)
      - by Einherjar @ 2023-08-02 13:50 UTC [2%]

 512. Re: [bitcoin-dev] Concern about "Inscriptions"
      - by GamedevAlice @ 2023-08-02 11:07 UTC [2%]

 513. Re: [bitcoin-dev] Concern about "Inscriptions". (ashneverdawn)
      - by Keagan McClelland @ 2023-08-02  5:58 UTC [5%]

 514. Re: [bitcoin-dev] Concern about "Inscriptions". (ashneverdawn)
      - by Hugo L @ 2023-07-31  4:12 UTC [3%]

 515. Re: [bitcoin-dev] Concern about "Inscriptions".
      - by rot13maxi @ 2023-07-30 18:34 UTC [6%]

 516. Re: [bitcoin-dev] Concern about "Inscriptions".
      - by Léo Haf @ 2023-07-27 19:03 UTC [3%]

 517. Re: [bitcoin-dev] [SPAM]  Concern about "Inscriptions".
      - by aymeric @ 2023-07-27 10:41 UTC [6%]

 518. Re: [bitcoin-dev] Concern about "Inscriptions".
      - by vjudeu @ 2023-07-27  5:10 UTC [6%]

 519. Re: [bitcoin-dev] Concern about "Inscriptions".
      - by leohaf @ 2023-07-26  9:46 UTC [8%]

 520. Re: [bitcoin-dev] Concern about "Inscriptions".
      - by vjudeu @ 2023-07-26  5:30 UTC [5%]

 521. [bitcoin-dev] Concern about "Inscriptions".
      - by leohaf @ 2023-07-25 14:11 UTC [8%]

 522. Re: [bitcoin-dev] Standardisation of an unstructured taproot annex
      - by Antoine Riard @ 2023-07-04 20:18 UTC [1%]

 523. [bitcoin-dev] CivKit Node v0.0.1 release - "Sic itur ad astra"
      - by Antoine Riard @ 2023-06-21  8:14 UTC [1%]

 524. Re: [bitcoin-dev] Standardisation of an unstructured taproot annex
      - by Joost Jager @ 2023-06-20 12:30 UTC [0%]

 525. Re: [bitcoin-dev] Standardisation of an unstructured taproot annex
      - by Greg Sanders @ 2023-06-12 13:03 UTC [0%]

 526. Re: [bitcoin-dev] Bitcoin mail list needs an explicit moderation policy
      - by vjudeu @ 2023-06-12  5:26 UTC [1%]

 527. Re: [bitcoin-dev] Standardisation of an unstructured taproot annex
      - by Antoine Riard @ 2023-06-12  3:16 UTC [1%]

 528. Re: [bitcoin-dev] Standardisation of an unstructured taproot annex
      - by Joost Jager @ 2023-06-10  7:43 UTC [3%]

 529. Re: [bitcoin-dev] Scaling and anonymizing Bitcoin at layer 1 with client-side validation
      - by Peter Todd @ 2023-06-05 18:09 UTC [0%]

 530. [bitcoin-dev] Conceptual package relay using taproot annex
      - by Joost Jager @ 2023-06-05  7:57 UTC [1%]

 531. Re: [bitcoin-dev] Bitcoin mail list needs an explicit moderation policy
      - by alicexbt @ 2023-06-03 17:21 UTC [0%]

 532. Re: [bitcoin-dev] Standardisation of an unstructured taproot annex
      - by Greg Sanders @ 2023-06-03 12:05 UTC [1%]

 533. Re: [bitcoin-dev] Standardisation of an unstructured taproot annex
      - by Joost Jager @ 2023-06-03  7:49 UTC [2%]

 534. Re: [bitcoin-dev] Standardisation of an unstructured taproot annex
      - by Greg Sanders @ 2023-06-03  1:14 UTC [0%]

 535. Re: [bitcoin-dev] Standardisation of an unstructured taproot annex
      - by David A. Harding @ 2023-06-03  1:08 UTC [2%]

 536. Re: [bitcoin-dev] [Lightning-dev] Bitcoin mail list needs an explicit moderation policy
      - by Bryan Bishop @ 2023-06-03  0:06 UTC [0%]

 537. [bitcoin-dev] Bitcoin mail list needs an explicit moderation policy
      - by Dr Maxim Orlovsky @ 2023-06-02 23:43 UTC [1%]

 538. [bitcoin-dev] Scaling and anonymizing Bitcoin at layer 1 with client-side validation
      - by Dr Maxim Orlovsky @ 2023-06-01 17:21 UTC [1%]

 539. [bitcoin-dev] Bitcoin Core 25.0 released
      - by Michael Ford @ 2023-05-26 10:39 UTC [1%]

 540. [bitcoin-dev] Stake Certificates and Web-of-Stakes: privacy-preserving proving UTXOs attributes in P2P systems
      - by Antoine Riard @ 2023-05-18  6:08 UTC [1%]

 541. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by jk_14 @ 2023-05-12  9:36 UTC [1%]

 542. Re: [bitcoin-dev] tx max fee
      - by Andrew Baine @ 2023-05-11 15:20 UTC [0%]

 543. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Aleksandr Kwaskoff @ 2023-05-11 13:12 UTC [1%]

 544. Re: [bitcoin-dev] tx max fee
      - by Kalle Rosenbaum @ 2023-05-11 12:32 UTC [0%]

 545. Re: [bitcoin-dev] tx max fee
      - by vjudeu @ 2023-05-11 11:02 UTC [1%]

 546. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Keagan McClelland @ 2023-05-10 20:44 UTC [2%]

 547. Re: [bitcoin-dev] tx max fee
      - by Erik Aronesty @ 2023-05-10 17:42 UTC [0%]

 548. Re: [bitcoin-dev] tx max fee
      - by vjudeu @ 2023-05-10 16:19 UTC [1%]

 549. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Weiji Guo @ 2023-05-10  3:08 UTC [3%]

 550. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Tom Harding @ 2023-05-09 21:06 UTC [1%]

 551. Re: [bitcoin-dev] Witness script validation to reject arbitrary data
      - by Aymeric Vitte @ 2023-05-09 17:45 UTC [1%]

 552. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Erik Aronesty @ 2023-05-09 16:32 UTC [1%]

 553. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Tom Harding @ 2023-05-09 15:21 UTC [1%]

 554. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Erik Aronesty @ 2023-05-09 12:50 UTC [1%]

 555. Re: [bitcoin-dev] Witness script validation to reject arbitrary data
      - by Moth @ 2023-05-09 12:20 UTC [1%]

 556. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by jk_14 @ 2023-05-09  8:41 UTC [2%]

 557. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Ali Sherief @ 2023-05-09  1:43 UTC [2%]

 558. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Peter Todd @ 2023-05-09  0:02 UTC [5%]

 559. Re: [bitcoin-dev] Witness script validation to reject arbitrary data
      - by Peter Todd @ 2023-05-08 23:55 UTC [4%]

 560. Re: [bitcoin-dev] tx max fee
      - by Peter Todd @ 2023-05-08 23:57 UTC [0%]

 561. Re: [bitcoin-dev] tx max fee
      - by Erik Aronesty @ 2023-05-09  0:04 UTC [0%]

 562. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Luke Dashjr @ 2023-05-08 22:37 UTC [3%]

 563. Re: [bitcoin-dev] Witness script validation to reject arbitrary data
      - by Christopher Allen @ 2023-05-08 21:43 UTC [3%]

 564. Re: [bitcoin-dev] Witness script validation to reject arbitrary data
      - by angus @ 2023-05-08 21:33 UTC [2%]

 565. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Erik Aronesty @ 2023-05-08 21:01 UTC [1%]

 566. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Erik Aronesty @ 2023-05-08 20:59 UTC [1%]

 567. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Michael Folkson @ 2023-05-08 20:36 UTC [1%]

 568. [bitcoin-dev] Witness script validation to reject arbitrary data
      - by Moth @ 2023-05-08 20:16 UTC [3%]

 569. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Erik Aronesty @ 2023-05-08 19:47 UTC [1%]

 570. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Ali Sherief @ 2023-05-08 19:31 UTC [1%]

 571. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Michael Folkson @ 2023-05-08 17:13 UTC [1%]

 572. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Melvin Carvalho @ 2023-05-08 16:37 UTC [1%]

 573. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Erik Aronesty @ 2023-05-08 12:58 UTC [1%]

 574. Re: [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Michael Folkson @ 2023-05-08 12:33 UTC [1%]

 575. [bitcoin-dev] tx max fee
      - by Erik Aronesty @ 2023-05-07 23:59 UTC [1%]

 576. [bitcoin-dev] [Mempool spam] Should we as developers reject non-standard Taproot transactions from full nodes?
      - by Ali Sherief @ 2023-05-07 17:22 UTC [1%]

 577. Re: [bitcoin-dev] Bitcoin fungibility and inscribed sats
      - by Kree Love @ 2023-04-20 23:06 UTC [0%]

 578. Re: [bitcoin-dev] Bitcoin Core maintainers and communication on merge decisions
      - by Aymeric Vitte @ 2023-04-20 14:25 UTC [0%]

 579. Re: [bitcoin-dev] Bitcoin Core maintainers and communication on merge decisions
      - by Erik Aronesty @ 2023-04-20 13:59 UTC [0%]

 580. Re: [bitcoin-dev] Bitcoin Core maintainers and communication on merge decisions
      - by Aymeric Vitte @ 2023-04-20 10:54 UTC [0%]

 581. Re: [bitcoin-dev] Bitcoin Core maintainers and communication on merge decisions
      - by Michael Folkson @ 2023-04-20  8:45 UTC [0%]

 582. Re: [bitcoin-dev] Bitcoin Core maintainers and communication on merge decisions
      - by Andrew Chow @ 2023-04-19 21:33 UTC [1%]

 583. Re: [bitcoin-dev] Bitcoin Core maintainers and communication on merge decisions
      - by Aymeric Vitte @ 2023-04-19 15:17 UTC [1%]

 584. Re: [bitcoin-dev] RGB protocol announcement
      - by Dr Maxim Orlovsky @ 2023-04-18 23:16 UTC [1%]

 585. [bitcoin-dev] RGB protocol announcement
      - by Dr Maxim Orlovsky @ 2023-04-10 22:09 UTC [1%]

 586. Re: [bitcoin-dev] Bitcoin ungibility and inscribed sats
      - by Steve Lee @ 2023-04-01  7:29 UTC [2%]

 587. [bitcoin-dev] Bitcoin fungibility and inscribed sats
      - by alicexbt @ 2023-03-31 16:30 UTC [2%]

 588. Re: [bitcoin-dev] BIP for OP_VAULT
      - by alicexbt @ 2023-03-30 18:12 UTC [0%]

 589. Re: [bitcoin-dev] BIP for OP_VAULT
      - by Zac Greenwood @ 2023-03-30 10:39 UTC [1%]

 590. Re: [bitcoin-dev] BIP for OP_VAULT
      - by Steve Lee @ 2023-03-30  0:16 UTC [0%]

 591. Re: [bitcoin-dev] BIP for OP_VAULT
      - by alicexbt @ 2023-03-29 19:57 UTC [0%]

 592. Re: [bitcoin-dev] BIP for OP_VAULT
      - by Zac Greenwood @ 2023-03-29  7:10 UTC [0%]

 593. Re: [bitcoin-dev] BIP for OP_VAULT
      - by Anthony Towns @ 2023-03-24 12:10 UTC [1%]

 594. [bitcoin-dev] BIP: Trust minimized swaps using PSBT, SINGLE|ANYONECANPAY and nostr
      - by alicexbt @ 2023-03-03  1:44 UTC [3%]

 595. Re: [bitcoin-dev] Testing censorship resistance of bitcoin p2p network
      - by Peter Todd @ 2023-02-22 16:39 UTC [0%]

 596. Re: [bitcoin-dev] Testing censorship resistance of bitcoin p2p network
      - by alicexbt @ 2023-02-19  0:33 UTC [4%]

 597. Re: [bitcoin-dev] Debate: 64 bytes in OP_RETURN VS taproot OP_FALSE OP_IF OP_PUSH
      - by Aymeric Vitte @ 2023-02-18 18:38 UTC [3%]

 598. Re: [bitcoin-dev] Testing censorship resistance of bitcoin p2p network
      - by Russell O'Connor @ 2023-02-18 18:03 UTC [1%]

 599. Re: [bitcoin-dev] Testing censorship resistance of bitcoin p2p network
      - by vjudeu @ 2023-02-18  9:48 UTC [1%]

 600. Re: [bitcoin-dev] Testing censorship resistance of bitcoin p2p network
      - by Andrew Poelstra @ 2023-02-18  1:28 UTC [0%]


Results 401-600 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