📅 Original date posted:2017-12-21
📝 Original message:It seems that the exchanges are doing everything that they can to slow things. Not only have the major exchanges not implemented segwit yet, but a bigger, less addressed issue is that they have start applying transfer limits on crypto as well as cash. They do not respond for months to requests to upgrade limits, and this results in many transactions instead of one to transfer crypto to cold storage devices.
These issues may self-resolve over time, since I think they are all impacted by KYC and the explosive growth.
From: bitcoin-dev-bounces at lists.linuxfoundation.org [mailto:bitcoin-dev-bounces at lists.linuxfoundation.org] On Behalf Of Jameson Lopp via bitcoin-dev
Sent: Thursday, December 21, 2017 1:03 PM
To: Melvin Carvalho <melvincarvalho at gmail.com>; Bitcoin Protocol Discussion <bitcoin-dev at lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Total fees have almost crossed the block reward
I'd hope that the incentives are in place to encourage high volume senders to be more efficient in their use of block space by batching transactions and implementing SegWit, though this may not be the case for providers that pass transaction fees along to their users.
We've been trying to be more proactive about outreach regarding efficient use of block space to our own customers at BitGo - when we break down the cost savings of implementing a new technique, it generally helps to hasten their adoption. I suspect that in many cases this is an issue of education - we should be more proactive in calling out inefficient uses of block space.
Good resources to bookmark and share:
https://bitcointechtalk.com/saving-up-to-80-on-bitcoin-transaction-fees-by-batching-payments-4147ab7009fb
https://blog.zebpay.com/how-zebpay-reduced-bitcoin-transaction-fees-a9e24c788598
- Jameson
On Thu, Dec 21, 2017 at 4:30 PM, Melvin Carvalho via bitcoin-dev <bitcoin-dev at lists.linuxfoundation.org <mailto:bitcoin-dev at lists.linuxfoundation.org> > wrote:
I asked adam back at hcpp how the block chain would be secured in the long term, once the reward goes away. The base idea has always been that fees would replace the block reward.
At that time fees were approximately 10% of the block reward, but have now reached 45%, with 50% potentially being crossed soon
https://fork.lol/reward/feepct
While this bodes well for the long term security of the coin, I think there is some legitimate concern that the fee per tx is prohibitive for some use cases, at this point in the adoption curve.
Observations of segwit adoption show around 10% at this point
http://segwit.party/charts/
Watching the mempool shows that the congestion is at a peak, though it's quite possible this will come down over the long weekend. I wonder if this is of concern to some.
https://dedi.jochen-hoenicke.de/queue/more/#24h
I thought these data points may be of interest and are mainly FYI. Though if further discussion is deemed appropriate, it would be interesting to hear thoughts.
_______________________________________________
bitcoin-dev mailing list
bitcoin-dev at lists.linuxfoundation.org <mailto:bitcoin-dev at lists.linuxfoundation.org>
https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171221/08b9c9a0/attachment.html>;
Jim Rogers [ARCHIVE] /
npub15t…sf4vm
2023-06-07 18:08:58
in reply to nevent1q…49ez
Author Public Key
npub15tp99z535a8nr8229gwj4r37fe74ppxv227w8sq24mjj84nd5rgs6sf4vmSeen on
wss://relay.nostr.bandPublished at
2023-06-07 18:08:58Event JSON
{
"id": "4499e91829f0609c2f191392711225a69d2344ed7b3c16cdbfe2066dafb027de",
"pubkey": "a2c2528a91a74f319d4a2a1d2a8e3e4e7d5084cc52bce3c00aaee523d66da0d1",
"created_at": 1686161338,
"kind": 1,
"tags": [
[
"e",
"48c41c7539aa5fc716622ee4d3d2a0098787009ed58de994ebf05a477cd5807b",
"",
"root"
],
[
"e",
"b10036d411f6aacb1f036a085c70ccd088d92f8e9f2f34a0a6e619c659c6fe5e",
"",
"reply"
],
[
"p",
"45d091c7bcdbb8674dc8b91c60f7323053ab1432c4c882fd2d9897fe502eebed"
]
],
"content": "📅 Original date posted:2017-12-21\n📝 Original message:It seems that the exchanges are doing everything that they can to slow things. Not only have the major exchanges not implemented segwit yet, but a bigger, less addressed issue is that they have start applying transfer limits on crypto as well as cash. They do not respond for months to requests to upgrade limits, and this results in many transactions instead of one to transfer crypto to cold storage devices. \n\n \n\nThese issues may self-resolve over time, since I think they are all impacted by KYC and the explosive growth. \n\n \n\n \n\nFrom: bitcoin-dev-bounces at lists.linuxfoundation.org [mailto:bitcoin-dev-bounces at lists.linuxfoundation.org] On Behalf Of Jameson Lopp via bitcoin-dev\nSent: Thursday, December 21, 2017 1:03 PM\nTo: Melvin Carvalho \u003cmelvincarvalho at gmail.com\u003e; Bitcoin Protocol Discussion \u003cbitcoin-dev at lists.linuxfoundation.org\u003e\nSubject: Re: [bitcoin-dev] Total fees have almost crossed the block reward\n\n \n\nI'd hope that the incentives are in place to encourage high volume senders to be more efficient in their use of block space by batching transactions and implementing SegWit, though this may not be the case for providers that pass transaction fees along to their users.\n\n \n\nWe've been trying to be more proactive about outreach regarding efficient use of block space to our own customers at BitGo - when we break down the cost savings of implementing a new technique, it generally helps to hasten their adoption. I suspect that in many cases this is an issue of education - we should be more proactive in calling out inefficient uses of block space.\n\n \n\nGood resources to bookmark and share:\n\n \n\nhttps://bitcointechtalk.com/saving-up-to-80-on-bitcoin-transaction-fees-by-batching-payments-4147ab7009fb\n\n \n\nhttps://blog.zebpay.com/how-zebpay-reduced-bitcoin-transaction-fees-a9e24c788598\n\n \n\n- Jameson\n\n \n\nOn Thu, Dec 21, 2017 at 4:30 PM, Melvin Carvalho via bitcoin-dev \u003cbitcoin-dev at lists.linuxfoundation.org \u003cmailto:bitcoin-dev at lists.linuxfoundation.org\u003e \u003e wrote:\n\nI asked adam back at hcpp how the block chain would be secured in the long term, once the reward goes away. The base idea has always been that fees would replace the block reward.\n\nAt that time fees were approximately 10% of the block reward, but have now reached 45%, with 50% potentially being crossed soon\n\nhttps://fork.lol/reward/feepct\n\nWhile this bodes well for the long term security of the coin, I think there is some legitimate concern that the fee per tx is prohibitive for some use cases, at this point in the adoption curve.\n\nObservations of segwit adoption show around 10% at this point\n\nhttp://segwit.party/charts/\n\nWatching the mempool shows that the congestion is at a peak, though it's quite possible this will come down over the long weekend. I wonder if this is of concern to some.\n\nhttps://dedi.jochen-hoenicke.de/queue/more/#24h\n\nI thought these data points may be of interest and are mainly FYI. Though if further discussion is deemed appropriate, it would be interesting to hear thoughts.\n\n\n_______________________________________________\nbitcoin-dev mailing list\nbitcoin-dev at lists.linuxfoundation.org \u003cmailto:bitcoin-dev at lists.linuxfoundation.org\u003e \nhttps://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev\n\n \n\n-------------- next part --------------\nAn HTML attachment was scrubbed...\nURL: \u003chttp://lists.linuxfoundation.org/pipermail/bitcoin-dev/attachments/20171221/08b9c9a0/attachment.html\u003e",
"sig": "033007ad595a18df675dfea15e5a0709ef80433e0fbc4d35e460cefd718c415c02b57870104cc7b50122fe8358cfbfe6fb28912fd342c15de8f285adff015eb6"
}