12 Comments
User's avatar
Anirudh Ramesh's avatar

Great article πŸ‘. Reads like a nice story from beginning to end.

jatin's avatar

Great article. Thank you so much Aaryaman.

Pranav Mittal's avatar

Thank you Aaryaman! The conceptual clarity aside, this is an extraordinary piece of writing!

UB's avatar

Very useful read. Thanks for penning this down. I had one doubt :

"Supposing the message came accompanied by a digital signature, our general has all of the tools he needs to verify the signature for himself without trusting anybody else. The contents of the letter would be the message, the signature would be some alphanumerals that would be sent along with the letter, and the public key required for verifying the signature would be the public key of the purported sender of the letter."

Would a leak of someone's private key make it possible to do fraudulent transactions? Since the private key + the message + the public key is all that's needed to verify a transaction

Aaryaman.Vir's avatar

hello and thank you. yes, with another person's private key, you could generate signatures on their behalf which would lead to identity theft (in the case of the generals) or loss of bitcoin (because the attacker could publish properly signed transactions sending bitcoin out of the compromised public key/wallet)

Raghu Venkat's avatar

Succinct and well hashed article. Nice one.

Thirumurugan Karunakaran's avatar

Lovely written BRO!!!! God Bless!!!

Fluky Hermit's avatar

Thank you so much for writing out this masterpiece on Bitcoin101.

Darshan Subash's avatar

The most crystal clear foundational primer on crypto I have found. Would highly recommend this to everyone in my network. Thank you so much for this Aaryaman.

they’ve's avatar

This was just what I needed, thanks a ton!

Vishal's avatar

Superb..excellent work

akshat's avatar

Thanks for the detailed article Aaryaman. Thoroughly enjoyed it. I had a doubt which wasn't covered in the Q&A:

> When reorganization happened, Abdullah and Beelzebub's computations to generate Block#21 would be wasted. That would imply every time "different" blocks are committed, thousands of nodes would end-up spending ~10 minutes (average time between 2 blocks being committed) trying to solve mining puzzle for a history that would be discarded. Do you know the number of nodes that have to do reoganization for every block being committed, and if this problem is being solved in some way?