SynCoLab – Collaborative Synthetic Data Lab with Agent Validation + Verifiable Storage

[d3osaju]

Title:

Spicy AI Collaboration with Storacha Data Storage - Mar 31, 2025 - SynCoLab - Encode AI Hackathon

---

Body:

Spicy AI Collaboration with Storacha Data Storage - Mar 31, 2025 - SynCoLab - Encode AI Hackathon

Contributors

@deoxicit

Accomplished Tasks

• 🔐 Create & provision 2 agent-specific Storacha spaces (generator, validator)
• ✅ Store at least 3 artifacts per agent (prompt, output, CoT, score)
• 📤 Upload each run to IPFS via Storacha with full UCAN authorization
• 🧬 Use .ipfs.w3s.link and path-based links for CID access
• 💾 Optional support for runs.json uploads to archive full run history

Update

Agent collaboration + synthetic data generation + decentralized storage

• 🤖 Agent A (generator): creates synthetic datasets based on user prompts
• 🧪 Agent B (validator): reviews the synthetic output, logs reasoning (CoT), and scores it
• 🧾 All artifacts (prompt, CoT, output, score) are stored via Storacha in agent-specific spaces
• 📦 CIDs are returned to users, enabling public auditability and data provenance
• 🧠 Drift comparison vs. benchmark datasets using OpenAI embeddings
• 💡 Prompt history, replay, and agent dashboards included

💻

Live Demo

🌐 https://syncolabs-production.up.railway.app/

Try:

• Picking a prompt category (e.g. Healthcare)
• Running the agent flow
• Viewing results + IPFS links
• Uploading all runs to Storacha
• Pasting a benchmark CID for drift scoring

---

📦

GitHub Repo

🔗 https://github.com/deoxicit/syncolabs

---

📽️

Demo Videos

Feedback

• Let me know what else do you think i can add this and i am accepting changes for greater good.

Next Tasks

• 🔒 Private UCAN-based access for CoT logs
• 🖼️ CID visualizer for IPFS directories
• ✍️ Wallet-signed metadata for authorship

Thanks for building this amazing storage layer 💙
We’re excited to build more with Storacha!

[jamiechicago312]

Thank you so much for submitting this update! 🙌 I'm tagging in @alanshaw and @fforbeck to assist me with reviewing your project so far.

We will work on following up related to

We’d love to hear your feedback — we’re open to adding:

🔒 Private UCAN-based access for CoT logs
🖼️ CID visualizer for IPFS directories
✍️ Wallet-signed metadata for authorship

[jamiechicago312]

Also I finished up the template if you wanted to make adjustments to this for your update, but feel free to create a new one if that is easier.
https://github.com/orgs/storacha/discussions/83

[d3osaju]

Sure that is helpful

[d3osaju]

Hey Just updated the discussion topic , hope this is okay

[jamiechicago312]

❓ @deoxicit
Do the agents share information with one another? Like I share that my healthcare cost $5000 would then the bot be able to determine the financial side where it can come up with a payment plan for me to pay it off? That is an example I thought of just now. But I'm sure there are others.

[d3osaju]

Yes they are sharing information with reach other ,

I am planning to implement a separate endpoint for validator agent only , So u can pass a file in specified format it can do the validation too

[fforbeck]

@deoxicit @jamiechicago312 loved the app. I noticed that you are configuring the agent using the regular authentication flow with email, so you need to confirm the email every time you initialize the agent, right?

You can create a delegation from your Storacha account to the agent, and grant that agent permission to upload data to Storacha. Check this out: https://docs.storacha.network/concepts/ucan/#delegate-across-apps-and-services

This will cover the UCAN authorization flow. Then you can set the delegation encoded as base64 in an env var, and load it to configure the agent during the app initialization, e.g: https://github.com/storacha/mcp-storage-server/blob/main/src/core/storage/config.ts#L19

You can see the same process to create the agent key and delegation in this demo: https://www.youtube.com/watch?v=Ow4HDoq-FSE

[d3osaju]

Since they are using same instance, one time verification is enough , until we push some new changes and redeploy the server.

I will i try the UCAN Authorization flow for sure