Bitcoin Forum
November 22, 2026, 03:35:20 AM *
News: Latest Bitcoin Core release: 32.1 [Torrent]
 
   Home   Help Search Login Register More  
Poll
Question: Will you support Gavin's new block size limit hard fork of 8MB by January 1, 2016 then doubling every 2 years?
1.  yes
2.  no

Pages: « 1 ... 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 [1356] 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 ... 1557 »
  Print  
Author Topic: Gold collapsing. Bitcoin UP.  (Read 2032359 times)
cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 22, 2015, 10:09:29 PM
 #27101

network is keeping up with unconf tx's not too bad at 7500
cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 22, 2015, 10:11:21 PM
 #27102

my nodes having no trouble keeping up with memory and no signs of crashing.
justusranvier
Legendary
*
Offline

Activity: 1400
Merit: 1069



View Profile
June 22, 2015, 10:12:33 PM
 #27103

I think it was 100% necessary to get it going, but just thinking about the 50% cut every 4 years that's like quitting hard drugs cold turkey, it not like any business invests in new infrastructure with a guaranteed 50% cut in income is a great business to get into even if you can price it in.

to be honest I was even a little apprehensive at the first halving, I thought it would be too much of a shock, I kept mining only because the price went up, all in all there are lots of well balanced incentives and while I've fantasized how my ideal alt would work I learn why something is the way it is.
If I thought it was worth going through the argument, I'd be in favor of a protocol change to make the block reward shrink a little bit each block instead of suddenly dropping by half every four years.

Really though it's only the first 3-4 block reward halvings that we need to worry about. After that it should be small enough to not matter any more.
Odalv
Legendary
*
Offline

Activity: 1414
Merit: 1000



View Profile
June 22, 2015, 10:14:02 PM
 #27104

Only full nodes need to verify everything.  Not every user needs to run a full node.  

Why do so many people equate users with full nodes?

b/c you will not know if last 5(or 100) full nodes are cheating. ... you will have to trust them blindly like a sheep. :-)

It is easy to do not verify if you know that everybody can verify.

but .... if only "few" people have resources to verify ... and even less will spend(risk) resources to verify then who knows if blockchain is still valid ?

If you are pool miner who only create hashes and is not verifying blocks then cartel of pool owner can create bitcoins out of thin air. (and nobody will notice until it is late)
TPTB_need_war
Sr. Member
****
Offline

Activity: 420
Merit: 262


View Profile
June 22, 2015, 10:14:51 PM
Last edit: June 22, 2015, 10:33:04 PM by TPTB_need_war
 #27105

Cyführer,

My dedication to you(r) high(ney)ness...

https://www.youtube.com/watch?v=tAhp17Mp7Xs

The key distinction between wannabes and the real deal is the latter make it appear to be effortless and the former believe it is...

https://www.youtube.com/watch?v=PH8nTfxwByY

https://www.youtube.com/watch?v=x7-bI8dj_sk

https://www.youtube.com/watch?v=A9ZaudNTSeQ

Odalv
Legendary
*
Offline

Activity: 1414
Merit: 1000



View Profile
June 22, 2015, 10:16:03 PM
Last edit: June 22, 2015, 10:42:35 PM by Odalv
 #27106

my nodes having no trouble keeping up with memory and no signs of crashing.

increase load 20x and you will see what is chaos.

edit:
it is 1 MB block size limit what keeps your nodes happy. :-)
Erdogan
Legendary
*
Offline

Activity: 1512
Merit: 1005



View Profile
June 22, 2015, 10:50:27 PM
 #27107

my nodes having no trouble keeping up with memory and no signs of crashing.

increase load 20x and you will see what is chaos.

edit:
it is 1 MB block size limit what keeps your nodes happy. :-)

Yes, the test demonstrates, if anything, that hell does not break lose when transaction pressure exceeds the limit. So it is not critical that the increase happens at any specific point. What we still don't know, is what happens when real people really want transactions to go through, and when the pressure keeps up over weeks. I think there is time to do it calmly.
Odalv
Legendary
*
Offline

Activity: 1414
Merit: 1000



View Profile
June 22, 2015, 10:59:33 PM
 #27108

my nodes having no trouble keeping up with memory and no signs of crashing.

increase load 20x and you will see what is chaos.

edit:
it is 1 MB block size limit what keeps your nodes happy. :-)

Yes, the test demonstrates, if anything, that hell does not break lose when transaction pressure exceeds the limit. So it is not critical that the increase happens at any specific point. What we still don't know, is what happens when real people really want transactions to go through, and when the pressure keeps up over weeks. I think there is time to do it calmly.


This test demonstrates that cypherdoc's resources are at 25-45% of its capacity. And if we increase block size 8x then he can process only 2-4 MB blocks and his nodes will collapse.
TPTB_need_war
Sr. Member
****
Offline

Activity: 420
Merit: 262


View Profile
June 22, 2015, 11:05:04 PM
 #27109

my nodes

The vested interest.

This is why I hate PoW mining as an economically significant paradigm.

ASIC hardware can't be repurposed.

I designed a far superior ASIC-resistant hash (meaning leverage the ASIC inside the CPU) than Monero's but I was still reticent because it is not sufficient to deal with that paradigmatic flaw, but then suddenly ugghh the epiphany and the rest is history waiting to be made.

cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 22, 2015, 11:14:50 PM
 #27110

my nodes having no trouble keeping up with memory and no signs of crashing.

increase load 20x and you will see what is chaos.

edit:
it is 1 MB block size limit what keeps your nodes happy. :-)

Yes, the test demonstrates, if anything, that hell does not break lose when transaction pressure exceeds the limit. So it is not critical that the increase happens at any specific point. What we still don't know, is what happens when real people really want transactions to go through, and when the pressure keeps up over weeks. I think there is time to do it calmly.


This test demonstrates that cypherdoc's resources are at 25-45% of its capacity. And if we increase block size 8x then he can process only 2-4 MB blocks and his nodes will collapse.

nobody is expecting to not have to increase their full node capacity upon 8MB block sizes.  that's the price to pay to bring in new users.  as new users come in, more merchants will be born and host their own full nodes.   that's what we have been talking about as the network moves to more specialized full nodes.
cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 22, 2015, 11:16:33 PM
 #27111

unconf tx's are still only at 6400
cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 22, 2015, 11:18:04 PM
 #27112

fee rate dropping again:

cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 22, 2015, 11:29:27 PM
 #27113

my nodes having no trouble keeping up with memory and no signs of crashing.

increase load 20x and you will see what is chaos.

edit:
it is 1 MB block size limit what keeps your nodes happy. :-)

Yes, the test demonstrates, if anything, that hell does not break lose when transaction pressure exceeds the limit. So it is not critical that the increase happens at any specific point. What we still don't know, is what happens when real people really want transactions to go through, and when the pressure keeps up over weeks. I think there is time to do it calmly.


This test demonstrates that cypherdoc's resources are at 25-45% of its capacity. And if we increase block size 8x then he can process only 2-4 MB blocks and his nodes will collapse.

no, my higher memory usage is coming from higher than normal unconf tx's.  the UTXO set is relatively flat at around 7MiB.  with bigger blocks, the unconf tx's could be cleared out much faster in bigger chunks.
Erdogan
Legendary
*
Offline

Activity: 1512
Merit: 1005



View Profile
June 22, 2015, 11:30:48 PM
 #27114

my nodes having no trouble keeping up with memory and no signs of crashing.

increase load 20x and you will see what is chaos.

edit:
it is 1 MB block size limit what keeps your nodes happy. :-)

Yes, the test demonstrates, if anything, that hell does not break lose when transaction pressure exceeds the limit. So it is not critical that the increase happens at any specific point. What we still don't know, is what happens when real people really want transactions to go through, and when the pressure keeps up over weeks. I think there is time to do it calmly.


This test demonstrates that cypherdoc's resources are at 25-45% of its capacity. And if we increase block size 8x then he can process only 2-4 MB blocks and his nodes will collapse.

So you think his hardware is suffering from muscular atrophy?
cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 22, 2015, 11:40:35 PM
 #27115

what's interesting is that this attack is not slowing down block formation at_all.  we're just seeing continual full blocks.  based on Tradeblock's previous analysis, real customer tx's can probably get through if they pay a high enough fee.  unfortunately, the avg consumer won't know what that fee is given current wallet software capability and will get frustrated from delays.

edit:  altho unconf tx's aren't that bad at 4500
Erdogan
Legendary
*
Offline

Activity: 1512
Merit: 1005



View Profile
June 23, 2015, 01:10:16 AM
 #27116

what's interesting is that this attack is not slowing down block formation at_all.  we're just seeing continual full blocks.  based on Tradeblock's previous analysis, real customer tx's can probably get through if they pay a high enough fee.  unfortunately, the avg consumer won't know what that fee is given current wallet software capability and will get frustrated from delays.

edit:  altho unconf tx's aren't that bad at 4500

My guess is when we approach the limit, 1) people will learn what is the necessary fee to get their transactions into the first block, 2) the blocks will normally not be full for those transactions, 3) some people will pay lower fees and they are happy to risk waiting a few blocks sometimes. 4) The fee will be just high enough to discourage the least necessary transactions.

Said otherwise, since people's preferences are diversified, most people will be happy with the situation. This does not mean I want an artificial cap; the lower prices and the larger number of happy customers, the better chance bitcoin has to be the global money system everybody prefer. Only the physical limits of the system, as defined by nature, should exist.

cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 23, 2015, 01:21:31 AM
 #27117

dying off again:

smooth
Legendary
*
Offline

Activity: 2982
Merit: 1203



View Profile
June 23, 2015, 01:24:35 AM
 #27118

This does not mean I want an artificial cap; the lower prices and the larger number of happy customers, the better chance bitcoin has to be the global money system everybody prefer. Only the physical limits of the system, as defined by nature, should exist.

There is no physical limit defined by nature, other than whatever the highest capacity node in the world can handle (which would be the only node able to keep up and therefore the network would consist of a single node).

In any other configuration the capacity is defined by the lowest capacity node on the network, which is not a limit defined by nature, but by intended or unintended consequences of the protocol design. If you want the lowest capacity node to be home computers, embedded devices, etc. then the protocol has to be designed differently than if you want that lowest capacity node to be a large or very large server in a data center. Nature allows either.
cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 23, 2015, 01:31:17 AM
 #27119

i don't think any spam attacks can be sustained for a prolonged period of time.  it's too expensive as they pay normal tx fees.  while yes, at 1MB, they crowd out normal users, at 8MB or more, the spammers have to pay 8x more in fees.  while the anti Gavin crowd will say it's a drop in the bucket to perform such an attack even at 8x, what they i think they miss is that those tx fees will be tremendously beneficial for the miners raking up all those free fees and actually is expensive.  that will strengthen mining which is always a good thing for an industry that has been under stress for over the last year.  that would be the last thing they want to do.  can you also imagine a sustained 8x increase in the tx graph below?:



and what that would do to the price?  an 8x increase?  pt being, a spam attack is and will get more and more expensive and uneconomical and even strengthen mining.  it's be like your local candy store; owners ideally would like to sell to as many kids on the block as possible to keep them all happy but if one big kid keeps coming in week after week and buying out all your inventory, you aren't going to complain.  you might even prefer it as your turnover increases and you make more money.

all in all, this is just another form of manipulation of an open source, transparent system that won't work in the end and shouldn't be used as a reason for us not to adopt Gavin's plan.

edit:  yes, full nodes will be more expensive. but we already know they will become specialized.  and once pruning comes in, ordinary users can still run those.
cypherdoc (OP)
Legendary
*
Offline

Activity: 1764
Merit: 1009



View Profile
June 23, 2015, 01:37:11 AM
 #27120

hey, i thought the network was only capable of 2-3 tx/s?  look at our peaks today.  not bad:

Pages: « 1 ... 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 [1356] 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 ... 1557 »
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!