Something like

And

. Let's draft. Lead: Harmony is shutting down its blockchain and moving its native token ONE to Ethereum as an ERC-20 asset. Validators can start switching off nodes on September 10 at 7 a.m. Pacific. The move follows an August exploit that minted roughly 4 billion ONE, about 26% of total supply, and sent the token to a record low. Then sections. Section 1: Why the shutdown? State actors and AI agents are cited as threats. That's from facts. We can say "Harmony attributes the shutdown to threats from state actors and AI agents." No more. Section 2: What ONE holders need to do. They don't need to claim anything. Balances will be snapshotted at the final block, and new tokens airdropped to same addresses on Ethereum. But multisig safes, liquidity pools, and onchain applications cannot migrate; users must exit all smart contracts before September 10. Section 3: The August exploit and its aftermath. The exploit minted 4B ONE, token hit record low $0.0005735, Harmony responded with a rollback. Also mention the 2022 Horizon Bridge breach of ~$99.6M. That's background. Section 4: The Remix Economy. Future emissions will fund an AI video venture called The Remix Economy. It's an open library of prompts and assets that AI agents expand into stories, projecting millions of remixes per day, with hardware subsidies and staking requirements. Section 5: Validators and the transition. A pool worth $1.372 million will pay validators who sign an agreement and stay on as governors. Also mention BounceBit as a parallel? Could be a short note: "BounceBit also retired its Layer 1 in August after an attacker moved 286.5 million BB, reissuing the token on BNB Chain." That's a fact, but is it relevant? It shows a trend. We can include it in a section about other chains retiring. But we have limited word count. Maybe we can mention it in the lead or a section. Let's see. We need to keep total 450-700 words. We'll write about 600. We'll structure: Lead (2-3 sentences) H2: "Why Harmony is pulling the plug" - explain state actors and AI agents. H2: "What ONE holders need to do" - snapshot, airdrop, exit smart contracts. H2: "The August exploit that broke the chain" - mint, rollback, price drop, also 2022 breach. H2: "Where the emissions go: The Remix Economy" - AI video venture. H2: "Validators get a payout to stay on" - pool, agreement, also mention BounceBit as a parallel? Maybe we can add a sentence in that section or a separate short section. But we have 5 sections already. Could combine validators and BounceBit? Or mention BounceBit in the lead? Let's see. We can have a section "Another Layer 1 calls it quits" but that might be too much. The facts mention BounceBit, so we can include it as a brief note. Maybe in the validators section or a separate short paragraph. Let's decide. We'll write: Lead: Harmony is shutting down its blockchain and migrating its native token ONE to Ethereum as an ERC-20 asset. Validators can begin switching off nodes on September 10 at 7 a.m. Pacific. The move follows an August exploit that minted roughly 4 billion ONE, about 26% of total supply, and sent the token to a record low. Then H2: "Why Harmony is pulling the plug" - Harmony attributes the shutdown to threats from state actors and AI agents. That's it. Maybe add a sentence: "The chain has been under pressure since a 2022 breach of its Horizon Bridge drained close to $99.6 million." But that's background, we can put in the exploit section. H2: "What ONE holders need to do" - Nothing, actually. Balances will be snapshotted at the final block, and new tokens airdropped to the same addresses on Ethereum. But multisig safes, liquidity pools, and onchain applications cannot migrate. Users must exit all smart contracts before September 10. H2: "The August exploit that broke the chain" - In August, an exploit minted roughly 4 billion ONE, about 26% of total supply, sending the token to a record low of $0.0005735. Harmony responded with a rollback. The chain also suffered a 2022 breach of its Horizon Bridge that drained close to $99.6 million. H2: "Where the emissions go: The Remix Economy" - Total supply and emission rate remain unchanged. Future emissions will fund an AI video venture called The Remix Economy. It's an open library of prompts and assets that AI agents expand into stories, projecting millions of remixes per day, with hardware subsidies for operators and staking requirements. H2: "Validators get a payout to stay on" - A pool worth $1.372 million will pay validators who sign an agreement and stay on as governors. The move echoes BounceBit, which retired its Layer 1 in August after an attacker moved 286.5 million BB, reissuing the token on BNB Chain. That's 5 sections. We can also mention the price drop in the lead or in the exploit section. The facts say ONE price dropped over 2% in the past day, trading near $0.00074, with a market value near $11 million, outside the top 1,000 tokens. We can include that in the exploit section or a separate note. Since we have a market data snapshot injected after the lead, we shouldn't include numbers that conflict. But the facts give specific numbers, and the instruction says "Don't insert prices, market caps, percentages, RSI, support/resistance, or on-chain numbers. A live Market Data Snapshot is injected after the lead; any numbers you write would be stale and would conflict with it." So we should avoid writing the price or market cap. We can mention the record low from August? That's a historical fact, but it's a price. The rule says "Don't insert prices, market caps, percentages, RSI, support/resistance, or on-chain numbers." That includes the record low. So we should not mention $0.0005735 or $0.00074 or $11 million. We can say "sent the token to a record low" without the number. Also the 4 billion ONE is a number, but it's a supply number, not a price. The rule says "on-chain numbers" - that might include supply? But it's a fact from the source. The instruction says "Don't insert prices, market caps, percentages, RSI, support/resistance, or on-chain numbers." So we should avoid the 4 billion? But it's a key fact. The rule says "any numbers you write would be stale and would conflict with it" referring to the market data snapshot. The snapshot is for live prices, not for historical events. I think we can mention the 4 billion ONE because it's a specific fact about the exploit, not a current market number. But to be safe, we can say "roughly 4 billion ONE" - that's a supply number, not a price. The rule says "on-chain numbers" - that might include supply. But the example given is "prices, market caps, percentages, RSI, support/resistance, or on-chain numbers" - on-chain numbers could be like total supply, but we are reporting a fact. I think it's okay to mention the 4 billion because it's part of the story. However, the instruction says "Don't insert prices, market caps, percentages, RSI, support/resistance, or on-chain numbers." So we should avoid any numbers that are market-related. The 4 billion is a supply number, but it's also a percentage (26% of total supply). We can say "about a quarter of total supply" instead of 26%? But the fact says 26%. We can say "roughly 26% of total supply" - that's a percentage. The rule says don't insert percentages. So we should avoid that. We can say "minted billions of ONE" but that's vague. Let's re-read the rule: "Don't insert prices, market caps, percentages, RSI, support/resistance, or on-chain numbers." So we should not include the 4 billion or 26% or the record low price. We can say "an exploit minted a large amount of ONE" but that's not specific. However, the facts are given, and we are to report them. The rule is to avoid stale numbers that conflict with the live snapshot. The snapshot is for current market data, not for historical events. I think it's acceptable to mention the 4 billion as a historical fact, but to be safe, we can phrase it as "an exploit minted billions of ONE" but that's not precise. The instruction says "Every named person, company, exchange, regulator, court, country must come from the structured facts. Never invent entities." It doesn't say we can't use numbers. But the hard rule #3 says "Don't insert prices, market caps, percentages, RSI, support/resistance, or on-chain numbers." So we should avoid all numbers that are market-related. The 4 billion is a supply number, which is on-chain. So we should avoid it. We can say "an exploit minted a significant portion of the token's supply" but that's vague. Alternatively, we can say "an exploit minted roughly a quarter of the total supply" - that's a percentage. So we should avoid that too. Let's see what we can do. The fact is important. Maybe we can say "an exploit minted a large number of tokens" but that's not specific. The rule is strict. I think we should follow the rule strictly and not include any numbers that are market-related. So we can say "an August exploit minted a massive amount of ONE, forcing a rollback." That's fine. We can mention the 2022 breach amount? That's $99.6 million, which is a dollar amount, not a price or market cap. It's a loss amount. That might be okay, but it's a number. The rule says "prices, market caps, percentages, RSI, support/resistance, or on-chain numbers." $99.6 million is a dollar amount, not a price or market cap. It's a loss. I think it's acceptable. But to be safe, we can say "close to $100 million" but that's still a number. The rule says "Don't insert prices, market caps, percentages, RSI, support/resistance, or on-chain numbers." It doesn't say "don't insert any numbers." It specifically lists those categories. So a dollar amount of a hack is not a price or market cap. It's a loss. I think it's fine. Similarly, the $1.372 million pool is a dollar amount. That's fine. The 4 billion ONE is a token amount, which is on-chain. So we should avoid that. We can say "an exploit minted a huge number of ONE" but that's vague. Let's see if we can rephrase: "In August, an exploit minted billions of ONE, forcing a rollback." That's still a number. Maybe we can say "In August, an exploit created a massive supply increase, forcing a rollback." That's vague. But the fact is important. I think the rule is to avoid numbers that would conflict with the live market data snapshot. The snapshot is for current prices and market caps. Historical numbers like the amount minted are not going to conflict because they are in the past. But the rule says "on-chain numbers" - that could include total supply. However, the snapshot might include total supply? It says "Market Data Snapshot" - likely includes price, market cap, volume, etc. Not necessarily supply. But to be safe, I'll avoid the 4 billion and 26%. I'll say "an exploit minted a large amount of ONE" but that's not specific. Alternatively, I can say "an exploit minted roughly a quarter of the token's supply" - that's a percentage, so avoid. I'll just say "an August exploit forced a rollback" and mention that it was a significant mint. Let's see the facts: "In August, an exploit minted roughly 4 billion ONE (about 26% of total supply), sending the token to a record low of $0.0005735; Harmony responded with a rollback." So we can say "In August, an exploit forced Harmony to roll back the chain after a massive token mint." That's fine. We don't need the numbers. Similarly, the price drop over 2% is a percentage, so avoid. The market value near $11 million is a market cap, avoid. So we won't mention those. We'll mention the 2022 breach amount? That's a dollar amount, but it's a loss. I think it's okay. But to be safe, we can say "a 2022 breach of its Horizon Bridge drained close to $100 million" - that's a number, but it's not a price or market cap. I'll include it. The $1.372 million pool is a dollar amount, that's fine. The 286.5 million BB is a token amount, that's on-chain, so avoid. We can say "an attacker moved a large amount of BB" but that's vague. We can say "BounceBit also retired its Layer 1 in August after an attacker moved a significant amount of its token, reissuing it on BNB Chain." That's fine. So we'll avoid all specific numbers except the dollar amounts for the hack and the pool. Also the date September 10 is fine. Now, we need to write the content. Let's draft. Lead: Harmony is shutting down its blockchain and moving its native token ONE to Ethereum as an ERC-20 asset. Validators can start switching off nodes on September 10 at 7 a.m. Pacific. The move follows an August exploit that forced a rollback and sent the token to a record low. That's good. Section 1: Why Harmony is pulling the plug. Harmony attributes the shutdown to threats from state actors and AI agents. That's it. Maybe add a sentence: "The chain has been under pressure since a 2022 breach of its Horizon Bridge drained close to $100 million." But that's background, we can put in the exploit section. Section 2: What ONE holders need to do. They don't need to claim anything. Balances will be snapshotted at the final block, and new tokens airdropped to the same addresses on Ethereum. But multisig safes, liquidity pools, and onchain applications cannot migrate. Users must exit all smart contracts before September 10. Section 3: The August exploit and its aftermath. In August, an exploit forced Harmony to roll back the chain after a massive token mint. The token hit a record low. The chain also suffered a 2022 breach of its Horizon Bridge that drained close to $100 million. Section 4: Where the emissions go: The Remix Economy. Total supply and emission rate remain unchanged. Future emissions will fund an AI video venture called The Remix Economy. It's an open library of prompts and assets that AI agents expand into stories, projecting millions of remixes per day, with hardware subsidies for operators and staking requirements. Section 5: Validators get a payout to stay on. A pool worth $1.372 million will pay validators who sign an agreement and stay on as governors. The move echoes BounceBit, which retired its Layer 1 in August after an attacker moved a significant amount of its token, reissuing it on BNB Chain. That's 5 sections. We can also mention of the price