{"type":"rich","version":"1.0","author_name":"npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","author_url":"https://nostr.ae/npub1kf0ppcjaguxekg24yx6smgxlu73qn0k8lm0t2wrqc0scpl7u3sgsmf3f58","provider_name":"njump","provider_url":"https://nostr.ae","html":"📅 Original date posted:2013-12-02\n📝 Original message:On Mon, Dec 2, 2013 at 9:33 AM, Mike Hearn \u003cmike at plan99.net\u003e wrote:\n\u003e \"The payment protocol at least would need some notion of fee, or possibly\n\u003e (better?) the ability for a recipient to specify some inputs as well as some\n\u003e outputs.\"\n\n\u003cvendor hat: on\u003e\n\nBitPay noticed this detail last week.  We were noticing that some\ntransactions were not even reaching our bitcoind border routers (edge\nnodes), due to low/no fees.  That led to a long discussion of all\nthings fee-related.  SPV fees are a big issue.  Getting\nchild-pays-for-parent in some form out to miners is another.  Getting\na smart, dynamic fee market Gavin mentions is a big need.\n\n-- \nJeff Garzik\nBitcoin core developer and open source evangelist\nBitPay, Inc.      https://bitpay.com/"}
