Pages:
Author

Topic: Are we stress testing again? - page 29. (Read 33192 times)

legendary
Activity: 1372
Merit: 1252
July 06, 2015, 07:02:35 PM
#39

I don't personally think so. I just did a transaction and I quickly had 3 confirmations (as seen in blockchain.info). Your post was 1 day tho so who knows.
legendary
Activity: 910
Merit: 1000
July 06, 2015, 06:16:32 PM
#38
But there paying tx fees so miners are happy to put them through?
legendary
Activity: 1176
Merit: 1011
July 06, 2015, 06:15:40 PM
#37
What could be the possible solution for this. Cant this spamming stopped somehow?
Nodes should filter out dust transactions.
full member
Activity: 168
Merit: 100
http://pachinko.games-bit.com/
July 06, 2015, 06:10:01 PM
#36
What could be the possible solution for this. Cant this spamming stopped somehow?
legendary
Activity: 1274
Merit: 1000
July 06, 2015, 06:07:23 PM
#35
and this is the worst time to clog up the system because new adopters won't understand that it isn't business as usual. 

Quite the contrary, if you want attention this is the best time to get it, when everyone is looking.

Bigger blocks can be filled up with dust transactions just as easily.
legendary
Activity: 910
Merit: 1000
July 06, 2015, 06:03:56 PM
#34
172,000 transactions in last 24 hours.  A record.  Over 200k soon?  Sounds like they should of solved the block size increase issue weeks ago rather then arguing about it.
legendary
Activity: 1722
Merit: 1000
Satoshi is rolling in his grave. #bitcoin
July 06, 2015, 05:39:27 PM
#33
Well i just received a transaction without any issue, but i see that unconfirmed transactions are at 10 000, and mempool at 12 MB tho.
Don't know if the bigger block sizes only are the solution to this problem, but something definitely needs to be done, because if there's a lot of people that cant get their transactions confirmed, it's looking bad.

cheers
legendary
Activity: 1806
Merit: 1024
July 06, 2015, 05:29:48 PM
#32
I guess a bigger block mb size will help in cases like this, is stress testing really a good way to point out to others that bitcoin needs bigger size blocks, then it comes the dilemma of miner saying one size and core developers an other.

uhhmm NO.  bigger blocks has nothing to do with this. 

if you want to send out dust (not sure why you would) you shouldn't expect it to be confirmed right away or at all.

bigger blocks can be filled just as fast with spam transactions as it doesn't cost much of anything.  filling 20mb blocks will cause problems with nodes not getting blocks synced.

regular transactions are NOT affected.

Yes, the costs for scaling the "block-filling-attack" are minimal for any serious attacker. In fact, what these stupid stress tests prove is that 1) there is no serious problem for non-dust transactions and 2) the (non-existent) problem would certainly not be solved by increasing the max-blocksize.

The only real solution is a healthy fee market. I had no problems getting my tx confirmed - just don't send dust and pay an adequate fee and you'll be fine. Dust transactions can happen on sidechains or off-chain. These transaction do not require the same level of security as ordinary transactions.

ya.ya.yo!
legendary
Activity: 2450
Merit: 1002
July 06, 2015, 05:06:03 PM
#31
I guess a bigger block mb size will help in cases like this, is stress testing really a good way to point out to others that bitcoin needs bigger size blocks, then it comes the dilemma of miner saying one size and core developers an other.

uhhmm NO.  bigger blocks has nothing to do with this. 

if you want to send out dust (not sure why you would) you shouldn't expect it to be confirmed right away or at all.

bigger blocks can be filled just as fast with spam transactions as it doesn't cost much of anything.  filling 20mb blocks will cause problems with nodes not getting blocks synced.

regular transactions are NOT affected.

I think u missed the point of the stress tests, well the only way I can figure ... is to prove that if this were to become bitcoin's normal tx rate anytime, then the blocksize would need to be made larger. Because a constant tx rate of over just 7 tx/s I think?? will cause all sorts of tx confirmation delays at the current blocksize limitation.
sr. member
Activity: 326
Merit: 250
July 06, 2015, 05:03:52 PM
#30
The whole of blockchain seems pretty stressed.... made a transaction from bitreserve this morning and it is still not even showing on blockchain.info... the funny thing is I made a transaction during last week stress too lol.. getting used to it now.. but buying a lot of litecoin as well... i think its looking like a good option now

I sent something from an exchange about four hours ago and it's been showing on blockchain.info for hours. The only problem is it's still unconfirmed. I think we'll be lucky if our transactions get confirmed by tomorrow. The stress testers are learning how to do more damage from each test.
tss
hero member
Activity: 742
Merit: 500
July 06, 2015, 05:03:25 PM
#29
I guess a bigger block mb size will help in cases like this, is stress testing really a good way to point out to others that bitcoin needs bigger size blocks, then it comes the dilemma of miner saying one size and core developers an other.

uhhmm NO.  bigger blocks has nothing to do with this. 

if you want to send out dust (not sure why you would) you shouldn't expect it to be confirmed right away or at all.

bigger blocks can be filled just as fast with spam transactions as it doesn't cost much of anything.  filling 20mb blocks will cause problems with nodes not getting blocks synced.

regular transactions are NOT affected.
hero member
Activity: 686
Merit: 500
July 06, 2015, 04:50:59 PM
#28
I guess a bigger block mb size will help in cases like this, is stress testing really a good way to point out to others that bitcoin needs bigger size blocks, then it comes the dilemma of miner saying one size and core developers an other.
full member
Activity: 257
Merit: 100
July 06, 2015, 04:42:33 PM
#27
The whole of blockchain seems pretty stressed.... made a transaction from bitreserve this morning and it is still not even showing on blockchain.info... the funny thing is I made a transaction during last week stress too lol.. getting used to it now.. but buying a lot of litecoin as well... i think its looking like a good option now
hero member
Activity: 672
Merit: 500
July 06, 2015, 04:18:23 PM
#26

I got the hex of your transaction and try to push it to the network from blockchain.info. Received this error:
"The Maximum number of outputs in a single transaction is 200"

Look at your transaction on another explorer:
https://www.blocktrail.com/BTC/tx/0c6429646bfe986c4d34d72f6592632cbbf0b6b890c42cb23ef06ba6456c1123
It has 8 inputs and 238 outputs.

The problem is the size, miners don't like large transactions with just enough fees. I estimated the transaction size to be 9.6kb, so your 0.0011btc fee should be enough. Just wait it out. It should confirm when there are less transactions in the mempool. The transaction is 8btc, so it's priority will shoot up in a few hours.

Why did you put all 238 outputs in 1 transaction? I think it would be easier to confirm if you split it into 3 to 4 smaller transactions.
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
July 06, 2015, 04:17:22 PM
#25
So the solution is more node's or miners?

Bigger blocks. More miners will not make finding blocks faster as difficulty adjusts and more nodes will do nothing at all to reduce the number of unconfirmed transactions, they will just help relay them (and blocks).

Bummer.  Why are they testing again, didn't they prove their point the first time around?  Maybe it is a different entity this time, but the timing is horrible.  With the Greece thing BTC is getting some nice press, and this is the worst time to clog up the system because new adopters won't understand that it isn't business as usual.  So the experiment proved pretty much what it intended to prove:  if you muck up the network, then it gets mucked up!

IIRC both tests failed.
legendary
Activity: 2940
Merit: 1865
July 06, 2015, 04:14:19 PM
#24
...

Yes, and it looks like they are still at it.  Below address is one of a long chain of about $49.21, all but one with value of $0.00:

https://blockchain.info/address/1Lc8DpFMWC2Ze33Wj2tpwjqFrBP4s9LjLH

*   *   *

I have not seen this before.  Does anyone else have a similar experience to share?  

Confirmation times of hours is unacceptable.

It would be very interesting to learn who is responsible...
sr. member
Activity: 378
Merit: 257
July 06, 2015, 04:13:33 PM
#23
Bummer.  Why are they testing again, didn't they prove their point the first time around?  Maybe it is a different entity this time, but the timing is horrible.  With the Greece thing BTC is getting some nice press, and this is the worst time to clog up the system because new adopters won't understand that it isn't business as usual.  So the experiment proved pretty much what it intended to prove:  if you muck up the network, then it gets mucked up!
legendary
Activity: 1512
Merit: 1012
July 06, 2015, 04:10:59 PM
#22
13Mb of unconfirmed ...

https://blockchain.info/unconfirmed-transactions

 Grin they really want the block liberation ...
sr. member
Activity: 353
Merit: 250
Zichain
July 06, 2015, 04:10:48 PM
#21
Weird stuff going on .
https://www.blocktrail.com/BTC/tx/0c6429646bfe986c4d34d72f6592632cbbf0b6b890c42cb23ef06ba6456c1123

Never had this message on BlockTrail , there is no "High Priority" message : Priority :   28,751,614 < 28,800,000

Quote
10,000,000    *    374    =    3,740,000,000
10,000,000    *    380    =    3,800,000,000
20,000,000    *    378    =    7,560,000,000
20,000,000    *    381    =    7,620,000,000
10,010,000    *    386    =    3,863,860,000
300,000,000    *    380    =    114,000,000,000
30,730,793    *    377    =    11,585,508,961
400,000,000    *    371    =    148,400,000,000
   300,569,368,961 age
300,569,368,961    /    10 kB    =    28,751,614 priority
required for high priority; 28,800,000

sr. member
Activity: 326
Merit: 250
July 06, 2015, 04:09:55 PM
#20
I'm having the same problem. I withdrew from an exchange and couldn't tell them how much in transaction fees I wanted to pay. If I had known in advance I would have paid far more in fees to get my transaction processed fast. Blockchain.info said this every time I have checked for hours now.

Estimated Confirmation Time: Within 6 Blocks (Medium Priority)
Pages:
Jump to: