Explore Hub: Protocol Launches

Story's official DATA Foundation blog listed a June 25, 2026 announcement saying Story is becoming The DATA Foundation, IP becomes DATA, and Story Network becomes DATA Network.

What Happened

The official DATA Foundation blog lists the June 25 update, and the foundation whitepaper is dated June 2026. A Chainwire-distributed announcement says Trace launches as an onchain registry for AI training data provenance and licensing, with Kled integration registering 1.5 billion user-contributed records.

The article uses the official or strongest available source as the decision anchor and keeps the explicit dates aligned with that source. The dates below are UTC where a time is stated.

Why It Matters

Radar's owner-fit angle is protocol discovery. The important question is what Trace records, who controls receipt issuance, how licensing and consent updates work, and how token migration affects dapps and integrations. Exchange ticker changes are secondary to the protocol surface.

This is an execution and risk-control update, not a prediction. The clean decision is whether positions, bots, transfers, claims, routes, or dapp interactions need a verified change before a deadline or protocol state changes.

Separate three records before action: the source timestamp, the event timestamp, and the account or protocol state observed in the live interface. When those records disagree, the article should trigger a manual review rather than a forced trade, transfer, bridge, claim, or contract interaction.

What To Watch Next

Watch the DATA blog for migration timing, Trace documentation, contract addresses, receipt schema, governance controls, and developer integration paths. Treat third-party coverage as context until the official pages publish implementation details.

Recheck the official page before acting, store the retrieval time, and preserve the no-action branch when the live interface does not match the announcement.

For exchange events, verify every subaccount, bot, conditional order, and API route separately. For protocol events, verify the official domain, contract or documentation path, governance status, and user-facing app state before relying on third-party summaries.

Archive the final decision with UTC time.

Sources

Continue this cluster

Continue with related checks from the same cluster so the follow-up decision stays narrow and auditable.