Bitcoin Development Mailinglist
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
			download mbox.gz: |
1601. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Gregory Maxwell @ 2015-07-29 19:53 UTC [1%]

1602. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Mike Hearn @ 2015-07-29 18:03 UTC [1%]

1603. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Jorge Timón @ 2015-07-29 18:00 UTC [1%]

1604. Re: [bitcoin-dev] Răspuns:  Personal opinion on the fee market from a worried local trader
      - by Raystonn . @ 2015-07-29 17:47 UTC [1%]

1605. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Sriram Karra @ 2015-07-29 17:30 UTC [1%]

1606. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn'ttemporary
      - by Raystonn . @ 2015-07-29 17:17 UTC [1%]

1607. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Gregory Maxwell @ 2015-07-29 16:53 UTC [1%]

1608. [bitcoin-dev] Răspuns:  Personal opinion on the fee market from a worried local trader
      - by Vali Zero @ 2015-07-29 14:09 UTC [1%]

1609. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Thomas Zander @ 2015-07-29 12:13 UTC [1%]

1610. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Eric Lombrozo @ 2015-07-29 12:03 UTC [1%]

1611. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Thomas Zander @ 2015-07-29 11:29 UTC [1%]

1612. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Thomas Zander @ 2015-07-29 11:18 UTC [1%]

1613. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Mike Hearn @ 2015-07-29 11:15 UTC [1%]

1614. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Eric Lombrozo @ 2015-07-29 10:43 UTC [1%]

1615. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Mike Hearn @ 2015-07-29  9:59 UTC [1%]

1616. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Eric Lombrozo @ 2015-07-29  5:17 UTC [1%]

1617. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Milly Bitcoin @ 2015-07-29  3:46 UTC [1%]

1618. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Eric Lombrozo @ 2015-07-29  3:37 UTC [1%]

1619. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Eric Lombrozo @ 2015-07-29  2:40 UTC [1%]

1620. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Eric Lombrozo @ 2015-07-29  0:55 UTC [1%]

1621. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Mark Friedenbach @ 2015-07-29  0:46 UTC [1%]

1622. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Eric Lombrozo @ 2015-07-29  0:44 UTC [1%]

1623. Re: [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Jean-Paul Kogelman @ 2015-07-29  0:43 UTC [2%]

1624. [bitcoin-dev] Why Satoshi's temporary anti-spam measure isn't temporary
      - by Eric Lombrozo @ 2015-07-28 22:25 UTC [1%]

1625. Re: [bitcoin-dev] [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-07-26 21:13 UTC [0%]

1626. Re: [bitcoin-dev] [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-07-24  6:55 UTC [0%]

1627. [bitcoin-dev] QR code alternatives (was: Proposal: extend bip70 with OpenAlias)
      - by Mike Hearn @ 2015-07-20 14:40 UTC [1%]

1628. Re: [bitcoin-dev] BIP 102 - kick the can down the road to 2MB
      - by Venzen Khaosan @ 2015-07-18  4:32 UTC [1%]

1629. Re: [bitcoin-dev] BIP 102 - kick the can down the road to 2MB
      - by Angel Leon @ 2015-07-17 21:13 UTC [1%]

1630. Re: [bitcoin-dev] Significant losses by double-spending unconfirmed transactions
      - by Peter Todd @ 2015-07-17 11:59 UTC [1%]

1631. Re: [bitcoin-dev] Significant losses by double-spending unconfirmed transactions
      - by Greg Schvey @ 2015-07-16 15:33 UTC [0%]

1632. Re: [bitcoin-dev] Significant losses by double-spending unconfirmed transactions
      - by Me @ 2015-07-16 14:50 UTC [0%]

1633. Re: [bitcoin-dev] Significant losses by double-spending unconfirmed transactions
      - by Arne Brutschy @ 2015-07-16 14:30 UTC [0%]

1634. Re: [bitcoin-dev] Mailing List Administrivia - GPG, Archives, Breakage, TODO, mirrors, etc
      - by grarpamp @ 2015-07-16  4:57 UTC [0%]

1635. Re: [bitcoin-dev] Significant losses by double-spending unconfirmed transactions
      - by Milly Bitcoin @ 2015-07-15 19:57 UTC [1%]

1636. Re: [bitcoin-dev] Significant losses by double-spending unconfirmed transactions
      - by Matthieu Riou @ 2015-07-15 18:25 UTC [0%]

1637. Re: [bitcoin-dev] Significant losses by double-spending unconfirmed transactions
      - by Adrian Macneil @ 2015-07-15 17:01 UTC [0%]

1638. Re: [bitcoin-dev] Significant losses by double-spending unconfirmed transactions
      - by Milly Bitcoin @ 2015-07-15 16:12 UTC [1%]

1639. Re: [bitcoin-dev] Bitcoin Core 0.11.0 released
      - by odinn @ 2015-07-15 11:20 UTC [0%]

1640. [bitcoin-dev] Significant losses by double-spending unconfirmed transactions
      - by simongreen @ 2015-07-15  3:29 UTC [1%]

1641. Re: [bitcoin-dev] Proposal: extend bip70 with OpenAlias
      - by Mike Hearn @ 2015-07-13 22:31 UTC [1%]

1642. Re: [bitcoin-dev] Bitcoin Core 0.11.0 released
      - by Wladimir J. van der Laan @ 2015-07-12 17:13 UTC [1%]

1643. Re: [bitcoin-dev] Bitcoin Core 0.11.0 released
      - by Wladimir J. van der Laan @ 2015-07-12 16:41 UTC [1%]

1644. [bitcoin-dev] Bitcoin Core 0.11.0 released
      - by Wladimir J. van der Laan @ 2015-07-12 15:49 UTC [1%]

1645. Re: [bitcoin-dev] Why not Child-Pays-For-Parent?
      - by Matt Whitlock @ 2015-07-12 10:18 UTC [0%]

1646. Re: [bitcoin-dev] Why not Child-Pays-For-Parent?
      - by Jeff Garzik @ 2015-07-11 22:29 UTC [0%]

1647. Re: [bitcoin-dev] Why not Child-Pays-For-Parent?
      - by Dan Bryant @ 2015-07-11 21:30 UTC [1%]

1648. Re: [bitcoin-dev] Why not Child-Pays-For-Parent?
      - by Tier Nolan @ 2015-07-10 17:28 UTC [1%]

1649. Re: [bitcoin-dev] Can we penalize peers who relay rejected replacement txs?
      - by Tom Harding @ 2015-07-10  1:57 UTC [0%]

1650. Re: [bitcoin-dev] Can we penalize peers who relay rejected replacement txs?
      - by Matt Whitlock @ 2015-07-10  1:36 UTC [1%]

1651. Re: [bitcoin-dev] Can we penalize peers who relay rejected replacement txs?
      - by Matt Whitlock @ 2015-07-10  1:12 UTC [0%]

1652. [bitcoin-dev] Can we penalize peers who relay rejected replacement txs?
      - by Matt Whitlock @ 2015-07-09 23:55 UTC [1%]

1653. Re: [bitcoin-dev] block-size tradeoffs & hypothetical alternatives (Re: Block size increase oppositionists: please clearly define what you need done to increase block size to a static 8MB, and help do it)
      - by Tom Harding @ 2015-06-30 22:56 UTC [1%]

1654. Re: [bitcoin-dev] BIP: Full Replace-by-Fee deployment schedule
      - by Adam Back @ 2015-06-30 13:12 UTC [0%]

1655. Re: [bitcoin-dev] BIP: Full Replace-by-Fee deployment schedule
      - by Peter Todd @ 2015-06-30  1:37 UTC [2%]

1656. Re: [bitcoin-dev] Mailing List Administrivia - GPG, Archives, Breakage, TODO, mirrors, etc
      - by Warren Togami Jr. @ 2015-06-29  2:27 UTC [1%]

1657. Re: [bitcoin-dev] Mailing List Administrivia - GPG, Archives, Breakage, TODO, mirrors, etc
      - by Andy Schroder @ 2015-06-29  1:49 UTC [0%]

1658. Re: [bitcoin-dev] Original Vision
      - by Aaron Voisine @ 2015-06-28  1:52 UTC [1%]

1659. Re: [bitcoin-dev] Mailing List Administrivia - GPG, Archives, Breakage, TODO, mirrors, etc
      - by Jeff Garzik @ 2015-06-27 23:54 UTC [0%]

1660. [bitcoin-dev] Mailing List Administrivia - GPG, Archives, Breakage, TODO, mirrors, etc
      - by grarpamp @ 2015-06-27 22:21 UTC [1%]

1661. Re: [bitcoin-dev] [RFC] IBLT block testing implementation
      - by Rusty Russell @ 2015-06-27  4:46 UTC [0%]

1662. Re: [bitcoin-dev] The need for larger blocks
      - by Aaron Voisine @ 2015-06-26 19:05 UTC [0%]

1663. Re: [bitcoin-dev] The need for larger blocks
      - by Patrick Strateman @ 2015-06-26 18:47 UTC [0%]

1664. Re: [bitcoin-dev] The need for larger blocks
      - by Mark Friedenbach @ 2015-06-26 18:31 UTC [0%]

1665. Re: [bitcoin-dev] The need for larger blocks
      - by Alex Morcos @ 2015-06-26 18:29 UTC [0%]

1666. Re: [bitcoin-dev] The need for larger blocks
      - by Jeff Garzik @ 2015-06-26 18:23 UTC [0%]

1667. Re: [bitcoin-dev] The need for larger blocks
      - by Pieter Wuille @ 2015-06-26 18:12 UTC [0%]

1668. Re: [bitcoin-dev] The need for larger blocks
      - by Jeff Garzik @ 2015-06-26 17:57 UTC [1%]

1669. Re: [bitcoin-dev] [RFC] IBLT block testing implementation
      - by Kalle Rosenbaum @ 2015-06-25 21:02 UTC [0%]

1670. [bitcoin-dev] game-theory, miner incentive alignment vs current proposals
      - by Adam Back @ 2015-06-23 19:42 UTC [0%]

1671. Re: [bitcoin-dev] Welcome to the new Bitcoin Dev List
      - by Andy Schroder @ 2015-06-23 18:45 UTC [0%]

1672. Re: [bitcoin-dev] Draft BIP : fixed-schedule block size increase
      - by Ross Nicoll @ 2015-06-23  7:59 UTC [1%]

1673. [bitcoin-dev] [RFC] IBLT block testing implementation
      - by Rusty Russell @ 2015-06-23  5:53 UTC [1%]

1674. Re: [bitcoin-dev] Welcome to the new Bitcoin Dev List
      - by s7r @ 2015-06-21 21:35 UTC [0%]

1675. Re: [bitcoin-dev] Welcome to the new Bitcoin Dev List
      - by Btc Drak @ 2015-06-21 21:31 UTC [0%]

1676. [bitcoin-dev] Welcome to the new Bitcoin Dev List
      - by Warren Togami Jr. @ 2015-06-21 21:29 UTC [1%]

1677. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-06-21 14:39 UTC [0%]

1678. [Bitcoin-development] Fwd: Re: [RFC] Canonical input and output ordering in transactions
      - by Jorge Timón @ 2015-06-21  7:27 UTC [0%]

1679. [Bitcoin-development] IMPORTANT - Bitcoin Dev List Move Tuesday, June 23rd 8pm UTC
      - by Warren Togami Jr. @ 2015-06-20  7:48 UTC [1%]

1680. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by David Vorick @ 2015-06-20  3:49 UTC [1%]

1681. Re: [Bitcoin-development] F2Pool has enabled full replace-by-fee
      - by Jeffrey Paul @ 2015-06-19 19:49 UTC [1%]

1682. Re: [Bitcoin-development] Mailman incompatibility with DKIM ...
      - by Mike Hearn @ 2015-06-19 10:49 UTC [1%]

1683. Re: [Bitcoin-development] Mailman incompatibility with DKIM ...
      - by Mike Hearn @ 2015-06-19 10:24 UTC [1%]

1684. Re: [Bitcoin-development] Mailman incompatibility with DKIM ...
      - by Warren Togami Jr. @ 2015-06-19 10:10 UTC [1%]

1685. Re: [Bitcoin-development] Mailman incompatibility with DKIM ...
      - by Mike Hearn @ 2015-06-19  9:56 UTC [1%]

1686. [Bitcoin-development] Mailman incompatibility with DKIM ...
      - by Warren Togami Jr. @ 2015-06-19  9:51 UTC [1%]

1687. Re: [Bitcoin-development] FYI - Mailing List Move Preparations
      - by Jeff Garzik @ 2015-06-19  5:28 UTC [0%]

1688. Re: [Bitcoin-development] FYI - Mailing List Move Preparations
      - by Warren Togami Jr. @ 2015-06-19  5:02 UTC [0%]

1689. [Bitcoin-development] FYI - Mailing List Move Preparations
      - by Warren Togami Jr. @ 2015-06-19  4:57 UTC [1%]

1690. Re: [Bitcoin-development] soft-fork block size increase (extension blocks)
      - by Richard Moore @ 2015-06-17 16:17 UTC [0%]

1691. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-06-17  9:51 UTC [0%]

1692. Re: [Bitcoin-development] [RFC] Canonical input and output ordering in transactions
      - by Rusty Russell @ 2015-06-16  8:06 UTC [0%]

1693. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Pieter Wuille @ 2015-06-16 19:48 UTC [1%]

1694. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Pieter Wuille @ 2015-06-16 19:25 UTC [1%]

1695. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-06-16 19:22 UTC [1%]

1696. Re: [Bitcoin-development] Reusable payment codes
      - by odinn @ 2015-06-16 16:26 UTC [0%]

1697. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-06-16 12:31 UTC [0%]

1698. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-06-16 12:12 UTC [0%]

1699. Re: [Bitcoin-development] [RFC] Canonical input and output ordering in transactions
      - by Jorge Timón @ 2015-06-16  7:10 UTC [1%]

1700. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Tom Harding @ 2015-06-16  5:26 UTC [0%]

1701. Re: [Bitcoin-development] [RFC] Canonical input and output ordering in transactions
      - by Rusty Russell @ 2015-06-15 21:01 UTC [1%]

1702. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-06-15 11:59 UTC [0%]

1703. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Pieter Wuille @ 2015-06-15 10:00 UTC [0%]

1704. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-06-15  9:21 UTC [1%]

1705. Re: [Bitcoin-development] Proposal: Move Bitcoin Dev List to a Neutral Competent Entity
      - by odinn @ 2015-06-15  9:13 UTC [0%]

1706. Re: [Bitcoin-development] Proposal: Move Bitcoin Dev List to a Neutral Competent Entity
      - by Andy Schroder @ 2015-06-15  5:50 UTC [0%]

1707. Re: [Bitcoin-development] Proposal: Move Bitcoin Dev List to a Neutral Competent Entity
      - by Warren Togami Jr. @ 2015-06-15  3:19 UTC [1%]

1708. Re: [Bitcoin-development] [RFC] Canonical input and output ordering in transactions
      - by Mark Friedenbach @ 2015-06-15  2:47 UTC [1%]

1709. Re: [Bitcoin-development] User vote in blocksize through fees
      - by Eric Lombrozo @ 2015-06-14 20:10 UTC [1%]

1710. Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
      - by Nathan Wilcox @ 2015-06-13 15:38 UTC [0%]

1711. Re: [Bitcoin-development] User vote in blocksize through fees
      - by Vincent Truong @ 2015-06-12 23:01 UTC [1%]

1712. Re: [Bitcoin-development] User vote in blocksize through fees
      - by Eric Lombrozo @ 2015-06-12 20:04 UTC [1%]

1713. Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
      - by Aaron Voisine @ 2015-06-11 18:55 UTC [0%]

1714. Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
      - by Nathan Wilcox @ 2015-06-11 18:30 UTC [0%]

1715. Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
      - by Tom Harding @ 2015-06-11 17:10 UTC [1%]

1716. Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
      - by Troy Benjegerdes @ 2015-06-11  1:46 UTC [0%]

1717. Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
      - by Aaron Voisine @ 2015-06-10 21:18 UTC [0%]

1718. Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
      - by Andy Schroder @ 2015-06-10 20:03 UTC [1%]

1719. Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
      - by Peter Todd @ 2015-06-10 20:03 UTC [0%]

1720. Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
      - by Nathan Wilcox @ 2015-06-10 20:00 UTC [0%]

1721. Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
      - by Jeff Garzik @ 2015-06-10 19:54 UTC [1%]

1722. Re: [Bitcoin-development] Proposal: SPV Fee Discovery mechanism
      - by Aaron Voisine @ 2015-06-10 19:19 UTC [1%]

1723. Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
      - by Andy Schroder @ 2015-06-10 18:59 UTC [0%]

1724. Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
      - by Troy Benjegerdes @ 2015-06-10 18:47 UTC [0%]

1725. Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
      - by Troy Benjegerdes @ 2015-06-10 18:02 UTC [1%]

1726. Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
      - by Andy Schroder @ 2015-06-10 18:41 UTC [0%]

1727. Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
      - by s7r @ 2015-06-10 18:36 UTC [0%]

1728. Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
      - by Ivan Brightly @ 2015-06-10 18:28 UTC [0%]

1729. Re: [Bitcoin-development] Is SourceForge still trustworthy enough to host this list?
      - by Andy Schroder @ 2015-06-10 16:46 UTC [1%]

1730. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Raystonn . @ 2015-06-09 19:03 UTC [1%]

1731. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Gavin Andresen @ 2015-06-09 18:25 UTC [1%]

1732. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Raystonn . @ 2015-06-09 17:52 UTC [1%]

1733. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Tier Nolan @ 2015-06-09 14:18 UTC [1%]

1734. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Gavin Andresen @ 2015-06-09 13:36 UTC [1%]

1735. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Loi Luu @ 2015-06-09  9:33 UTC [1%]

1736. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the blocksize limit
      - by Raystonn . @ 2015-06-08 22:46 UTC [1%]

1737. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Peter Todd @ 2015-06-08 22:28 UTC [1%]

1738. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Peter Todd @ 2015-06-08 22:26 UTC [1%]

1739. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the blocksize limit
      - by Peter Todd @ 2015-06-08 22:18 UTC [1%]

1740. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the blocksize limit
      - by Raystonn . @ 2015-06-08 22:10 UTC [1%]

1741. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the blocksize limit
      - by Btc Drak @ 2015-06-08 22:07 UTC [1%]

1742. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Bob McElrath @ 2015-06-08 22:06 UTC [2%]

1743. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the blocksize limit
      - by Raystonn . @ 2015-06-08 22:01 UTC [1%]

1744. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Peter Todd @ 2015-06-08 21:44 UTC [1%]

1745. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the blocksize limit
      - by Raystonn . @ 2015-06-08 21:40 UTC [1%]

1746. Re: [Bitcoin-development] [RFC] Canonical input and output ordering in transactions
      - by Peter Todd @ 2015-06-08 21:36 UTC [0%]

1747. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Raystonn . @ 2015-06-08 21:33 UTC [1%]

1748. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Peter Todd @ 2015-06-08 21:33 UTC [1%]

1749. Re: [Bitcoin-development] [RFC] Canonical input and output ordering in transactions
      - by Danny Thorpe @ 2015-06-08 21:25 UTC [1%]

1750. Re: [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Raystonn . @ 2015-06-08 21:14 UTC [2%]

1751. [Bitcoin-development] New attack identified and potential solution described: Dropped-transaction spam attack against the block size limit
      - by Raystonn . @ 2015-06-08 20:07 UTC [2%]

1752. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-06-06 16:35 UTC [0%]

1753. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Peter Todd @ 2015-06-06 15:32 UTC [0%]

1754. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Pieter Wuille @ 2015-06-06 15:23 UTC [0%]

1755. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Luke Dashjr @ 2015-06-06 15:18 UTC [1%]

1756. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Pieter Wuille @ 2015-06-06 15:13 UTC [0%]

1757. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-06-06 15:05 UTC [0%]

1758. Re: [Bitcoin-development] BIP for Proof of Payment
      - by Pieter Wuille @ 2015-06-06 14:47 UTC [1%]

1759. [Bitcoin-development] BIP for Proof of Payment
      - by Kalle Rosenbaum @ 2015-06-06 14:35 UTC [1%]

1760. Re: [Bitcoin-development] Max Block Size: Simple Voting Procedure
      - by Stephen Morse @ 2015-06-03  0:30 UTC [0%]

1761. Re: [Bitcoin-development] Max Block Size: Simple Voting Procedure
      - by Matt Whitlock @ 2015-06-02 21:26 UTC [1%]

1762. Re: [Bitcoin-development] DevCore London
      - by Mike Hearn @ 2015-06-02 14:20 UTC [0%]

1763. Re: [Bitcoin-development] soft-fork block size increase (extension blocks)
      - by Tom Harding @ 2015-06-02  0:42 UTC [0%]

1764. Re: [Bitcoin-development] Why do we need a MAX_BLOCK_SIZE at all?
      - by Jim Phillips @ 2015-06-01 20:02 UTC [1%]

1765. Re: [Bitcoin-development] Why do we need a MAX_BLOCK_SIZE at all?
      - by Stephen Morse @ 2015-06-01 19:02 UTC [0%]

1766. [Bitcoin-development] Why do we need a MAX_BLOCK_SIZE at all?
      - by Jim Phillips @ 2015-06-01 18:32 UTC [1%]

1767. Re: [Bitcoin-development] soft-fork block size increase (extension blocks)
      - by Adam Back @ 2015-06-01 17:21 UTC [1%]

1768. [Bitcoin-development] soft-fork block size increase (extension blocks)
      - by Adam Back @ 2015-06-01 15:40 UTC [1%]

1769. [Bitcoin-development] Max Block Size: Simple Voting Procedure
      - by Stephen Morse @ 2015-05-31 19:04 UTC [1%]

1770. Re: [Bitcoin-development] Proposed alternatives to the 20MB step function
      - by Cameron Garnham @ 2015-05-30  1:36 UTC [1%]

1771. Re: [Bitcoin-development] ChainDB Whitepaper
      - by Peter Todd @ 2015-05-20  6:26 UTC [1%]

1772. Re: [Bitcoin-development] Long-term mining incentives
      - by Damian Gomez @ 2015-05-13 17:49 UTC [0%]

1773. Re: [Bitcoin-development] Long-term mining incentives
      - by Tier Nolan @ 2015-05-13 13:28 UTC [1%]

1774. Re: [Bitcoin-development] Long-term mining incentives
      - by Thomas Voegtlin @ 2015-05-13  9:49 UTC [0%]

1775. Re: [Bitcoin-development] Long-term mining incentives
      - by Adam Back @ 2015-05-12 23:48 UTC [0%]

1776. Re: [Bitcoin-development] Long-term mining incentives
      - by Pedro Worcel @ 2015-05-12 21:24 UTC [0%]

1777. [Bitcoin-development] Fwd: Proposed additional options for pruned nodes
      - by Adam Weiss @ 2015-05-12 21:17 UTC [0%]

1778. Re: [Bitcoin-development] Long-term mining incentives
      - by Dave Hudson @ 2015-05-12 16:21 UTC [0%]

1779. Re: [Bitcoin-development] Long-term mining incentives
      - by Gavin Andresen @ 2015-05-12 16:10 UTC [1%]

1780. Re: [Bitcoin-development] A way to create a fee market even without a block size limit (2013)
      - by Stephen @ 2015-05-11  5:31 UTC [0%]

1781. [Bitcoin-development] A way to create a fee market even without a block size limit (2013)
      - by Sergio Lerner @ 2015-05-10 20:45 UTC [1%]

1782. Re: [Bitcoin-development] A suggestion for reducing the size of the UTXO database
      - by Bob McElrath @ 2015-05-10 14:42 UTC [1%]

1783. Re: [Bitcoin-development] A suggestion for reducing the size of the UTXO database
      - by Jim Phillips @ 2015-05-09 21:11 UTC [0%]

1784. Re: [Bitcoin-development] A suggestion for reducing the size of the UTXO database
      - by Pieter Wuille @ 2015-05-09 20:38 UTC [0%]

1785. Re: [Bitcoin-development] Proposed alternatives to the 20MB step function
      - by Joel Joonatan Kaartinen @ 2015-05-08 22:36 UTC [0%]

1786. Re: [Bitcoin-development] Proposed alternatives to the 20MB step function
      - by Peter Todd @ 2015-05-08 16:51 UTC [0%]

1787. Re: [Bitcoin-development] Assurance contracts to fund the network with OP_CHECKLOCKTIMEVERIFY
      - by Peter Todd @ 2015-05-08 16:43 UTC [1%]

1788. Re: [Bitcoin-development] Assurance contracts to fund the network with OP_CHECKLOCKTIMEVERIFY
      - by Tier Nolan @ 2015-05-08 15:03 UTC [1%]

1789. Re: [Bitcoin-development] Proposed alternatives to the 20MB step function
      - by Matt Whitlock @ 2015-05-08 13:24 UTC [0%]

1790. Re: [Bitcoin-development] Proposed alternatives to the 20MB step function
      - by Matt Whitlock @ 2015-05-08 12:48 UTC [0%]

1791. Re: [Bitcoin-development] Proposed alternatives to the 20MB step function
      - by Gavin Andresen @ 2015-05-08 12:48 UTC [0%]

1792. Re: [Bitcoin-development] Proposed alternatives to the 20MB step function
      - by Joel Joonatan Kaartinen @ 2015-05-08 12:32 UTC [1%]

1793. Re: [Bitcoin-development] Block Size Increase
      - by Joel Joonatan Kaartinen @ 2015-05-08  1:51 UTC [1%]

1794. Re: [Bitcoin-development] Block Size Increase
      - by 21E14 @ 2015-05-07 23:05 UTC [0%]

1795. Re: [Bitcoin-development] Block Size Increase
      - by Matt Corallo @ 2015-05-07 21:29 UTC [1%]

1796. Re: [Bitcoin-development] Block Size Increase
      - by Jeff Garzik @ 2015-05-07 19:54 UTC [1%]

1797. Re: [Bitcoin-development] Block Size Increase
      - by Mike Hearn @ 2015-05-07 16:13 UTC [0%]

1798. Re: [Bitcoin-development] Block Size Increase
      - by Jeff Garzik @ 2015-05-07 15:56 UTC [1%]

1799. Re: [Bitcoin-development] Block Size Increase
      - by Peter Todd @ 2015-05-07 14:32 UTC [0%]

1800. Re: [Bitcoin-development] Block Size Increase
      - by Jeff Garzik @ 2015-05-07 14:04 UTC [1%]


Results 1601-1800 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