Polymarket has taken action after identifying users who allegedly pressured an Israeli journalist to alter coverage of an Iranian missile strike that became the subject of a high-stakes prediction market. Emanuel Fabian, the military correspondent for The Times of Israel, said he began receiving messages urging him to rewrite his March 10 report about a missile that landed near Beit Shemesh. The market around Iran’s strike had drawn significant attention, with more than $17 million wagered on whether the event would occur on that date. In response to the harassment, Polymarket said it banned the involved accounts and would forward information to authorities as part of its enforcement of the platform’s Terms of Service.

Key takeaways

• Polymarket publicly banned accounts tied to attempts to influence editorial coverage of a war-related event.
• The Beit Shemesh incident sparked discussion about the alignment of journalism, prediction markets, and user incentives, given the roughly $17 million at stake on the March 10 date.
• Journalists reported receiving death threats and coercive messages aimed at changing coverage, leading to police involvement in the investigation.
• Experts and lawmakers have warned that open war and political markets can create incentives for insider manipulation or abuse, adding regulatory scrutiny to the sector.
• Interference allegations surfaced as market participants debated the event’s outcome and how market rules defined a valid strike versus an intercepted one.

Market context: Prediction markets around geopolitical events have surged in activity, attracting capital and attention but also drawing scrutiny from lawmakers who caution that such markets can incentivize manipulation or insider trading. The episode underscores ongoing debates about regulation, accountability, and the safeguards needed to protect both journalists and participants while preserving the informational value of these markets.

Why it matters

The episode sits at the intersection of journalism, technology platforms, and financial markets that attempt to forecast real-world events. It highlights the vulnerabilities reporters face when their work intersects with open, global betting markets. Polymarket’s swift action—banning accounts implicated in intimidation and promising to share data with authorities—signals an(self) effort to deter harassment while maintaining a level of accountability for participants who attempt to shape coverage for personal gain. The incident also raises practical questions for platform design: how to verify events, resolve disputes when official narratives diverge, and deter abusive behavior without stifling legitimate speculation.

From a market-design perspective, the case emphasizes how event definitions and payout rules can become contentious when the public narrative contradicts initial reports. The market in question stipulated that a “Yes” resolution would occur if Iran initiated a drone, missile, or air strike on Israeli soil on the listed date, with exceptions for missiles or drones that were intercepted. Such clauses matter greatly as information evolves and as authorities confirm or dispute particular details. The controversy illustrates the delicate balance between price discovery and the integrity of editorial content, especially in fast-moving conflicts where new information can quickly alter the perceived probability of an outcome.

Regulatory and legislative attention surrounding prediction markets has grown in recent years. Critics argue that a widely followed war-related market can create incentives for insiders to profit from confidential or strategic information, potentially harming the market’s integrity. Lawmakers have proposed or introduced measures aimed at increasing oversight and reducing opportunities for manipulation. In this environment, Polymarket’s actions—such as banning participants and cooperating with authorities—are part of a broader push to establish guardrails while preserving the utility of open, decentralized forecast platforms.

The Israel-Beit Shemesh episode also reinforces how journalism and real-time events can interact with online betting ecosystems. A journalist’s safety can become a concern when gigabytes of data and real-time bets converge with heated debates over national security. In this case, Fabian reported receiving messages in Hebrew from an individual who threatened harm should he alter the article, a reminder that the digital amplification of conflict can translate into tangible risks for reporters. The police investigation underscores that, beyond market mechanics, these threats are taken seriously by authorities and investigated through formal channels.

As the discourse evolves, platforms like Polymarket are likely to face ongoing scrutiny over how they moderate content, enforce terms of service, and guard against attempts to influence public reporting. The balance between encouraging open discourse and protecting participants—and journalists—from coercion is delicate, and the incident adds to a growing discourse on how best to govern and supervise prediction markets without dampening their potential for information discovery.

What to watch next

• Updates from police on the investigation into the threats against Emanuel Fabian and any legal actions taken.
• Polymarket’s next steps regarding moderation policies, account bans, or changes to event-market rules following the incident.
• New information about the Iran–Israel market’s March 10 resolution and how different outlets corroborate the event outcome.
• Regulatory developments or proposed legislation targeting prediction markets and their handling of geopolitical bets.

Sources & verification

• Times of Israel report by Emanuel Fabian detailing threats and pressure to alter coverage of the March 10 incident.
• Polymarket event page for the Iran strikes Israel on market.
• Polymarket statement condemning harassment posted on X.
• Emanuel Fabian’s tweet from March 10, 2026 embedded in the coverage.
• Times of Israel update confirming the missile outside Beit Shemesh was not intercepted, as reported by Fabian.
• Cointelegraph coverage on related Polymarket trades and arrests.

Beit Shemesh episode and the stakes for prediction markets

The Beit Shemesh incident centers on a clash between the ambition of market-based forecasting and the realities of reporting on armed conflict. Polymarket’s market on Iran’s strike attracted substantial capital, illustrating how participants extrapolate geopolitical risk into financial bets. The protracted tension between a journalist’s independence and the expectations of a global betting audience became palpable as individuals on social media and messaging channels urged Fabian to change the narrative to favor a particular market outcome. The prompt action by Polymarket—to ban the involved accounts and cooperate with authorities—highlights a broader effort by platform operators to deter abuse and maintain trust in the reliability of the market data they produce.

Meanwhile, the evolving official narrative around March 10’s events adds another layer of complexity. Early investor sentiment and public commentary can diverge from later assessments of what occurred, such as whether missiles were intercepted or landed as described. The distinction matters for the market’s payout logic, and it also raises questions about how platforms should handle disputed or evolving information. As authorities continue to investigate and as more details become available, the episode will likely inform ongoing debates about the governance of prediction markets and their role in risk pricing during geopolitical crises.

Beyond the mechanics, the episode underscores the need for robust protections for journalists who operate under the glare of online betting communities. It also spotlights the responsibilities of market operators to police conduct and to implement clear, enforceable policies that safeguard editorial integrity while preserving a platform’s openness. The path forward will likely involve refinements to event definitions, stronger identity and abuse prevention measures, and transparent reporting on enforcement actions—elements that can help sustain the usefulness of prediction markets without compromising safety or ethics.

The broader conversation about how to balance free inquiry, market liquidity, and the well-being of reporters is far from settled. As prediction markets mature, observers will watch not only for accurate price signals but also for how platforms handle threats, disputes, and regulatory expectations. The Beit Shemesh incident thus stands as a case study in the intersection of journalism, technology-enabled forecasting, and the high-stakes world of geopolitics.

Spark Protocol is moving to reactivate Wrapped Bitcoin (WBTC) collateral support on SparkLend and expand its liquidity layer infrastructure, according to a proposal published Monday. The changes include re-enabling WBTC collateral functionality, adding USDT and USDT transfer asset rate limits to Anchorage, and onboarding a Uniswap v4 USDT/USDS pool. The proposal also covers Spark Treasury grants for Q2 2026.

WBTC collateral support was disabled in late 2024 due to governance and custody concerns in the WBTC ecosystem. The asset has now operated under the updated structure for approximately 1.5 years without incident, prompting the Spark Foundation to reassess its risk profile for re-listing on the protocol.

Sources: Sky Forum – Proposed Changes to Spark | Sky Forum – WBTC Asset Review

This article was generated automatically by The Defiant’s AI news system from publicly available sources.

The U.S. Securities and Exchange Commission has dropped a multi-year case against Nader Al‑Naji, who had been accused of misleading investors and violating federal securities laws tied to the launch of the BitClout platform.

A joint stipulation of dismissal filed with the United States District Court for the Southern District of New York on Thursday said the SEC’s crypto task force had reassessed the matter and decided to end the litigation.

However, the filing warned that the decision should not be interpreted as a broader policy shift that would automatically extend to other crypto-related cases.

“The Commission’s decision to exercise its discretion and seek dismissal of this litigation is based on the particular facts and circumstances of this case,” the filing said.

Al-Naji, a former Google engineer and the founder of the DeSo blockchain, was first charged by the SEC in 2024, just years after launching BitClout in March 2021. Subsequently, a cease and desist order was issued against the platform.

In its complaint at the time, the SEC under former chair Gary Gensler accused Al-Naji of raising more than $257 million by selling BitClout’s native BTCLT token without properly disclosing that the proceeds could be used to pay BitClout team members.

The commission also accused Al-Naji of using funds raised from investors to finance a lavish personal lifestyle. According to the SEC, roughly $7 million of the proceeds were used to cover rent for a Beverly Hills mansion and to make cash gifts to family members. 

Regulators further alleged that Al-Naji mischaracterized the inner workings of the platform by presenting BitClout as fully decentralized even though he was allegedly controlling the project behind the scenes.

Under the terms of the settlement, the case has now been dismissed with prejudice, and Al-Naji has agreed to waive any claims for reimbursement of legal fees or expenses from the SEC.

Simultaneously, the U.S. Department of Justice has also ended a parallel criminal case against Al-Naji that had accused him of wire fraud.

“After months of searching, using every method and tool at their disposal, including applying pressure to those around me, the government decided to dismiss their charges,” Al-Naji wrote in an X post.

“Perhaps the allegation that hurt the most was the government’s claim that BitClout/DeSo, the blockchain that I’ve been working on for years now, is not fully decentralized […] In the short term, I’ve got big plans for DeSo, Focus, Openfund, and HeroSwap (my team’s core products). Every single one is best in class at what it does and a potential billion dollar business on its own. Now that I’m able to operate at full capacity, free from stifling constraints, and with my reputation and network restored, I’m confident we’ll realize that potential,” he added.

Under President Donald Trump’s administration, the SEC has dropped several enforcement actions against crypto firms. At the same time, the agency’s crypto task force has said it intends to move away from regulation by enforcement and toward a more collaborative framework built around clearer rules for digital asset companies.

Earlier this month, the SEC also dropped its lawsuit against Justin Sun, which had accused the TRON founder of fraud and securities law violations.

Aave announced the launch of ‘Aave Shield,’ a new protective measure, following a $50 million loss suffered by a trader during a token swap. In a post-mortem analysis, Aave clarified that the loss was caused not by slippage but by illiquid market conditions that decimated the trade’s execution price when the trader swapped USDT for AAVE tokens.

The incident occurred on March 12, 2026, when a trader attempted to exchange $50.4 million in USDT stablecoins but received only $39,000 worth of AAVE tokens, crystallizing a near-total loss. The launch of Aave Shield signals the protocol’s effort to prevent similar catastrophic trades by adding safeguards around illiquid or thin markets.

Sources: Aave

This article was generated automatically by The Defiant’s AI news system from publicly available sources.

Nonfungible token marketplace OpenSea has postponed the launch of its native token SEA, initially slated for March 30, citing tough market conditions and it not being market-ready.

“The reality is that market conditions are challenging across crypto right now, and $SEA only launches once,” OpenSea CEO Devin Finzer posted to X on Monday. 

The OpenSea (SEA) token, announced in October, was touted as part of OpenSea’s plan to transition into a “trade everything” app across multiple chains, which includes perpetual futures. 

The SEA token would enable discounted trading fees to users on this platform, in addition to offering creator incentives and community voting. OpenSea users will also be able to stake SEA tied to NFT tokens and collections. 

However, Finzer said OpenSea wants to make sure “every piece is in place” before launching the token rather than to “force the original date.” There is no new target date for the SEA launch.

Since October, OpenSea users have participated in the “Waves” reward program to be eligible for SEA token allocation. Finzer said that the campaign will be ending.

He also noted that users who participated in Waves 3, 4, 5 and 6 campaigns can opt to receive refunds for the platform fees OpenSea retained during that period, though anyone taking up the option would also lose any Treasure Chest rewards they have earned. Treasures were point-like rewards that OpenSea users earned to win certain prizes.

The move has prompted some users to question why OpenSea did not make refunds available for Wave 1 and 2 participants.

Dune Analytics shows that OpenSea’s token and NFT volume hit a four-year peak of $3.3 billion in October, which coincided with Wave 1 (which ran Sept. 15 to Oct. 15), and then hit $705 million in November, coinciding with Wave 2 (which ran from Oct. 15 to Nov. 15).

Cointelegraph reached out to OpenSea for comment.