Change suggestion 2: https://en.bitcoin.it/wiki/Scalability
Add under storage section: Assuming 2000 TPS, which would be 1 megabyte per second, or 600 megabytes per block, it would be 3.5 gigabytes per hour. 84 gigabytes per day. 2.4 terabytes per month. 30 terabytes per year. After a decade it would add 296 terabytes in size.
Establishing new nodes or starting new pools would be highly difficult but not impossible, and would likely require mailing dozens of high density hard drives with a split bootstrap.dat.
Block chain growth on the other hand could be reduced by reducing transactions on the block chain, and making the blockchain more of a check clearinghouse style system between online wallets, although that would require trusting online wallet providers in the same sense many miners trust their pools.
Topic: Bitcoin Wiki Suggestions (Read 470 times)
I'm not willing to pay ~$9 for wiki posting privileges (I'll probably spend less time on the wiki then the forum anyway), so I'm going to make suggested changes to pages from here.
Proof of Burn: remurrage should be changed to dispatch. The opposite of demurrage is dispatch. It should also be mentioned that is theoretically possible to create an address prefix that would not have a private key attached to it, much like how Bitcoin addresses with a prefix of 3 can have multiple private keys.
Proof of Burn: remurrage should be changed to dispatch. The opposite of demurrage is dispatch. It should also be mentioned that is theoretically possible to create an address prefix that would not have a private key attached to it, much like how Bitcoin addresses with a prefix of 3 can have multiple private keys.
Jump to: