SatoshiTimes.com

[SatoshiTimes.com @satoshitimescom]

@t4t5 archived bitcoin sourceforge release notes confirm that the uploaded v0.1 version on jan 12th was actually v0.1.3

[SatoshiTimes.com @satoshitimescom]

@t4t5 archived bitcoin sourceforge release notes confirm that the uploaded v0.1 version on jan 12th was actually v0.1.3

[SatoshiTimes.com @satoshitimescom]

@t4t5 warren pointing out the same sneaky satoshi file swap with v0.1.3 too

[SatoshiTimes.com @satoshitimescom]

@notgrubles T4T5 may be saying otherwise here. We don’t know the initial setup of the genesis block machine plus the initial 14 blocks, since that v0.1 code has been lost. Perhaps intentionally as an extra security function by Satoshi.

[SatoshiTimes.com @satoshitimescom]

This is really interesting behavior by Satoshi at the Genesis of Bitcoin. The specific UTC time for when this 0.1.1 was built on jan 10th - records resource compilation at 23:08:02, followed 7 minutes 58 seconds later by final stripping at 23:16:00.
- Genesis Block of Jan 3rd
- Then Jan 8th Announcement on mailing list with apparent bitcoin.exe file available for download and running (which we no longer have apparently)
- block 1 + is mined on the same day, jan 8th, with this now lost software
- Jan 9th we see satoshi inviting hal finney to test this original 0.1 software uploaded to sourceforge as a .rar file at https://t.co/joeZtV7rT7 but no surviving copy exists, for deets see https://t.co/fX2AZtG47W
- on the same day, friday, Hal replies that he'll test it out on the weekend https://t.co/7fYFujnwVa
- next day Satoshi creates the Bitcoin mailing list on sourceforge https://t.co/c4s49jUIZy
- there's a day long gap between blocks 14 and 15 right at this time between the 9th and 10th.
- Satoshi emails adam back and wei dai on jan 10th saying he's released v0.1 https://t.co/KDL9DzCJhA
- Hal after this, sends satoshi an email at 10:59pm UTC saying 0.1 crashes, please fix it https://t.co/2Gmo4JWVzh
- 9 minutes latter on the 10th at around 11:08:02pm UTC, Satoshi built v0.1.1 , likely to help hal with the crash? ,

This 2nd version of the original was eventually uploaded to the bitcointalk/bitcoin.org/smf/forums as v0.1 in a clerical error by @halfin and user mrb ? (which is your control copy here) https://t.co/G10IFIMCNy

Fun

[SatoshiTimes.com @satoshitimescom]

This is really interesting behavior by Satoshi at the Genesis of Bitcoin. The specific UTC time for when this 0.1.1 was built on jan 10th - records resource compilation at 23:08:02, followed 7 minutes 58 seconds later by final stripping at 23:16:00.
- Genesis Block of Jan 3rd
- Then Jan 8th Announcement on mailing list with apparent bitcoin.exe file available for download and running (which we no longer have apparently)
- block 1 + is mined on the same day, jan 8th, with this now lost software
- Jan 9th we see satoshi inviting hal finney to test this original 0.1 software uploaded to sourceforge as a .rar file at https://t.co/joeZtV7rT7 but no surviving copy exists, for deets see https://t.co/fX2AZtG47W
- on the same day, friday, Hal replies that he'll test it out on the weekend https://t.co/7fYFujnwVa
- next day Satoshi creates the Bitcoin mailing list on sourceforge https://t.co/c4s49jUIZy
- there's a day long gap between blocks 14 and 15 right at this time between the 9th and 10th.
- Satoshi emails adam back and wei dai on jan 10th saying he's released v0.1 https://t.co/KDL9DzCJhA
- Hal after this, sends satoshi an email at 10:59pm UTC saying 0.1 crashes, please fix it https://t.co/2Gmo4JWVzh
- 9 minutes latter on the 10th at around 11:08:02pm UTC, Satoshi built v0.1.1 , likely to help hal with the crash? ,

This 2nd version of the original was eventually uploaded to the bitcointalk/bitcoin.org/smf/forums as v0.1 in a clerical error by @halfin and user mrb ? (which is your control copy here) https://t.co/G10IFIMCNy

Fun

[T4T5 @t4t5]

i rebuilt satoshi's 2009 bitcoin.exe byte for byte!

afaik nobody has been able to perfectly recreate the executable published in 2009 from source, because we didn't know the exact build environment that was used.

using opus 5.5, i reverse-engineered satoshi's build machine from the binary.

it now outputs an exe with the exact same sha256 as the 2009 release!

[SatoshiTimes.com @satoshitimescom]

@bensig you should try to find the private mailing list records wei dai and nick szabo were on that developed b-money as a concept...those conversations are still not yet public as far as i can tell

[Kiawtzin @kiawtzin]

"...but there's other things we could do"

-Satoshi Nakamoto

[COLDCARD @COLDCARDwallet]

COLDCARD Mk3 Security Advisory

If you generated a seed on a Mk3 after firmware 4.0.1, your funds may be at risk.

Mk4, Q and Mk5 are not affected based on our early analysis.

Read the advisory and migrate carefully:

https://t.co/3vgPHOjMS7

[Kevin Loaec 🧙‍♂️🐟 @KLoaec]

Alright I'm convinced THIS IS NOT A DRILL.
It is a small minority of users, not everyone.
We DON'T KNOW what the attack is. Could be RNG, could be NONCE, could be something else. We DON'T KNOW if it affects only single sig with no passphrase, or if it's a different layer. Use multisig, preferably multi-vendor.

[…::: jon @jonatack]

It's great to see more/wider support for open source bitcoin development.

It's frightening to see any aspect of it centrally coordinated by the same people that already have a lot of power.

Imagine you are a bitcoin open source developer, and an important person in or advising the consortium doesn't like you or has already played a role in defunding you.

Developers, like node runners, need good options.

[Scoresby @BitcoinScoresby]

Do you know the story of Nicholas Bohm?

⚡️ Running a Bitcoin node in January 2009.
⚡️ Emailing with Satoshi.
⚡️ Helped to prove Craig Wright was not Satoshi.
⚡️ Absolute lad.

https://t.co/oR1tNyGps9

[Jameson Lopp @lopp]

This is a neat new site that creates a timeline of over 1,000 activities performed by Satoshi Nakamoto: https://t.co/vr0reFmMTn