Bitcoin Forum
May 10, 2024, 08:36:31 PM *
News: Latest Bitcoin Core release: 27.0 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Post-Minting Phase and CPU Usage  (Read 8688 times)
InterArmaEnimSil (OP)
Member
**
Offline Offline

Activity: 77
Merit: 10


View Profile
July 16, 2010, 03:52:00 AM
 #1

I've got a machine that I've left running "for the cause" for the past week or so since I found out about bitcoins.  Even though I'm skeptical of a few of the monetary policy claims behind the currency, I think an extra-governmental digital currency is in and of itself a positive thing, so I'm willing to run my machine more than usual to help out with the network.  I've got two questions regarding CPU consumption, which stem from the fact that my machine is a speed-stepping laptop.

1)I understand that 21,000,000 coins is the maximum.  How many total blocks will this be, given the logarithmic decrease of coins/block when we hit the 21M?

2)After all the blocks are minted, the network, as I understand it, will be responsible for validating transactions, and will receive occasional transaction fees as an incentive for running the system.  Currently, generating coins guzzles CPU cycles, but I can see no reason why the much faster transaction processing won't be far more lax on the CPU, as it won't involve literally constant crypto work.  Am I right or wrong here?

12aro27eH2SbM1N1XT4kgfsx89VkDf2rYK
Each block is stacked on top of the previous one. Adding another block to the top makes all lower blocks more difficult to remove: there is more "weight" above each block. A transaction in a block 6 blocks deep (6 confirmations) will be very difficult to remove.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction.
1715373391
Hero Member
*
Offline Offline

Posts: 1715373391

View Profile Personal Message (Offline)

Ignore
1715373391
Reply with quote  #2

1715373391
Report to moderator
bdonlan
Full Member
***
Offline Offline

Activity: 221
Merit: 102


View Profile
July 16, 2010, 03:58:11 AM
 #2

2)After all the blocks are minted, the network, as I understand it, will be responsible for validating transactions, and will receive occasional transaction fees as an incentive for running the system.  Currently, generating coins guzzles CPU cycles, but I can see no reason why the much faster transaction processing won't be far more lax on the CPU, as it won't involve literally constant crypto work.  Am I right or wrong here?
You still need to generate blocks (and do all the hashing etc) for transaction processing - the proof-of-work is what prevents an attacker from producing a very convincing block chain with transactions cleverly rearranged to undo his payment.
Insti
Sr. Member
****
Offline Offline

Activity: 294
Merit: 252


Firstbits: 1duzy


View Profile
July 16, 2010, 10:22:40 PM
 #3

1)I understand that 21,000,000 coins is the maximum.  How many total blocks will this be, given the logarithmic decrease of coins/block when we hit the 21M?

Somewhere around block 5,355,000 (this will be sometime around 2111 at 6 blocks an hour.)
I expect many things will have changed by then though.


 

knightmb
Sr. Member
****
Offline Offline

Activity: 308
Merit: 258



View Profile WWW
July 16, 2010, 11:22:20 PM
 #4

1)I understand that 21,000,000 coins is the maximum.  How many total blocks will this be, given the logarithmic decrease of coins/block when we hit the 21M?

Somewhere around block 5,355,000 (this will be sometime around 2111 at 6 blocks an hour.)
I expect many things will have changed by then though.

Interesting, I could still be alive then.  *gramps sitting in rocking chair*  "I remember back in the old days when we didn't have 200 core computers in our cell phones to create these blocks" to which the great-great-great grand kids reply "Yeah, he's loony; everyone knows there is no such thing as a single core computer...."  Grin

Timekoin - The World's Most Energy Efficient Encrypted Digital Currency
D҉ataWraith
Member
**
Offline Offline

Activity: 60
Merit: 10



View Profile
July 17, 2010, 05:15:59 PM
 #5

Hehe, nah. Everybody's brain will have been copied into a computer by that time anyway, so no need for cell phones.  Cheesy

If Moore's Law holds 'til then, a single computer would be waaaay more powerful than all today's human brains combined. Kind of scary, kind of cool. Gotta love exponential trends...

1NvcPV6xi6yqo5yg8aWSkNdasPSAsGtt1m
theymos
Administrator
Legendary
*
Offline Offline

Activity: 5194
Merit: 12983


View Profile
July 17, 2010, 10:46:45 PM
 #6

1)I understand that 21,000,000 coins is the maximum.  How many total blocks will this be, given the logarithmic decrease of coins/block when we hit the 21M?

Somewhere around block 5,355,000 (this will be sometime around 2111 at 6 blocks an hour.)
I expect many things will have changed by then though.

The last block that will generate coins will be block #6,929,999. Then the total number of coins in circulation will remain static at 20999999.9769.

I've created some future-proof calculators for this:
http://theymos.ath.cx:64150/q/bcperblock/6929999
http://theymos.ath.cx:64150/q/totalbc/6929999
(Change 6929999 to whatever number you want, or leave it out for the current number of blocks.

1NXYoJ5xU91Jp83XfVMHwwTUyZFK64BoAD
Insti
Sr. Member
****
Offline Offline

Activity: 294
Merit: 252


Firstbits: 1duzy


View Profile
July 17, 2010, 11:17:41 PM
 #7

The last block that will generate coins will be block #6,929,999. Then the total number of coins in circulation will remain static at 20999999.9769.

I've created some future-proof calculators for this:
http://theymos.ath.cx:64150/q/bcperblock/6929999
http://theymos.ath.cx:64150/q/totalbc/6929999
(Change 6929999 to whatever number you want, or leave it out for the current number of blocks.

Cool thanks, I trust your calculations more than mine (which were 5 mins and a spreadsheet.)
Pages: [1]
  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!