DATA Blockchain Shifts to Sui After $30M Deal
DATA is retiring its own blockchain after a $30 million Sui investment. Learn why it is focusing on AI data provenance, how Trace works and what changes.

DATA Is Leaving Its Own Blockchain to Focus on AI Data Provenance
A blockchain startup doesn't have to keep running its chain to preserve whatever it built. DATA - formerly known as Story Protocol - is making that call after securing a $30 million investment from the Sui Foundation. The plan is to retire its own network and move its work to Sui, with a tighter product focus: recording where data came from, the consent terms tied to it, and the licensing history for data used to train AI models.
The shift comes after a broader rethink. DATA started with the bigger idea of putting lots of intellectual property onchain, ranging from music rights to patents. In reality, those markets already had established systems and intermediaries, and getting major rights holders to adopt permissionless licensing turned out to be hard. Now the company sees a more specific gap in AI data: buyers can struggle to verify what a dataset actually contains, where it came from, and whether its use is properly licensed.
The problem is real - but a blockchain record alone doesn't automatically solve it. This piece looks at why DATA is changing direction, what its Trace registry is meant to do, why it chose Sui, and what the move does - and doesn't - prove about the business.
Why DATA is leaving its own blockchain
This is less about switching "favorite" chains and more about a product and operations decision. DATA spent years building a Layer 1 network intended for a wide set of use cases: registering intellectual property onchain and attaching usage terms to it. The original concept could cover music royalties, patents, trademarks, and other rights.
The issue wasn't that intellectual property has no licensing problems. It was that each IP category has its own market structure, legal norms, intermediaries, and incentives. Many rights holders already have ways to manage permissions, and large rights owners had little reason to make high-value assets available through permissionless licensing.
As CEO Andrea Muttoni put it in an interview with CoinDesk, the company was trying to "boil the ocean" in a market that's both crowded and hard to move.
That breadth also runs into a classic startup issue: even a technically ambitious platform can be tough to sell when customers, workflows, and the day-to-day business case differ from one use case to the next. Building a network didn't remove the need to persuade rights holders, marketplaces, and buyers to change their behavior. It just added another system the company had to operate while trying to fix those adoption problems.
The cost of owning the infrastructure
Running a blockchain takes more than writing protocol code. It means ongoing work involving engineering, validators, security audits, and infrastructure providers. Sometimes those costs make sense - especially if the chain is central to the product or if you need capabilities other networks don't offer. But those costs get harder to justify when the business is increasingly focused on a single application.
DATA's application is Trace, a registry for information about AI training data. As the company leaned harder into Trace, the question shifted: keep investing in its own Layer 1, or put that effort into the registry and the tools around it.
Moving to Sui lets DATA reduce the burden of operating a standalone chain. That doesn't make blockchain infrastructure "free," and it doesn't remove migration or integration work. It just changes where the engineering and operations effort goes. In other words, DATA is opting to lean on another network instead of maintaining the full stack itself.
The company's rebrand from Story Protocol to DATA Foundation in June had already signaled a pivot toward AI data. Leaving its own chain continues that narrowing - this time focusing on the infrastructure needed for tracking provenance and usage rights. Muttoni describes it as a continuation of the earlier shift rather than a totally new turn.
A strategic reset is not proof of product-market fit
The $30 million investment helps with money and ecosystem support, but it doesn't automatically prove that Trace has found a durable market. DATA hasn't said how much of its original $140 million funding remains. Muttoni also said existing investors, including a16z crypto, are still involved. Beyond the announced investment, financial terms weren't disclosed.
For customers and token holders, the real test is whether Trace becomes useful in real data transactions. That means more than logging activity. Buyers need to be able to find the records, understand what the records mean, and trust them when they decide whether to license or use a dataset. The infrastructure choice may make that easier - but it can't replace adoption.
What Trace records about AI training data
Trace is set up to create a record tied to a data contribution. When someone submits a video, voice recording, or other file through a participating marketplace, the registry can capture details like the submission date, the contributor's agreed terms, and later licensing or payment events.
In theory, this gives data buyers and sellers a more inspectable history. A buyer could check where a contribution came from and what permissions were attached to it. A contributor could point to the terms they accepted. And a marketplace could use the registry to make its own data flows easier to audit.
That distinction matters. Trace is described as a registry, not a marketplace that directly matches every dataset with a buyer. DATA says its current goal is to provide infrastructure for auditability and provenance. Muttoni didn't rule out the company running a marketplace later, but didn't provide details.
Provenance records are useful, but they don't fix everything
A record can make information easier to inspect and harder to change without leaving traces. It can't, by itself, prove that what someone entered into the system was true to begin with. If the contributor, marketplace, or intermediary provides inaccurate origin or licensing details, recording those details doesn't make them correct.
That's the core challenge for any provenance system: the value depends on how the real-world file is linked to the person or organization submitting it, what permissions they can actually grant, and what later events get recorded. If that chain is weak, the registry can still preserve a clean-looking history of a bad claim.
So the question isn't simply whether Trace uses blockchain. It's how the product handles submissions, represents consent, deals with changes and disputes, and helps buyers understand which claims are verified versus merely recorded. The public description doesn't cover all of those controls. Those details will matter as the product moves from recording contributions to supporting licensing decisions that have real consequences.
DATA's own rationale is tied to experience with Poseidon, an AI data company incubated by the Story team. Muttoni said buyers had limited ways to tell whether datasets offered for sale were original, properly licensed, or exclusive. He also described an instance where vendors reportedly offered Poseidon a dataset as "exclusive" even though it was available from other sellers. He added that the team was once given a dataset back that it believed it had originally provided.
Those examples show a trust and verification problem. They don't, on their own, establish how big the addressable market is or how many buyers will pay for a separate provenance layer. DATA hasn't disclosed how many Trace records have generated licensing revenue.
Activity counts need context
Marketplace Kled is a major driver of activity on Trace. Muttoni said Kled is adding between 3 million and 4 million contributions per day. That total includes older records being brought onto Trace, not just new submissions in the same period.
So the number signals registration volume, not the number of datasets sold, unique contributors, verified rights, or revenue-generating licenses. Those distinctions matter because high throughput can show a system is being used without proving it supports a sustainable business.
For now, DATA's case is that Trace can become a useful record layer across the data supply chain. Even if the company doesn't own the marketplace, a registry can still create value if participants use it consistently and the records reduce the cost or risk of transactions. The hardest part is getting partners to coordinate across multiple marketplaces and data providers.
Why Sui, and what the migration changes
DATA says Sui has tools that line up with its next product priorities. It named Walrus, a decentralized storage platform, and Seal, a tool for encrypting files and restricting access. The idea is that this combination could let DATA store copies of original files linked to Trace records and control who can access them.
Right now, Trace records information about a file rather than storing the file itself. Adding storage could let buyers compare what they received against what was submitted and identify any changes. Access controls could also help ensure files are available only to buyers with the right permissions.
These are potential product capabilities, not proof that every file will be stored or that every licensing condition can be enforced technically. DATA's announcement outlines direction. Whether it translates into real value will depend on implementation details, reliability, costs, user experience, and how access rights map to contractual and legal terms.
The migration plan for the DATA token
Sui Foundation's $30 million investment makes it DATA Network's largest institutional holder, according to Muttoni. He said the foundation plans to take a hands-off approach to DATA's product decisions. The company also plans to move its existing token to Sui on a one-to-one basis.
In the company's press release, existing $DATA holders are expected to keep their rights and vesting schedules unchanged. The current blockchain will remain operational until the migration is complete. That transition matters: holders need clear instructions and enough time to understand any wallet, custody, or exchange steps that affect them.
A one-to-one migration describes the conversion ratio, not every operational detail. Holders should follow DATA's official migration guidance and the instructions from relevant service providers rather than assuming the token will move automatically. The public information doesn't spell out a migration deadline or provide every technical step.
For DATA, the move also changes its relationship to infrastructure. Once the transition is complete, the company won't need to run its own blockchain, but it will rely on Sui for the network layer and on the selected tools for storage and access control. That's a trade-off, not an automatic upgrade. DATA gives up some direct control in exchange for focusing resources on the application and using an existing ecosystem.
This can be reasonable if maintaining a chain isn't the main source of differentiation. It's less appealing if the business later needs network-level features Sui doesn't provide - or if relying on external infrastructure adds costs or constraints that outweigh the savings. Ultimately, the decision should be judged against DATA's actual product needs, not against a general claim that one chain is "better" than another.
What to watch as DATA narrows its focus
The AI training data market is getting more attention as model developers and data providers look for ways to source, license, and manage training material. Muttoni estimates the market could be worth hundreds of billions of dollars. That's his estimate, not a disclosed number for Trace's addressable revenue or current sales.
A big market estimate doesn't tell you whether there's a real, pay-for value proposition. Execution matters here. DATA's pitch isn't just that AI companies need data - it's that participants may need dependable records about origin, permissions, and later use, and that they may pay, integrate, or change workflows to get those records.
A few practical indicators will show whether the strategy is working:
- Use beyond one major partner: Kled's volume is meaningful, but adoption across multiple marketplaces and buyers would reduce concentration risk.
- Commercial conversion: DATA hasn't disclosed how many records generated licensing revenue. Usage that results in money is more informative than contribution counts.
- Record quality: Buyers need to understand how submissions are checked, how consent is represented, and how disputes or corrections are handled.
- Repeatable integrations: A registry is more useful when partners can adopt it without custom work for every marketplace.
- Migration execution: The chain and token transition needs clear communication and a reliable process for holders and integrators.
- Operational economics: Moving away from a dedicated Layer 1 may reduce some burdens, but the real costs of storage, access control, and network usage still have to fit the business model.
The central product question is whether Trace can function as a neutral verification layer without needing to own every part of the data market. DATA says it wants to focus on auditability and provenance rather than competing with marketplaces right now. That can be a tighter, clearer role - but it depends on counterparties agreeing that shared records are worth maintaining.
There's also the governance issue. Consent and licensing terms aren't just static fields in a database; they can be conditional, time-bound, or depend on jurisdiction. A registry can make those terms easier to reference, but participants still have to figure out how legal agreements, access controls, and real-world rights fit together. In a high-stakes workflow, buyers will care about that boundary before they rely on a record.
The logic is still straightforward. DATA started by trying to build a broad intellectual property system. It ran into entrenched markets and diffuse customer needs. It then narrowed toward AI data and is now reducing infrastructure overhead to concentrate on one product. That sequence is more deliberate than continuing to maintain a chain simply because it was part of the original plan.
Conclusion
DATA's move to Sui is a decision to narrow both the system it operates and the market it's chasing. The company is stepping away from the idea of a general-purpose intellectual property network and focusing on Trace, where it sees a need for better records of AI data origin and permissions.
That focus is more coherent, but the business case still needs proof. Contribution volume isn't revenue, and an "immutable" record is only as useful as the evidence and processes behind it. The next signals to watch are adoption beyond Kled, licensing activity, the quality of provenance checks, and how smoothly the token migration goes.
If you're evaluating the project, it helps to separate the infrastructure story from the product story. Sui may reduce the burden of running a chain, but Trace still has to make data transactions more trustworthy and practical. Read the original CoinDesk report for the source interview and migration details, then judge future announcements against the same measurable questions.