Congrats on sapphire: you still have Al after aluminum oxide melts at >2000C, making it much more forever than diamond (carbon), which turns into carbon dioxide at 700C and blows away.

Go to account history and pick Please choose which history you want to see: BTC. Then examine the last btc transactions. Also check the registered email address for notifications.

Then pick the move topic button in the lower left of this forum post page and move the thread to marketplace->economics->service discussions, after unchecking the move notification.

This is nonsense. It takes no extra time to randomly find a <0000000ffff hash that is equivalent to difficulty 1, 2, or 2000. Anything may come out of the hasher as the first hash you get. There is no "six days of hashing", that is just a stupid idea.


This is nonsense, as I described before, this likely means only that 2^32 * (ExtraNonce - previousExtraNonce ) + nonce hashes were performed after genesis mining start before a block solution was created. Any computer that starts Bitcoin 0.1.0 mining increments its nonce+extranonce in the same deterministic way absent any network block or transaction messages. There is no connection between the genesis creator and the rest of the blockchain.



Lets look at how many Bitcoin clients there actually were then:

When Hal posted his crash debug log (cleverly pointed out by non-noob member Point at Infinity) containing the same first 49 blocks as we have now, it showed no timewarping or forking was done. Block 49's Timestamp is 2009-01-10 18:56:42; the email list message time is 2009-01-10 19:13. Block finding rate is similar before and after this point.

What it also shows is the number of Bitcoin clients listening in IRC for peers. Each Bitcoin has it's own 14 character "u" nick in the #bitcoin channel in 0.1.0 (you'll still find these in that channel from time to time). Who was in that channel? Three people were in the channel: Hal, another Bitcoin 0.1.0, and a listener.

List of nicks in #bitcoin channel:
IRC :lem.freenode.net 353 uCeSAaG6R9Qidrs @ #bitcoin :uCeSAaG6R9Qidrs x93428606 @u4rfwoe8g3w5Tai
IRC :lem.freenode.net 366 uCeSAaG6R9Qidrs #bitcoin :End of /NAMES list.

More info about those users?:
(format RPL_WHOREPLY "<channel> <user> <host> <server> <nick> ( "H" / "G" > ["*"] [ ( "@" / "+" ) ] :<hopcount> <real name>")

First nick to join channel (had channel ops): Bitcoin 0.1.0 user u4rfwoe8g3w5Tai
lem.freenode.net 352 uCeSAaG6R9Qidrs #bitcoin n=u4rfwoe8 h-68-164-57-219.lsanca54.dynamic.covad.net irc.freenode.net u4rfwoe8g3w5Tai H@ :0  u4rfwoe8g3w5Tai

Second nick to join channel: x93428606 (not bitcoin, connecting by Tor)
lem.freenode.net 352 uCeSAaG6R9Qidrs #bitcoin i=x9342860 gateway/tor/x-bacc5813d7825a9a irc.freenode.net x93428606 H :0  x93428606

Third nick to join channel: Hal's Bitcoin, uCeSAaG6R9Qidrs
lem.freenode.net 352 uCeSAaG6R9Qidrs #bitcoin n=uCeSAaG6 226-132.adsl2.netlojix.net irc.freenode.net uCeSAaG6R9Qidrs H :0  uCeSAaG6R9Qidrs

There is no evidence either way that bitcoin #1 was satoshi. To receive the first bitcoin transaction, Satoshi would not even need to run Bitcoin, just giving an address would be sufficient.

I am done responding to this thread, since my previous analysis is not interpreted correctly and there is no hypothesis here. Satoshi is bitrich, you aren't.

Please don't expect. Run bitcoin-0.1.0 on a private network. You don't need to compile it, run bitcoin.exe. You need two bitcoin machines with different IP addresses, and an IRC server that pretends to be freenode. See how much of your quad core it uses. See how long it takes to mine 10 blocks. It won't prove or debunk any argument, because the argument itself is ludicrous, but then you will know.

While we are posting code, net.cpp:

//// todo: start one thread per processor, use getenv("NUMBER_OF_PROCESSORS")
void ThreadBitcoinMiner(void* parg)
{
    vfThreadRunning[3] = true;
    CheckForShutdown(3);
    try
    {
        bool fRet = BitcoinMiner();

You can check out the python miner as a reference, which does all it's hashing in software. https://github.com/jgarzik/pyminer

Technically, if it didn't take you about 30000000000000000 hashes to find a valid nonce, its not really a block hash..

Wrong. (you should stop posting now...)

The genesis block, Sat, 03 Jan 2009 18:15:05 GMT, had to be included in the c++ code before it was compiled. Then the code had to be tested and packaged before it was released. Bitcoin probably was "premined" before release by some testing, but any blockchain testing was discarded.  Satoshi appears to have had working near-Bitcoin code for quite a while (see quote above).

Since the genesis block also has an extranonce of "4" like the first block does, it is likely generated with the same Bitcoin mining code as in the client, and took no more effort to find than the first block (3-4 nonce cycles).

The freenode #bitcoin channel (now used for discussion) is where Bitcoin originally connected to find peers. It would be interesting if there are any logs of how early this channel first appeared to see pre-release testing activity.

A more accessible view of discussion in that archive (which is a metzdowd mirror):
http://pl.it-usenet.org/group/11834/2008/11/
http://www.mail-archive.com/cryptography@metzdowd.com/thrd10.html

And interesting posts, Satoshi had been working a while on it:


and about inflation or deflation from coin creation rate:

Almost 4000 BTC a day is still getting printed ($4M USD worth), and it hardly debases the currency.

Wrong: http://www.metzdowd.com/pipermail/cryptography/2008-November/thread.html

You can look at the references:

https://bitcointalk.org/index.php?topic=120960.0 - has examples of getwork submissions

Here's an old post, follow for more info:


You are getting a block header, changing the nonce, and returning the hash of it you found which is below the target.

Note that special transforms have to be done before hashing (and then back before submitting results). Endian-ness of data needs to be flipped in 4 byte increments before hashing.

Header contents from your data (hashes are reversed):

Version: 00000002

00000002 9af1f43c342ad525e3c4fd9368a76fbe32a2bfc1d5503b6c00000076

Previous hash: 0000000000000076d5503b6c32a2bfc168a76fbee3c4fd93342ad5259af1f43c
(block 230829)

00000002 9af1f43c342ad525e3c4fd9368a76fbe32a2bfc1d5503b6c00000076
00000000 e5a720f8ec330f06fab42bb92f24d5d4211002bb202beb163fbeed28

Merkle root: 123f8e23fbeed2802beb16311002bb2f24d5d42ab42bb92c330f06fe5a720f8e

00000000 e5a720f8ec330f06fab42bb92f24d5d4211002bb202beb163fbeed28
123f8e23 5166d77c1a022fbe0000000000000080000000000000000000000000

Timestamp: 51 66 d7 7c (1365694332 unix epoch time)

123f8e23 5166d77c 1a022fbe0000000000000080000000000000000000000000

bits (Compact target): 1a 02 2f be

123f8e235166d77c 1a022fbe 0000000000000080000000000000000000000000

nonce: the value your miner will be changing

123f8e235166d77c1a022fbe 00000000 00000080000000000000000000000000

the data1 midstate should be ignored and calculated by your miner, newer mining protocols remove this.

Forum moderation policy


OP should edit the post before a mod does it.

I just put in a virtual order to liquidate 1M BTC if that's the OP's hypothesis (and yes, you could sell them, there are currently book orders to buy twice as many BTC as will ever exist) - :

I would love to see all the coins dumped. That would end this FUD and the temporary crash would only bounce up as people realize there is no more mystery coin.

The "early adopters are rich" is played out; besides Satoshi (who may never move coins or may not have early wallets - Bitcoin implementation may have been merely a proof of concept in his head), other mined coins have been lost or changed hands for things like pizzas and early investors have sold many times over. There are just a few, like casascius, who are strong willed enough to never spend their Bitcoins. I'd be relatively well off if I still had every BTC that's ever been in my wallet or knew the magic time to exchange them, but I spent them.

Most service workers would have a different opinion of the consideration paid them by the wealthy.

I didn't know that people are counting suit sleeve buttons, I'm calling my Savile Row tailor and telling him to update my pattern to buttons all the way up!


While Tradehill charged a USD fee to both sides of a trade, mtgox earns both BTC and USD in fees. This put about 9000 BTC of fees last month into their wallet. You can make your own argument that this is like a stock broker being paid in the stock he is pumping, but as Bitcoin is a currency, it shows that they are putting confidence in Bitcoin's success and future value by accepting it for their trading service (unlike most traders here, who just want to extract the most USD from BTC). Would you rather have an exchange that doesn't trust BTC enough that they want all their fees paid in USD?

BTW, it did go back up after a crash (to other exchange's prices), which everyone besides mtgox could also predict.

Now that you've proved nobody can identify you, you want to start a service where people send you Bitcoins. Seems reasonable.

Date from the raw email @ mailing list:


Note that the Jan 09 time above is UTC +8, it's Satoshi (pretending to be) in Asia or Western Australia.

Block 1 timestamp: 1231469665 Fri: 09 Jan 2009 02:54:25 GMT

At block 73, someone's miner gets a restart or a new player starts mining for several blocks

coinbase":"04ffff001d0101"
Sat, 10 Jan 2009 23:31:28 GMT

It is strong evidence that one entity mined those blocks. Mining timestamps start three hours after the announcement email dropped in the inbox of every crypto mailing list subscriber.

It would be cool if coinbase scriptsig + nonce could act as a counter of exactly how many hashes an individual miner has been doing, but analysis doesn't allow perfect inference of the hashrate. The bnExtraNonce (which is an OpenSSL bn BigNum being written in hex) starts at 1 every instantiation and is incremented whenever the miner loop is restarted which is:

-if the miner thread is restarted (through UI, restart),
-after every 262144 hashes:

• if new transactions have been seen and miner has ran for more than 60 seconds,
• if there is a new network block or a block is found
• if the nonce has wrapped to 0

One still could dump nonce+extra and attempt to assemble a tree of likely continuous miner runs, although analysis code might get confused pretty quickly.

One interesting thing in my reading of 0.1.0 is that mining won't start if Bitcoin is not connected to other nodes, so there had to be at least two Bitcoin machines on. This is probably to prevent naive forking, from miners reconnecting with a longer chain. In fact, I found that bitcoin would crash if it can't get to IRC. It also determines external IP addresses using two web services by static IPs that are dead, only one of which is still alive by DNS, so this makes testnetting harder since you have to emulate these. On the plus side, it writes the genesis block itself if blk0001 doesn't exist (which I find out after manually dumping and importing block 0 into another Bitcoin).

Also it looks like a good CPU would be lucky to get ~0.5MHash - the miner is single-threaded, and it calls the Crypto++ library to do SHA256 and byte juggling twice for every hash.

BTW all this crap about 32 hash bits etc is irrelevant. When did Sergio go batshit?

Mining was not constant either during 2009, it's up to you to figure out how much is Satoshi:

That is an incorrect assumption, remember the default behaviour of Bitcoin was to generate coins with just one checkbox in the options menu. You will find there are many people trying out Bitcoin, and before this forum opened, there was about six months of (lost) chit chat on a sourceforge forum too, so it's hard to examine records of people trying it out (or leaving it running):

2009-06-13 06:41

The new Bitcoin website/portal is up at bitcoin.sourceforge.net.  
Forums and a wiki are included, so you're welcome to join discussion  
and wiki documentation.

Martti Malmi
Bitcoin Web Developer


From here...





But what is true is that anybody running Bitcoin that year with a consumer Core 2 would make about 2000 BTC a day.
[Bounty] 201600 BTC for a time machine, I only need a few hours...

The new database for v0.8.0+ is stored in two subdirectories, "blocks" (block data, with block id database in "blocks/index"), and "chainstate" (unspent output database). Do not mess with files in these subdirectories.

The current size of the blockchain database subdirectories is 7.83 GB, 6.76 GB of which is raw block data.

1. Do you know why you wanna?
2. Start reading: https://www.weusecoins.com/en/mining-guide