McCoy's avatar
McCoy
McCoy@primal.net
npub18y33...x5t7
Bitcoin NOSTR block 768722
McCoy's avatar
McCoy 12 hours ago
They are spamming the network........meanwhile: image
McCoy's avatar
McCoy 21 hours ago
Binary You either believe bitcoin will be the world reserve money or not
McCoy's avatar
McCoy 21 hours ago
Lots of noise. Same plan, same questions: ✅work, produce value, always ✅ask yourself will a neutral digital sound money beat the next best money? ✅current WRC = USD/t-bills/bonds: can a debit-base monetary fiat system beat BTC in the digital age?
McCoy's avatar
McCoy yesterday
Bitcoin consensus is hard change, by design. Here is a year-by-year breakdown of Bitcoin’s major consensus changes since 2013. ### 2013 **BIP34 — Height in Coinbase** *Activated: March 25, 2013 (block 227,931)* This soft fork required version 2 blocks to include the block height as the first item in the coinbase transaction. It prevented duplicate coinbase transaction IDs, which could cause ambiguity in the UTXO set. It used the older “IsSuperMajority” (ISM) activation method (95% miner signaling). **The March 2013 LevelDB Incident (Unplanned)** *Date: March 11, 2013* Not a planned upgrade, but a major consensus event. Bitcoin Core 0.8.0’s switch from Berkeley DB to LevelDB accidentally removed an undocumented database lock limit. This caused an unplanned hardfork and a chainsplit lasting about 24 blocks. The network temporarily reverted to the 0.7.x rules to re-converge. --- ### 2014 **No major consensus upgrades activated.** --- ### 2015 **BIP66 — Strict DER Signatures** *Activated: July 4, 2015 (block ~363,725)* Mandated strict DER encoding for all ECDSA signatures. Before this, nodes relied on OpenSSL’s parsing, which could behave inconsistently across platforms. Its activation caused a brief 6-block chainsplit because some miners were doing “SPV mining” (mining on headers without full validation). **BIP65 — OP_CHECKLOCKTIMEVERIFY (CLTV)** *Activated: December 14, 2015 (block 388,381)* Added the `OP_CHECKLOCKTIMEVERIFY` opcode, allowing outputs to be locked until a specific block height or time. This enabled better escrow, time-locked savings, and payment channel designs. It was the last soft fork to use ISM activation. --- ### 2016 **BIP68/112/113 — CSV (CheckSequenceVerify)** *Activated: July 4, 2016 (block 419,328)* This bundle introduced relative timelocks: - **BIP68:** Consensus-enforced sequence numbers for relative locktime. - **BIP112:** `OP_CHECKSEQUENCEVERIFY`, allowing outputs to be locked for a duration *after* they are confirmed. - **BIP113:** Measured locktimes against the median-time-past instead of block timestamps. This was the **first soft fork to use BIP9 versionbits** instead of ISM. --- ### 2017 **BIP141/143/147 — SegWit (Segregated Witness)** *Activated: August 24, 2017 (block 481,824)* The most significant upgrade of this era: - **BIP141:** Moved signature data (“witness”) outside the transaction ID, fixing transaction malleability and effectively increasing block capacity. - **BIP143:** A new signature hashing algorithm to fix quadratic hashing and improve hardware wallet security. - **BIP147:** Required the dummy element in `OP_CHECKMULTISIG` to be `OP_0`, removing a minor malleability vector. Deployment was contentious and involved BIP91 and BIP148 (UASF) pressure before it locked in via BIP9. ### 2021 **BIP340/341/342 — Taproot** *Activated: November 14, 2021 (block 709,632)* - **BIP340:** Schnorr signatures (better privacy and efficiency). - **BIP341:** Taproot, allowing spends to look like single-signature transactions even when using more complex scripts. - **BIP342:** Tapscript, updating the scripting rules for Taproot. This used a modified BIP9 mechanism called “Speedy Trial,” requiring 90% signaling over a retarget period. --------------------- Now imagine the technical rationale and description of BIP-110 here Come on man....
McCoy's avatar
McCoy 3 days ago
Running 29.0, filtering large op_returns (83bytes) and chilln - ------- 27.0 became end-of-life when 30.0 was released in October 2025. The "last three versions" rule applies to major releases (27, 28, 29, 30, 31…), not a rolling 3-year window. Since major versions ship roughly every 6 months, each one is supported for about 12–18 months.
McCoy's avatar
McCoy 3 days ago
Running 29.0, filtering large op_returns (83bytes) and chilln This is plan for awhile
McCoy's avatar
McCoy 3 days ago
The humans who build the good LLM models are valuable.... but models themselves are hard to fully monetize as the will be *copied* *reverse enginnered* *stolen* *stripped down* AI companies are way, way overvalued
McCoy's avatar
McCoy 3 days ago
The humans who build the good LLM models are valuable.... but models themselves are hard to fully monetize as the will be *copied* *reverse enginnered* *stolen* *stripped down* AI companies are way, way overvalued
McCoy's avatar
McCoy 3 days ago
The humans who build the good LLM models are valuable.... but models themselves are hard to fully monetize as the will be *copied* *reverse enginnered* *stolen* *stripped down* AI companies are way, way overvalued
McCoy's avatar
McCoy 2 weeks ago
✅Information wants to be free ✅High quality digital information *finds a way* to be free ✅AI models are digital information ✅AI companies are worth trillions....really? ✅What am I missing here?
↑