Are the low fees due to a drop in popularity and usage or is it due to more segwit implementation? As far as I'm aware lightning is still on test net
The low fee is due to empty memepool which means more people are holding their bitcoins because they know what the holding will give us later.And segwit also the reason for the low traffic since many exchanges started to use segwit for their transaction and coinbase also going to implement the segwit soon so we can expect more cheaper transaction fee soon. 
Topic: Will these low transaction fees and times last?? (Read 426 times)
On a very basic level, I think the recent fee drops are as a result of the way bitcoin and other coins have not been performing well, especially in the last 4-6 weeks. If they kept the fees, it would be harder for individuals to keep making transactions as they would be experiencing more loss; thus, if no transactions exchanges don't get their cut (fees/commissions/etc). You can expect fees to climb back up when bitcoin prices go back up. However, if I were an excahnge, I'll still keep it low to be very competitive.
we need to increase the capacity and increasing the blocksize is not the only way of doing that. for starters SegWit is increasing the capacity. there are also other solutions such as signature aggregation and schnorr,... that can increase the capacity in the future. we may eventually increase the blocksize also but it seems to me that is a long ways down the line.
as for LN, from what i see, the way it can help scaling is that it has the potential to move a large number of transactions out of blockchain. for example imagine all the major exchanges (coinbase, kraken, bitfinex, bitstamp, poloniex, binance) started using LN, blocks may become mostly empty in that case and you don't need to open and close channels each time you make a transaction.
as for LN, from what i see, the way it can help scaling is that it has the potential to move a large number of transactions out of blockchain. for example imagine all the major exchanges (coinbase, kraken, bitfinex, bitstamp, poloniex, binance) started using LN, blocks may become mostly empty in that case and you don't need to open and close channels each time you make a transaction.
You're right. I mentioned the need to increase the blocksize assuming that millions of people would start using Bitcoin in the next few years. It would be great to see major exchanges using the Lightning Network, but years will pass before it happens. It took quite a long time for some exchanges to implement SegWit. Not to mention that they still charge enormous fees for withdrawals (I understand that maintaining a huge exchange is costly, but it's not a reason to rip-off your clients). Actually, I thought that exchanges would stick to on-chain transactions to avoid cheating. They will be able to run their LN nodes 24/7, anyway.
~
Lightning Network still requires broadcasting transactions to the network when you want to open a channel or close and old onel. That's why some people say that we will have to increase the blocksize anyway. Lightning Network is still not widely used among merchants so I don't think that is the reason of low transaction fees. It looks like batching and growing SegWit adoption does the good job of off-loading the load.
Lightning Network still requires broadcasting transactions to the network when you want to open a channel or close and old onel. That's why some people say that we will have to increase the blocksize anyway. Lightning Network is still not widely used among merchants so I don't think that is the reason of low transaction fees. It looks like batching and growing SegWit adoption does the good job of off-loading the load.
we need to increase the capacity and increasing the blocksize is not the only way of doing that. for starters SegWit is increasing the capacity. there are also other solutions such as signature aggregation and schnorr,... that can increase the capacity in the future. we may eventually increase the blocksize also but it seems to me that is a long ways down the line.
as for LN, from what i see, the way it can help scaling is that it has the potential to move a large number of transactions out of blockchain. for example imagine all the major exchanges (coinbase, kraken, bitfinex, bitstamp, poloniex, binance) started using LN, blocks may become mostly empty in that case and you don't need to open and close channels each time you make a transaction.
There is still a plan to increase the blocks in the future?
I would guess that it is happening because of competition, so I guess you could say because of popularity.
Just enjoy it, it will last
. I think maybe one day we will be looking at no transaction fees.
Just enjoy it, it will last
. I think maybe one day we will be looking at no transaction fees. I believe the low transaction fee is where to stay because most of exchange/wallet are now supporting SegWit, we also have the Lightning though it was still test net mode and we also have the Global CryptoCurrency coin which can use to make day to day transaction and micro payment.
Lightning Network still requires broadcasting transactions to the network when you want to open a channel or close and old onel. That's why some people say that we will have to increase the blocksize anyway. Lightning Network is still not widely used among merchants so I don't think that is the reason of low transaction fees. It looks like batching and growing SegWit adoption does the good job of off-loading the load.
I believe the low transaction fee is where to stay because most of exchange/wallet are now supporting SegWit, we also have the Lightning though it was still test net mode and we also have the Global CryptoCurrency coin which can use to make day to day transaction and micro payment.
I really hope the low fees last, BTC is actually doing well lately to keep up with demand.
Time will tell.
Time will tell.
hero member
Activity: 2660
Merit: 651
Want top-notch marketing for your project, Hire me
Are the low fees due to a drop in popularity and usage or is it due to more segwit implementation? As far as I'm aware lightning is still on test net
The lightning or the SegWit are the cause of the low in transaction fee and the reason behind it is the no transaction congestion i.e the bitcoin transaction per seconds is not like the huge traffic time. 
While there was a short maintenance of coinbase server the transaction count dropped heavily.
As soon as the maintenance was done, the transaction count increased instantly again.
The network did not recover. Their server were down for a short amount of time only.
This was not intentionally spammed. Coinbase did not batch transactions. They sent out every withdrawal in its own transaction.
Now they have started batching transactions which reduces the privacy a bit. But on the other hand they are saving a massive amount of TX fees.
Thanks to batching + segwit the amount of transactions in the mempool is clearly lower.
As soon as the maintenance was done, the transaction count increased instantly again.
The network did not recover. Their server were down for a short amount of time only.
This was not intentionally spammed. Coinbase did not batch transactions. They sent out every withdrawal in its own transaction.
Now they have started batching transactions which reduces the privacy a bit. But on the other hand they are saving a massive amount of TX fees.
Thanks to batching + segwit the amount of transactions in the mempool is clearly lower.
i knew they were implementing segwit, i didn't know they were batching as well. batching is much more important than segwit for reducing fees.
i'm finding it kinda strange how slow some of these places are to stay on the ball with their behavior. i'm not sure i've seen any mention of segwit or batching from gemini and they're supposed to be the fanciest kid in town.
I thought it was discovered that coinbase was 'spamming' after they went down for a while and the network immediately recovered.
While there was a short maintenance of coinbase server the transaction count dropped heavily.
As soon as the maintenance was done, the transaction count increased instantly again.
The network did not recover. Their server were down for a short amount of time only.
This was not intentionally spammed. Coinbase did not batch transactions. They sent out every withdrawal in its own transaction.
Now they have started batching transactions which reduces the privacy a bit. But on the other hand they are saving a massive amount of TX fees.
Thanks to batching + segwit the amount of transactions in the mempool is clearly lower.
I thought it was discovered that coinbase was 'spamming' after they went down for a while and the network immediately recovered.
I remember seeing all kinds of fancy theories that often added up to a cost of millions per day when coinbase laziness and stupidity adds up and makes sense.
For bitcoin's future health these low fees aren't sustainable so enjoy while you can.
I remember seeing all kinds of fancy theories that often added up to a cost of millions per day when coinbase laziness and stupidity adds up and makes sense.
For bitcoin's future health these low fees aren't sustainable so enjoy while you can.
Have you tried using any of those free transaction accelerating services like viabtc and save yourself the stress of waiting hours?
i wasnt using wallets. transaction is between two trading exchanges.Using an accelerating service is completely undependent from the sending/receiving wallet.
A transaction accelerator will give your TX a higher priority (for the miner you have paid).
The next block this miner will mine will include your transaction.
Did you check the transaction on a block explorer? How low is the fee set?
It is hard to imagine that a TX doesn't confirm for a long amount of time when looking at the mempool.
Average fees to get a transaction included into the next block are at <20 sat/B currently.
Quote
Will these low transaction fees and times last??
no, bitcoin still sucks.
i sent from bitstamp to bibox. bitstamp has set fees to low so now im stuck, as it is everyone else at the same transaction. it has been hours.
i dont know if they set fees manually or they dont give a f**k.
and i know its not directly bitcoins fault but it reflects poorly on bitcoin.
But how it can get stuck?
Because the transaction will get confirmed even with 1 sat/byte in minutes since the memepool is empty,so you need to contact the service ans support team of your exchange to get the problem resolved.
Do you have any of these academic papers online or links to mentions of them?
https://link.springer.com/chapter/10.1007/978-3-662-53357-4_1
i couldn't find the direct download link for this so i had to upload the PDF i had on my computer: https://www.dropbox.com/s/vdmi6diqo9apqb6/Bitcoin%20Stress%20Testing%2C%20Khaled%20Baqer.pdf?dl=0
Quote
Will these low transaction fees and times last??
no, bitcoin still sucks.
i sent from bitstamp to bibox. bitstamp has set fees to low so now im stuck, as it is everyone else at the same transaction. it has been hours.
i dont know if they set fees manually or they dont give a f**k.
and i know its not directly bitcoins fault but it reflects poorly on bitcoin.
Quote
Will these low transaction fees and times last??
no, bitcoin still sucks.
i sent from bitstamp to bibox. bitstamp has set fees to low so now im stuck, as it is everyone else at the same transaction. it has been hours.
i dont know if they set fees manually or they dont give a f**k.
and i know its not directly bitcoins fault but it reflects poorly on bitcoin.
Quote
Will these low transaction fees and times last??
no, bitcoin still sucks.
i sent from bitstamp to bibox. bitstamp has set fees to low so now im stuck, as it is everyone else at the same transaction. it has been hours.
i dont know if they set fees manually or they dont give a f**k.
and i know its not directly bitcoins fault but it reflects poorly on bitcoin.
there has been many spam attacks against bitcoin, some were more obvious than others and it has been happening for at least 3 years now, incidentally near the same time scaling debate started back in mid 2015.
the oldest one that i know of is the following one which led to some academic papers being written!
the oldest one that i know of is the following one which led to some academic papers being written!
a little bit of history!
the oldest massive scale spam attack that i can remember was called "stress test" back in Aug and Sep 2015 where they started sending transaction with 0.0001BTC and 0.0001BTC fixed fee. then to make matters worse they started releasing the private keys of the addresses involved. soon there were hundreds of people with access to these keys and hundreds of transactions spending the same outputs.
https://bitcointalksearch.org/user/coinwalleteu-553487
interestingly enough, this method of spam attack is still being used. 1BoatSLRHtKNngkdXEeobR76b53LETtpyT is a well known bitcoin address used in vanitygen with a publicly known private key.
the oldest massive scale spam attack that i can remember was called "stress test" back in Aug and Sep 2015 where they started sending transaction with 0.0001BTC and 0.0001BTC fixed fee. then to make matters worse they started releasing the private keys of the addresses involved. soon there were hundreds of people with access to these keys and hundreds of transactions spending the same outputs.
https://bitcointalksearch.org/user/coinwalleteu-553487
interestingly enough, this method of spam attack is still being used. 1BoatSLRHtKNngkdXEeobR76b53LETtpyT is a well known bitcoin address used in vanitygen with a publicly known private key.
Thanks for this bite of history! Funny that if those fixed fees now are actually really still being used, they'd be many times more the average fee I've been spending these past weeks. Do you have any of these academic papers online or links to mentions of them? The link you gave is just your post history.
That address still has recent txs too... amazing.
Sometimes you think it's a waste of money, but these guys probably obtained all those coins a long time ago, or couldn't spend it without risk of being traced... and if you think of the "success" of the forkcoins later on, I suppose it made it all worthwhile.
Jump to: