There is no magic formula.  As the author of the puzzle stated the addresses were selected randomly.  Random = no formula, got it?  Continue to waste your time looking but you will never find it.

Explain why you think an early adopter could not have 100,000 BTC? 

When we started we could mine them for free on our computers using the CPU and at one point they cost $0.10 per BTC to buy them.   So hypothetically an early adopter could have purchased say 50,000 BTC for only $5,000 and at 50 BTC per block would have only needed to mine 1000 blocks, at that time easily done in less than a month on a fast computer.

There is only one thing certain in this thread:  btcsuperhero does not have or have access to anyone who has $625,000,000.00

If they are registered and collecting KYC then they should have a compliance officer who should be able to answer this question.

If they are registered then they should be able to contact FinCEN directly and get an answer.

Two bits?  I think not.  Two bits is $0.25.  He only asked for $0.10.  So, more like a one dime punk scammer.

ajdaj, you would be wrong.  This was obviously done on purpose.

Hilarious addresses dude, I tip my hat to you.


Back in the old days when it did not cost anything to do a transaction and Bitcoins were only worth a couple of dollars each I actually placed one of my favorite poems into the blockchain, there to reside forever.  Here it is:


Of course you "forever flushed" away a lot more BTC than I did to clog up the blockchain forever with unspendable trash.

How does proving I have 1,000 BTC prove that I have 100,000 BTC?

I understand POF as "Proof of Funds", what is BCL?

This is a very large transaction with a newbie that posts phrases like "exposing a Satoshi" and "verifying a satoshi" without further explanation of what they mean.  So, you can see why I am hesitant and I have to ask a few questions.

If you cannot answer a few simple questions then nobody is going to do this large of a transaction with you.

After watching the episode I down voted the idea.  I guess China up voted the idea.

I have a Nissan Leaf.  By far the best car I have ever owned with one exception:  you cannot beat a gas powered vehicle for long trips.

Solution:  Electric car for everyday short trips, gas car for long trips.

I am in.

I have the 100,000 BTC spread out over about 1,000 accounts.

Question 1:  I am not 100% sure how or why you would want me to prove that I have that many BTC so please tell me more about that.  Are you wanting 1,000 signed messages from the 1,000 Bitcoin addresses?

Question 2:  Since you are a newbie I do not know how I can trust you to send me the $625,000,000.00 for the transaction.  Can you prove to me you have the $625 million dollars for the transaction?

EDIT Question 3:  What the heck do you mean by the phrases "exposing a Satoshi" and "verifying a satoshi"?  I do not understand.

Leaving out some small details:

1) Securely generate a private key.  This is basically a secure 256 bit random number.  It is not exactly 256 bits because it has to be less than a certain specified 256 bit number but for the purposes here let's just consider it a 256 bit random number.

2) Calculate the public key.  The formula is public_key = private_key * G.  Where private_key is a very large random number, G is the specified starting point on the specified elliptic curve (the "Generator" point), * is the specified scalar multiplication operation over the group of points on the elliptic curve and private_key is the calculated point on the elliptic curve.

3) Note that public_key is a point on an elliptic curve.  It has an X and a Y coordinate to describe which point is is.  But also note an interesting property of the X and the Y coordinates on all elliptic curves:  for every X coordinate on the curve there are only two possible Y coordinates.  It is not exactly correct in our case here but you can think of them as the possible positive Y coordinate and the possible negative Y coordinate.

Now the uncompressed public_key is simply X and Y.  So an uncompressed public key is 256 + 256 = 512 bits.

The compressed public key is X and a single bit, lets call it b, that tells you which of the two possible Y values to use.  So a compressed public key is 256 + 1 = 257 bits.  But you can easily calculate the full public key from the compressed public key by calculating the two possible Y coordinates from the X coordinate given and then using the single bit "b" to select which of the two Y coordinate values to use.

To get the Bitcoin address from the public key you either:

1) Take the full 512 bit public key (X, Y) and hash it down to 256 bits, then hash it down to 160 bits then encode the answer.

or

2) Take the 257 bit compressed public key (X, b) and hash it down to 256 bits, then hash it down to 160 bits then encode the answer.

Both the uncompressed and compressed versions of the public key and the encoded hashed versions of the public key (the compressed and uncompressed versions of the Bitcoin address) describe exactly the same point on the elliptic curve.

Therefore both the compressed and uncompressed versions of the Bitcoin address map back to exactly the same private key.

Are you using a HDD or a SSD for your data files?

If HDD then it may be too slow.  I found that until recently my HDD worked fine but with some of the most recent changes it was no longer fast enough to keep up so I switched over to my SSD and it started making good progress on catching up until this exception happened.

Waiting on 2.4.2 so I can get going again...

Yes, the bug I am reporting happens on 2.4.1.  Since there is no 2.4.2 yet maybe he is trying to say that hopefully this bug we are both having will be fixed soon in 2.4.2?

His response is cryptic but what I believe is that we are both running 2.4.1 full node, he is Win64, I am Win32, we are both getting the same error.

Win32, Full Node, running on an (through a symlink) SSD, got:

 Uncaught exception: Error: different props of 80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=, mem: {"unit":"80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=","level":3350626,"latest_included_mc_index":3245724,"main_chain_index":3245725,"is_on_main_chain":1,"is_free":1,"is_stable":0,"witnessed_level":3350611,"headers_commission":344,"payload_commission":157,"sequence":"good","author_addresses":["CHNK74ZY66XTYLWB45UES26G3AAS522V"],"witness_list_unit":"oj8yEksX9Ubq7lLc+p6F2uyHUuynugeVq4+ikT67X6E="}, db: {"unit":"80ftUd7v34yJstagU5EwTu6wyyDW0yRk9XX/K8ZL36Y=","level":3350626,"latest_included_mc_index":3245724,"main_chain_index":3245725,"is_on_main_chain":1,"is_free":1,"is_stable":0,"witnessed_level":3350611,"headers_commission":344,"payload_commission":157,"sequence":"temp-bad","author_addresses":["CHNK74ZY66XTYLWB45UES26G3AAS522V"],"witness_list_unit":"oj8yEksX9Ubq7lLc+p6F2uyHUuynugeVq4+ikT67X6E="}

Tried restart, still got the error, dead in the water.

Any ideas?

Up until recently my rotating media disk drive could keep up with the traffic on my full node wallet.

With the new version I can no longer keep up.

I would like to move the data files to my SSD.

Can I get instructions for moving the data files?  I am hoping it is something like:

1) Stop the program.
2) Copy the data files from where they are to a location on the SSD (which files to copy, where are they?)
3) Edit a file somewhere to point to the new data file location (what file to edit, what to edit?)
4) Restart the program
5) Catch up

If possible, I do not what to have to reinstall from scratch on the SSD and sync from the beginning.

The LBC project is currently running at 346.02 Mkeys/s and recently had a peak of about 521 Mkeys/s

How many keys per second does your method check?

Yes, ALL the Bitcoins in the puzzle transaction were placed there in a single transaction.  The author of the puzzle transaction came into this thread and explained the whole thing.  Yes, there is a well defined pattern to the puzzle transaction.  All the private keys are random but each key uses an increasing bit length.  Key one has a random one bit key, key two has a random two bit key, key three has a random three bit key, etc.  All of this work trying to find out a pattern to the random private keys is a complete and total waste of time.  "Fun" maybe, if you like to waste your time trying to find a pattern in random data.  If you bothered to read the thread you would know all this and would not have to guess.

We know exactly how the numbers were generated because the author of the puzzle came into this thread and told us.

Read back and find it if you are interested.

1) Are you trying to use vanitygen to solve this puzzle?  If so you are using the wrong tool - unless you plan to modify the code to make a program to work on this puzzle.

2) If you just want to install vanitygen for the heck of it and need information about vanitygen I suggest you ask in the vanitygen thread.  This thread is about the BTC puzzle transaction.

3) Maybe you meant LBC instead of vanitygen?  You can ask about LBC in the LBC thread - not here.

Wouldn't iByte (an apple) be more appropriate?