Topic: Ok, here's a 1BTC puzzle. - page 16. (Read 14607 times)

Why 21 Million?

Technical Explanation
One of the reasons was the need to keep the number of Satoshis within the limits of 64-bit double floating numbers with a small margin for multiplication/division rounding.

64 bit floating gives 52 bits of explicit storage. Interestingly 2 to the power of 51 is 2,251,799,813,685,248 units. This is just enough to store 21 million coins times 10⁸ divisions.

Mathematical Explanation
Calculate the number of blocks per 4-year cycle:

6 blocks per hour

6 blocks per hour
* 24 hours per day
* 365 days per year
* 4 yeears per cycle
= 210,240

~= 210,000

Sum all the block reward sizes:

50 + 25 + 12.5 + 6.25 + 3.125 + .... = 100

Multiply the two:

210,00 * 100 = 21 millions

Economically, because the currency is effectively infinitely divisible, then the precise amount doesn’t matter, as long as the limit remains fixed.

Since Bitcoin is often compared to gold, total coins matches total amount of gold mined in human history which can be imagined as a cube 21 m on a side.

As it is not entirely so important how many Bitcoins will exactly be mined. Satoshi could have easily chosen almost any number. He could just adjust block reward halving (210 000 blocks), reward sizes (50, 25, 12.5 …) etc. to match some particular number.

https://cryptalker.com/21-million/

I googled this words:
and found some books and articles about bitcoin. In tow of them mentioned that the reason of why total number of bitcoins is 21 million(finit) is because Satoshi wants Bitcoin mimic supply of gold in blockchain system.

Deepening myself more and more in this mystery, I seem to be closer to each other, but each circumstance leads me to a rather good path. I have spent a few nights and here are my current assumptions and results:
* .txt - I think the author meant that the way to solve should start in on this type (if not exactly): https://en.wikipedia.org/wiki/Text_file [thanks to this and similar reading I took a step continue] ->
* I got to the place where you can probably put it all together: https://www.dcode.fr/permutations-with-repetitions
... in so far as it is not necessary to focus specifically on this particular script - there are so many combinations and uses that certainly one of these several hundred tools is the key to the puzzle.
* I think there is no SATOSHI NAKAMOTO in the solution ... These are not English words in any form.

If I helped through my contribution with this post in your progress on this puzzle - rate and mark as merit

I think the first letters of the 8 words used in the answer maybe is to be used for the private key solution.

Im not too sure about that .txt what that means, but i've done some digging tonight, i've been scraping the bitcoin whitepaper for words starting with the letters used.
Having done that i now have a somewhat smaller list of words to be used.

I've then tried using watashi-kokoto's jsfiddle puzzler, but came up emptyhanded until now, it's pretty hard finding a meaningful combined text with the max of 32 chars 

I've tried these combinations:
WeTrustCodeOnNetworkOfHashTheory
WeTrustCodeOfNakamotoOnHashTrust
WeTrustCodeOfNakamotoOfHashTrust
WeTrustCodeOfNakamotoOrHashesToo
WeTrustChainsOfNetworkOnHashTime
WeTrustChainOfNetworkOnHashTrust
WeTrustCashOnNetworkOrHavingThem
WeTrustCashOnNetworkOnlyHaveThem
WeTrustChainOnNetworkOverHashToo

Maybe someone can actually make something out of the wordlist i've managed to get hold of from scraping that BTC whitepaper? would be great...

W:
Waits
Walk
Want
Wants
Was
Way
We
Wealth
Were
Were
What
When
Where
Which
While
Who
Widely
Will
With
Without
Work
Working
Would

T:
Tail
Take
Taking
Targeting
Telling
Than
That
The
Their
Them
Themselfes
Then
Theory
There
These
They
They'll
They're
Thin
Third
This
Those
Through
Throw
Tie
Time
Timestamp
Timestamped
Timestamping
Timestamps
To
Tolerant
Too
Took
Trades
Traditional
Transact
Transaction
Transactions
Transfer
Transfers
Transition
Tree
Trials
Trust
Trusted
Try
Trying
Two

C:
Calculate
Came
Can
Cannot
Cant
Care
Case
Cash
Casual
Catch
Catches
Catching
Cent
Central
Certain
Chain
Chained
Chains
Chances
Change
Changed
Changes
Channel
Characterized
Check
Choose
Chronological
Circulation
Code
Coin
Coins
Collectively
Collects
Combined
Combining
Come
Common
Communication
Compacted
Company
Compensate
Competing
Complete
Completely
Computational
Computationally
Computer
Conference
Confirm
Consensus
Consider
Constant
Containing
Continue
Continuously
Control
Controlled
Convention
Convinced
Cooperating
Coordination
Copy
Correct
Cost
Costs
Could
Counter-measure
Counts
Course
Cpu
Creating
Creator
Credit
Cryptographic
Cryptology
Cryptosystems
Cummunications
Currency
Current
Customers
Cutting

O:
Obtain
Odds
Of
Off
Old
On
Once
One
Ones
Ongoing
Online
Only
Open
Or
Order
Other
Otherwise
Ought
Our
Outpace
Output
Outputs
Over
Overpowered
Owerpower
Own
Owned
Owner
Owners
Ownership

N:
Nakamoto
Names
Necessarily
Necessity
Need
Needed
Needs
Network
Never
New
Newspaper
Next
No
Node
Nodes
Nonce
Non-reversible
Normally
Not
Now
Number

H:
Handle
Happened
Happens
Hardware
Has
Hash
Hash-based
Hashcash
Hashed
Hashes
Hashing
Hassling
Have
Having
He
Header
Headers
Help
Here
Hes
Him
Himself
His
History
Honest
Hour
How


If anyone is lucky to get that privatekey, one little tip would sure be appreciated, thanks 

1JAGo77nRtH2bBRbUe4ndW4zRtHSe3HKdD

Change the URL from
https://hi-in.facebook.com/blockchain/posts/thanks-to-our.../1180872818611963/
to:
https://facebook.com/blockchain/posts/thanks-to-our.../1180872818611963/

With this simple method, you will display this article in your local system language (keeping the fonts readable to you)

By the way, you can not waste time, because I've already checked it a few days ago and I did not find anything in this post ... Maybe it's some clue ...?

I've just done a quick google search for Natasha Otomoski and found 1 result, but I don't understand the language and the facebook page doesn't load for me, probably because I don't use facebook account, so I can't reach the content?

Don't worry, i have a Qtrit quantistic qcpu 

using the bip39 wordlist, there are a total of 161,735,049,399,563,309,103,078 valid possibilities to try.
this number was derived using the following algorithm:

.txt extension suggest me a dictionary attack.

I find it odd that the OP made 3 posts, 3 years ago then nothing until this puzzle. Not sure if it's relevant but thought I should point it out.

1814400 combinations can be from 8 digits. from 8 words even more

I am still confused with this thread, so now I am reading the comments from the members while studying it.

yup it just takes time and energy

stop trolling. some puzzles can take years before they're solved.

the OP didnt even give a single hint, how can he expect us to solve this ?
billions of possiblities,, im done with it, best of luck everyone

Because maybe you're starting to be annoying and spammy? Check your replies and see if they are helpful and fun to read.

you can only call it a "scam" if they asked you to pay some money to participate in this puzzle! since nobody asked for anything then worst case scenario is that you wasted your time and got "trolled".

Hi guys,
what is the probability that the "1BucK" is not a Vanity address and was just a coincidence?   1BTC=1Buck

Not really solution but just came up with this: "BlueWhalesHaveNoTeethOfTheirOwn" - that is 8 words, 32 characters - I think it is a play on the idea that Satoshi is a "whale" and big whales - like blue ones - do not have teeth. Some sort of pun - that probably is not literally it - too easy - but playing along the pun lines might work, methinks. The question is a file name - so that file has two roles - it contains information but is itself in its own name also information - so that implies there is a pun going on - apparent meaning plus secondary meaning - two roles - so I think the question being in a file name tells us to look for puns.

Funny that this is still going on, I thought for sure it would have been solved by now.


I would guess that it would be this one:

https://brainwalletx.github.io/

When I was guessing I was sure to generate both "compressed" and "uncompressed" versions of the keys.