What the proposal does
...
SharpLink's objection
...
The announcement
...
Next steps
...
Or we can combine some sections. We'll write: Lead: SharpLink has come out against EIP-8363, a draft Ethereum proposal that would burn a portion of validator rewards as the network's staking ratio climbs. Joseph Chalom announced the firm's opposition on X on Friday, targeting the so-called "Tapered Issuance Burn" proposal. Then section 1: "How the burn would work" - explain. Section 2: "Why it's contentious" - we can say the proposal reduces net rewards for validators, and that's the obvious point of tension. We can also note that the change is phased in, but details are incomplete. Section 3: "SharpLink's public stance" - describe the announcement, no further detail. Section 4: "What happens now" - the proposal is a draft, no timeline, the debate will continue. We'll write with varied sentences. Let's draft. Title: "SharpLink Opposes Ethereum Proposal to Burn Validator Rewards" - that's factual. Slug: "sharplink-opposes-ethereum-proposal-burn-validator-rewards" Subtitle: "Joseph Chalom announced the firm's stance on X on Friday, pushing back on EIP-8363." Meta description: "SharpLink publicly opposed EIP-8363, a draft Ethereum proposal that would burn validator rewards as staking ratio climbs. Joseph Chalom announced the stance on X on Friday." Keywords: ["SharpLink", "EIP-8363", "Ethereum", "validator rewards", "staking"] FocusKeyword: "EIP-8363" We'll set readability wordCount to actual count, readingTime based on 200 wpm. Let's write the content. I'll write:SharpLink has come out against EIP-8363, a draft Ethereum proposal that would burn a portion of validator rewards as the network's staking ratio climbs. Joseph Chalom announced the firm's opposition on X on Friday, making SharpLink an early named opponent of the so-called "Tapered Issuance Burn."
Wait, "early named opponent" - we don't know if early. We'll say "announcing the firm's opposition" without "early." Better: "SharpLink is pushing back on EIP-8363, a draft Ethereum proposal that would burn a portion of validator rewards as the network's staking ratio climbs. Joseph Chalom announced the firm's opposition on X on Friday, targeting the so-called 'Tapered Issuance Burn' proposal." Then:How the burn would work
EIP-8363, titled "Tapered Issuance Burn," is a draft Ethereum improvement proposal. It would burn part of validator rewards as the ratio of staked ETH rises. The change is phased in gradually, according to the draft, though the exact schedule isn't specified. The goal is to slow the growth of ETH supply as more coins get locked up in staking.
Why it's contentious
The proposal directly cuts what validators earn. As the staking ratio climbs, a larger slice of rewards gets burned, so net issuance drops. That means less income for anyone running staking operations or delegating ETH. For a firm like SharpLink, which is publicly opposing the plan, the mechanics are the obvious sticking point.
Wait, we don't know SharpLink runs staking operations. We can say "for staking participants" instead. And "which is publicly opposing" - that's fine. We'll rephrase: "For staking participants, the effect is straightforward: the more ETH staked, the more rewards get burned, and the less validators take home. That's the core tension the proposal creates." That avoids attributing to SharpLink. We'll write: "The proposal directly cuts what validators earn. As the staking ratio climbs, a larger slice of rewards gets burned, so net issuance drops. For anyone staking ETH, that means less income over time. The mechanism is the likely source of SharpLink's objection, though the firm didn't offer additional reasoning in Friday's announcement." But we don't know if they didn't offer reasoning. We can say "though the announcement didn't include further reasoning" - but we don't know. We can say "The announcement didn't spell out the firm's full rationale." But again, we don't know if they did. To be safe, we can say "The announcement gave no further details on the firm's reasoning." That's a negative claim, but it's plausible we can say "gave no further details" because we only have the fact that they announced opposition, no other details. But it's still an assertion about absence. We can phrase as "The post announced the opposition without going into specifics." That's a description of what we know: we know they announced opposition, and we don't know of any specifics, so it's safe to say "without going into specifics" because we have no specifics in the facts. That's fine. So: "The post announced the opposition without going into specifics." Then:The announcement
Chalom's X post on Friday was brief. It stated SharpLink's opposition to EIP-8363 and pointed to the proposal's name. No alternative plan or counter-proposal was mentioned. The post didn't include a timeline for further action.
Again, we don't know if it was brief. We can say "Chalom's X post on Friday announced the opposition. It didn't mention any alternative plan or counter-proposal." That's a negative claim but based on lack of info. We'll keep it.Next steps
EIP-8363 remains a draft, so it hasn't been scheduled for any network upgrade. Ethereum improvement proposals typically go through a review process before any decision. The staking ratio is a live metric, so the proposal's impact would grow over time if adopted. SharpLink's public opposition adds a voice to the debate, but the final call rests with the Ethereum ecosystem.
We need to be careful with "typically go through a review process" - that's general knowledge, but we can say "Ethereum improvement proposals go through a review process before any network upgrade" - that's factual. We'll keep it. We'll also note that the details of the phase-in are incomplete, which we already did. Now we need to ensure we don't use forbidden phrases. We have "so-called" - that's fine. We have no rhetorical questions, no "furthermore", etc. We'll check word count. Let's count: Lead (2 sentences) about 40 words. Then sections. Let's write the full content. I'll produce the JSON. Title: "SharpLink Opposes Ethereum Proposal to Burn Validator Rewards" Slug: "sharplink-opposes-ethereum-proposal-burn-validator-rewards" Subtitle: "Joseph Chalom announced the firm's stance on X on Friday, pushing back on EIP-8363." Meta description: "SharpLink publicly opposed EIP-8363, a draft Ethereum proposal that would burn validator rewards as staking ratio climbs. Joseph Chalom announced the stance on X on Friday." Keywords: ["SharpLink", "EIP-8363", "Ethereum", "validator rewards", "staking"] FocusKeyword: "EIP-8363" Readability: we'll compute word count. Let's write the content HTML.SharpLink is pushing back on EIP-8363, a draft Ethereum proposal that would burn a portion of validator rewards as the network's staking ratio climbs. Joseph Chalom announced the firm's opposition on X on Friday, targeting the so-called "Tapered Issuance Burn" proposal.
How the burn would work
EIP-8363, titled "Tapered Issuance Burn," is a draft Ethereum improvement proposal. It would burn part of validator rewards as the ratio of staked ETH rises. The change is phased in gradually, according to the draft, though the exact schedule isn't specified. The goal is to slow the growth of ETH supply as more coins get locked up in staking.
Why it's contentious
The proposal directly cuts what validators earn. As the staking ratio climbs, a larger slice of rewards
