Bitcoin Forum
December 03, 2016, 02:45:10 AM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Why is the bitcoin sky blue? -- n00b questions ;D  (Read 619 times)
MotorMouth
Newbie
*
Offline Offline

Activity: 4



View Profile
July 03, 2011, 07:06:42 AM
 #1

n00b question #1:
Looking at block explorer it looks like we're on block 134516 (is that correct?)
And at the end of each block, the hasher gets to "mint" a certain number of bitcoins... (correct?)
Right now it's 50 (yes)?  Did it used to be more? (100?) or did it start at 50? (don't know how to locate older blocks that aren't on the first page...)
Anyway, assuming each block is sequential (are they?), and that they started at 1 (did they?), there would be 50 x 134516 (or 6`725`800) BTC in existence.  That can't be right-- right?
Just curious how close we are to that 2 million mark.

Edit: hmm found part of the answer here: https://forum.bitcoin.org/index.php?topic=12530.0, it is about 6 million (http://blockexplorer.com/q/totalbc...)  So what's the total?  Is it 21 million?  I thought it was something with a 2...
Edit: ahh yeah, http://en.wikipedia.org/wiki/Bitcoin#Monetary_differences It is 21 million.

n00b question #2:
The mining difficulty increases every so often right?  Is there a way to find the history of difficulty increases?  I was hoping to coorelate difficulty increases to the different exchanges' prices and see if there was anything to see... (yay, let's try science!)


n00b question the third:
As a pool miner, how do I know that 100% of the work I'm being sent is actualling mining work and that I'm not helping the operator build a hash table or something on the side?  (I'm assuming my client calls 'getwork', gets back data, I hash it, and send the results back, yes?) -- also if we hit that 2 million mark (or max mark, whatever), and we have all this uber Th/s infrastructure in place for mining, what's to stop those pools from collectively cracking people's wallet encryptions (or other encryptions...?)  I'm assuming since each trasnaction is signed by the sender, that addresses that have never sent anything (or only send very little) would be easier to crack (because there will be more matching solutions that can fool the network), right?


Thanks, any insight into the above would be appreciated.



14FLvzjZfv486arHUjXEsU2x64VarTKepY
1480733110
Hero Member
*
Offline Offline

Posts: 1480733110

View Profile Personal Message (Offline)

Ignore
1480733110
Reply with quote  #2

1480733110
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
willphase
Hero Member
*****
Offline Offline

Activity: 770


View Profile
July 03, 2011, 09:26:25 PM
 #2

#2 - http://bitcoin.sipa.be/

#3 - Your are manipulating the block header to check if it hashes to a value that has a set number of leading zeros (for most miners, this is 8 zeros).  You change the nonce value which is at a set offset in the header.  If the pool wanted you to crack a password hash or something, then the hash it would be asking you to crack would have to start with zeros as well.  In addition, bitcoin block header hashes are double-SHA256 which is not usually used for hashing passwords especially as most of them use a salt.

Will

TurboK
Full Member
***
Offline Offline

Activity: 137



View Profile
July 09, 2011, 12:02:07 AM
 #3


Is there any other site like this one? It seems the graphs were changed recently and they are now pretty much worthless.

12zJNWtM2HknS2EPLkT9QPSuSq1576aKx7

Tradehill viral bullshit code: TH-R114411
k
Sr. Member
****
Offline Offline

Activity: 452


View Profile
July 09, 2011, 12:15:34 AM
 #4

#2
blockexplorer.com/q/nethash/2016
Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!