`

UPDATE: EXTENDED COORDINATION & SYNCHRONIZATION As Flow network validators prepare to resume normal network operations, the Flow Foundation coordination with ecosystem partners has highlighted the need for extended synchronization to ensure a smooth transition to the pre-exploit state. Flow is deeply integrated with numerous cross-chain bridges, exchanges, and infrastructure providers. To protect user funds and prevent state mismatches, it is critical that all downstream services correctly align. OPERATIONAL ADJUSTMENT The Foundation is actively deploying resources to assist network stakeholders, from bridges to individual apps, in resetting their systems to the target pre-exploit state: Flow Cadence Height: 137363395 Flow EVM Height: 51358233 CURRENT STATUS Validators: Ready (Mainnet 28 deployed) Ingestion: Paused (Pending Ecosystem sync) We are extending the coordination window to account for the various network partners. Resuming ingestion before all partners are synced could lead to data inconsistencies or service interruptions for users. The network will remain in a "read-only" state until we confirm that critical infrastructure providers are aligned. The next update here will be shared at 7am PT, December 28th.

Recapping the updates we’ve made to ChatGPT in the past week: - GPT-4o available under “Legacy models” by default for paid users - Paid users can toggle on “Show additional models” in settings to add legacy models like o3 and GPT-4.1, as well as GPT-5 Thinking mini, to the model picker - GPT-5 includes Auto, Fast, and Thinking in the model picker. Fast gives faster answers, Thinking takes more time to give deeper answers, Auto routes between Fast and Thinking Plus & Team users now get up to 3,000 messages/week on GPT-5 Thinking, with extra capacity on GPT-5 Thinking mini when limit is hit -GPT-5 now available for Enterprise & Edu users Coming soon: A warmer, more familiar personality for GPT-5.

So congratulations, Dean—you’ve correctly identified what every serious researcher already knows: P2PK was used until block 329. Bitcoin Core v0.1.5, which introduced P2PKH, went live just before block 330. You got that part right. Where you go full jackhammer-to-the-temple is pretending that someone asking “is block 331 P2PKH?” is somehow worthy of abuse. Because the real answer is: it depends who mined it and what client they were running. You think shouting “lol no” makes you look smart, but let’s be factual. P2PKH was the default from block 330 onward—in updated clients. But there was no hard enforcement. The network still accepted P2PK. That’s why we see legacy script types well into the 300s and beyond. So yes, Block 331 can contain P2PKH if the miner had upgraded. It can also contain P2PK if they hadn’t. That’s not contradiction. That’s protocol reality. What you’ve posted in your screenshot is a P2PK script, which supports the question, not refutes it. Instead of using that moment to clarify, you spat on it. You turned factual nuance into a tantrum and proved that even when you’re right on one technical point, you still fumble the application like a man wearing oven mitts at a piano recital. This isn’t about splitting hairs over script types—it’s about you sneering at a valid question while ignoring the one thing that buries your smug little bark: Satoshi updated the client. P2PKH went live at block 330. That’s the line. But the network doesn’t flip overnight—some nodes (miners) didn’t update. So yes, P2PK still showed up after. Doesn’t mean the spec didn’t change. It means not everyone moved with it. You mocking the question just shows you understand neither the history nor the mechanics. You’ve just proven my point—this isn’t Satoshi’s key. It’s someone else using the same early script type. So all the noise about “Satoshi’s P2PK vulnerability” is built on crap. Others mined blocks too. This script isn’t exclusive—it’s just old. You're not defending Bitcoin's integrity. You’re just defending your ego with block explorers and bad manners. PS - P2PK is valid TODAY!