After recording 250M+ Trace receipts, DATA’s next big challenge is turning all that activity into a stronger AI data business.
That’s why @datafdn’s planned move to Sui makes sense.
It could free the team to focus on what AI labs actually pay for: useful training data with clear rights and verifiable origins.
DATA began as Story Protocol, pursuing a broad vision for programmable intellectual property. In June, it narrowed its focus to AI training data, with Trace as its flagship audit product.
Now its infrastructure strategy is following that sharper focus.
Running an independent Layer 1 means maintaining blockchain software, coordinating upgrades, and supporting validator infrastructure. Those responsibilities draw on the same resources needed to improve products and win customers.
One team. Two demanding jobs.
For DATA, the strongest source of value is connecting data supply, permissions, and verification into something buyers can use with confidence.
Trace helps buyers inspect records of data origins, consent, licensing terms, and payment status, while keeping the underlying content confidential.
As I said before, DATA reports 250M+ receipts recorded by Trace.
The planned division of work is straightforward:
- Sui → shared blockchain infrastructure for DATA’s protocol
- Walrus → the planned default storage layer for DATA Foundation apps, suited to large files like images and video
- Trace → the audit and provenance product DATA can keep evolving around its specific market
The wider Sui stack also offers Seal for access control and Nautilus for verifiable offchain compute, giving DATA additional building blocks as implementation progresses.
The efficiency thesis is simple: Better resource allocation.
If shared infrastructure reduces the burden of maintaining a standalone chain, more engineering effort can go toward better verification tools, smoother integrations, and broader adoption.
Sui Foundation’s announced $30M investment adds institutional commitment to that direction. The partnership also gives Sui’s infrastructure a substantial data supply to support.
Execution still matters. Migration takes work, shared infrastructure comes with tradeoffs, and DATA will depend on another ecosystem. The efficiency gains need to become tangible.
The transition is still ahead. $DATA remains the protocol token, nothing changes immediately for holders, and more migration details will follow.
I think this is a credible comeback strategy both for DATA and SUI where both can apply the lessons from the broader experiment and concentrate resources where the product has the clearest purpose.
NFA. DYOR.
