“
we pay miners to perform correct, honest transaction confirmations. We don’t pay them to decide the rules, we pay them to follow the rules. The rules are decided collectively by everyone, you and me, by running our Bitcoin software of choice.
“
@kallerosenbaum
@nodesignal
Mega episode!
If you care about Bitcoin, then you need to hear this carefully.
https://anchor.fm/nodesignal/episodes/Nodesignal-Buchclub---E12---Grokking-Kalle-e1s80u
Sorry. Somehow the link is wrong 😕
@nodesignal
Mega episode!
If you care about Bitcoin, then you need to hear this carefully.
https://anchor.fm/nodesignal/episodes/Nodesignal-Buchclub---E12---Grokking-Kalle-e1s80u
I’m not sure about that.
What is the “core design”?
If that is also the block size, then that statement is not true anymore.
That’s not true anymore.
E.g. ASICs
At that time Bitcoin nodes could act as archival node, mine node and user access to transaction propagation in one system (machine).
Since then the game theory has changed.
🤣 also in Bitcoin space
SegWit + Taproot: policy making
Ord/Inscriptions: „that‘s not what that policy was meant for” 😂
Focus on the signal!
Not on the noise
Try harder
#[0] und #[1] stöbern in der Geschichte und in Büchern von einigen Denkern vergangener Zeit, die wenig bis selten erwähnt oder anderen bekannten Denkern aufgegriffen wurden. Viel Spaß mit diesem Deep Dive in die Geschichte:
https://nodesignal.space/2023/03/04/nodesignal-talk-e108-vergessene-denker/
Dieses Buch: Das kalte Herz geht auch in die Geschichte. Man kann eine Menge lernen. Bitcoin null erwähnt, aber Bitcoin kompatibel. ;)
note1x97ercgwyn7zdvsf3tg0gd6f96cdmf4dv8dzpsgz27vrah45vxxs4lee0l
1. The Taproot upgrade in 2021 removed the data limit entirely, as long as it fits inside a block. Segregated Witness (Segwit) software upgrade in 2017 allows up to 3MB of witness data to be stored ‘outside’ of the 1MB block limit. Together, they provide up to 4MB worth of storage space for the inscription content.
2. Inscriptions are stored in an “envelope” between Opcodes OP_IF and OP_ENDIF. OP_FALSE precedes OP_IF to ensure that this data is never actually used in script execution and does not take up stack space. No OP_RETURN is used, and the output containing an inscription is spendable and thus unprunable.
Ordinals and Fungibility:
TLDR: “[…] could transitively harm privacy on the bitcoin network […]”