Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 2/12 - First, what is Bitcoin Script? Every bitcoin is locked behind a small program — a set of conditions that must be satisfied to spend it. Think of it as a combination lock: the coins sit idle until someone provides the right sequence to open it.
R to @daily_btc_lore: 2/12 - First, what is Bitcoin Script? Every bitcoin is locked behind a small program — a set of conditions that must be satisfied to spend it. Think of it as a combination lock: the coins sit idle until someone provides the right sequence to open it.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 3/12 - On June 17, 2010, a user on Bitcointalk asked Satoshi about the cryptic strings visible in Bitcoin transactions — things like 'DUP HASH160 ... EQUALVERIFY CHECKSIG.' Satoshi's reply explained the entire design philosophy behind why he'd built it this way.
R to @daily_btc_lore: 3/12 - On June 17, 2010, a user on Bitcointalk asked Satoshi about the cryptic strings visible in Bitcoin transactions — things like 'DUP HASH160 ... EQUALVERIFY CHECKSIG.' Satoshi's reply explained the entire design philosophy behind why he'd built it this way.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 4/12 - The problem he'd solved: without a scripting system, every new transaction type would need its own hardcoded logic. 'It would have been an explosion of special cases,' he wrote. Script let the network evaluate any spending condition generically.
R to @daily_btc_lore: 4/12 - The problem he'd solved: without a scripting system, every new transaction type would need its own hardcoded logic. 'It would have been an explosion of special cases,' he wrote. Script let the network evaluate any spending condition generically.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 5/12 - He'd already baked in what he saw coming: 'Escrow transactions, bonded contracts, third party arbitration, multi-party signature, etc.' All of it had to be designed at the beginning, he wrote, to make sure it would be possible later. He was thinking years ahead.
R to @daily_btc_lore: 5/12 - He'd already baked in what he saw coming: 'Escrow transactions, bonded contracts, third party arbitration, multi-party signature, etc.' All of it had to be designed at the beginning, he wrote, to make sure it would be possible later. He was thinking years ahead.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 6/12 - The bitter irony: just two months after writing this, Satoshi disabled a large chunk of the opcodes he'd described. In August 2010, OP_CAT, OP_MUL, OP_DIV and roughly a dozen others were switched off. The network was too young to risk the attack surface.
R to @daily_btc_lore: 6/12 - The bitter irony: just two months after writing this, Satoshi disabled a large chunk of the opcodes he'd described. In August 2010, OP_CAT, OP_MUL, OP_DIV and roughly a dozen others were switched off. The network was too young to risk the attack surface.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 7/12 - One constraint survived intact and is fundamental: Bitcoin Script is deliberately NOT a full programming language. No loops. No recursion. Every script must terminate. A script that looped forever could cripple every node — so Satoshi made that structurally impossible.
R to @daily_btc_lore: 7/12 - One constraint survived intact and is fundamental: Bitcoin Script is deliberately NOT a full programming language. No loops. No recursion. Every script must terminate. A script that looped forever could cripple every node — so Satoshi made that structurally impossible.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 8/12 - What followed was fifteen years of careful additions. 2012: P2SH let you lock coins behind complex conditions without revealing them upfront. 2015–16: timelocks allowed 'unspendable until this date.' 2017: SegWit restructured how signature data is stored in a block.
R to @daily_btc_lore: 8/12 - What followed was fifteen years of careful additions. 2012: P2SH let you lock coins behind complex conditions without revealing them upfront. 2015–16: timelocks allowed 'unspendable until this date.' 2017: SegWit restructured how signature data is stored in a block.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 9/12 - The biggest upgrade came in November 2021: Taproot. Schnorr signatures let multiple parties merge keys into one indistinguishable on-chain from a single user's. MAST let you embed dozens of spending conditions in one transaction, revealing only the branch actually used.
R to @daily_btc_lore: 9/12 - The biggest upgrade came in November 2021: Taproot. Schnorr signatures let multiple parties merge keys into one indistinguishable on-chain from a single user's. MAST let you embed dozens of spending conditions in one transaction, revealing only the branch actually used.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 10/12 - The practical result: a 3-of-5 corporate multisig, a Lightning channel open, and a simple payment from your phone now all look identical on-chain to a passive observer. Bitcoin Script got more powerful and more private at the same time.
R to @daily_btc_lore: 10/12 - The practical result: a 3-of-5 corporate multisig, a Lightning channel open, and a simple payment from your phone now all look identical on-chain to a passive observer. Bitcoin Script got more powerful and more private at the same time.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 11/12 - Which brings us to now. OP_CAT (one of the opcodes Satoshi disabled in 2010) has been assigned BIP 347 and is being debated for restoration. It would enable 'covenants': conditions restricting not just who spends a coin but what the next transaction can do with it.
R to @daily_btc_lore: 11/12 - Which brings us to now. OP_CAT (one of the opcodes Satoshi disabled in 2010) has been assigned BIP 347 and is being debated for restoration. It would enable 'covenants': conditions restricting not just who spends a coin but what the next transaction can do with it.
Today in Bitcoin History / @daily_btc_lore:
R to @daily_btc_lore: 12/12 - The foundation Satoshi described that day is still there under everything. Whether to build higher on it — and at what risk — is the question Bitcoin is still answering.
Have a favorite Bitcoin history moment? Help me make sure it's in my list and drop it below 👇🧡
R to @daily_btc_lore: 12/12 - The foundation Satoshi described that day is still there under everything. Whether to build higher on it — and at what risk — is the question Bitcoin is still answering.
Have a favorite Bitcoin history moment? Help me make sure it's in my list and drop it below 👇🧡
PyCharm : The only Python IDE you need. | The JetBrains Blog:
Your JetBrains IDE Expertise, Now on LinkedIn
Your JetBrains IDE Expertise, Now on LinkedIn
The JetBrains Blog
Your JetBrains IDE Expertise, Now on LinkedIn - The JetBrains Blog
Connect your IDE to your LinkedIn profile and showcase your JetBrains IDE expertise based on real tool usage.
Kevin Boone's website:
MBook -- a proposal for a new, simple e-book format based on Markdown
MBook -- a proposal for a new, simple e-book format based on Markdown
kevinboone.me
Kevin Boone: MBook
– a proposal for a new, simple e-book format based on Markdown
– a proposal for a new, simple e-book format based on Markdown
Many file formats are suitable for representing e-books, but most are complex, and many are proprietary. This article puts forward a proposal for a new format, somewhat like EPUB, but hugely simplified.
Canal do JB:
O VÍCIO DE REESCREVER O PASSADO
O VÍCIO DE REESCREVER O PASSADO
YouTube
O VÍCIO DE REESCREVER O PASSADO
O vício de reescrever o passado acontece quando uma pessoa revisita constantemente acontecimentos antigos, imaginando como tudo teria sido diferente se outras decisões tivessem sido tomadas. Essa atitude pode gerar arrependimento, culpa e insatisfação com…