Did you know Bitcoin Core got it's 1st fee estimator in February 2015 with Bitcoin Core 0.10.0
Before this fees were hardcoded, and changed with new versions to reflect market conditions.
Here we can see people in 2010 being very surprised by the fact that fees are even a thing on Bitcoin.
They did not knew the extra BTC they got when mining were transactions fees.
Here we can see people in 2010 being very surprised by the fact that fees are even a thing on Bitcoin.
They did not knew the extra BTC they got when mining were transactions fees.
Satoshi, Gavin and theymos were the 3 known people to have access to the trigerring key.
It was speculated Mark Karpeles(Mt. Gox CEO) had one.
The only one to trigger these alerts was Gavin.
Even though it could only send a text message that was sent to your node, it was still dangerous.
Some rogue actor could ask people to update to a bad client, and claim a vulnerability.
Because of this it was completely removed in 2016, and the private key was made public.
However between the TX in Block 170 to Hal until the one shown above, we can see there were 7 other transactions made.
Looking at how the funds flowed, it seems Satoshi was making test payments to hiself.
Satoshi explaining what is a Blockchain
Bitcoin use the bas58 format for addresses(non-segwit)
Satoshi makes a point that script does NOT have loops
Simpler = better security!
This decision is what sets Bitcoin apart today from other blockchains.
Satoshi copied the implementation of SHA256 from the Crypto++ Library maintained by Wei Dai.
This makes a lot of sense, since it's always good to NOT implement your own cryptography.
Seems Satoshi considered using other Eliptic Curves for Bitcoin.
One strange thing here is the 279 value for secp265k1 in this comment. Typo?
Bitcoin uses secp256k1 with the standard 256 bits length.
Satoshi showing a bit of humours.
Since this is the last process that will run, it will close the app, hence closing the lights :)
wxFormBuilder was a GUI designer for wxWidgets C++ kit and fairly common.
You could design the layouts then it would automatically generated the corresponding C++ code for the GUI components.
Satoshi preferred this because it was also lightweight and had less dependences.
With version 0.5 on 21 November 2011, The Bitcoin Client(not yet called Core) introduced the QT user interface.
The QT stayed in the name of the client for a number of years.
The QT UI is still use this today by the Bitcoin Core client.
A fix was quickly issue by Satoshi and downplayed, probably in the hope of not triggering an exploit.
He also included some improvements in the upgrade.
The fix made the OP CODE return false, meaning outputs are now provably unspendable. - i.e. can never be spent = burned!
3/4
in 2013 people were doing odd hacks to insert in the blockchain:
- random data
- use it as a timestamp
But these hacks would forever stay in the the UTXO set!
A decision to set OP_RETURN as a parameter that allowed 40 bytes of data to be added.
This data can be pruned!
And ever since it was introduced, OP_RETURN always caused controversy and was changed quite a few times.
And the conversation was always about HOW MUCH data it should allow?
And now we are having this conversation yet again.
What do you think? 
Before launching the White Paper on 31 October 2008, Satoshi contacted Adam Back to verify the Hashcash citation.
in the email a draft of the White Paper is present.
Filename: e-cash.pdf
The Title is pasted in the email
"Electronic Cash Without a Trusted Third Party."
Adam mention's Wei Dai's b-money.
22 August 2008 Satoshi contacts Wei Dai, same draft is shared in the same format.
Link to a e-cash.pdf
The Title pasted:
"Electronic Cash Without a Trusted Third Party."
I was also curious if he registered 
5/5
And the last name come from the preBitcoin v0.1 code that Satoshi shared in private to a few testers.
In one instance when testing if the mining functions work he calls it SUPERCOIN.
This code was later share by one of the testers.
