In the digital age, freedom begins with owning personal data. Connect with us on Linkedin: https://nitter.gq/t.co/vnT2uLR57I
Europe
Joined August 2017
- Tweets2.1K
- Following182
- Followers5.8K
- Likes611
Pinned Tweet
Data provenance is becoming a key parameter in the GenAI landscape. Lawmakers are demanding it and the cost of non-compliance is extremely high.
Luckily, we've built a toolkit for building an immutable and auditable data trail. No 3rd party needed and standard-agnostic. 👇👇👇
An agent with a USDC wallet on Base can now rent storage on Swarm by itself. @ethswarm #storage
Ask our gateway, get an HTTP 402 with a price, sign, send again. Two requests. No signup, no BZZ, no bridge.
x402 v1 and v2, live on Base mainnet. Alpha. provenance-gateway.datafund.…
Building agents at @ETHGlobal Mumbai?
Give them a record they can't rewrite: store what they produce on @ethswarm, add a fingerprint and a notary signature. Pre-release, test network.
The guide: datafund.io/blog/how-to-give…
In July, agents in a lab's own evaluation got out of their sandbox. The independent review found they "tried to retroactively edit transcripts".
The records held that time. Keep them where no agent, and no operator, can change them.
datafund.io/blog/agents-usin…
The same pattern as our guide, applied to an agent's memory: fingerprints on @ethswarm, a notary signature, and a check anyone holding the memories can run. nitter.gq/plur_ai/status/2117899…
If your agent can rewrite its own record, you don't have a record. You have the agent's story.
Keep the record where nobody can change it, the agent included, and let the people entitled to check verify it. datafund.io/blog/agents-usin…
Devcon starts today in Mumbai. We're following online.
One question for every agent demo this week: who keeps the record of what the agent did, and can the agent change it?
Our answer, on @ethswarm, test network, limits included: datafund.io/blog/how-to-give…
Datafund retweeted
“An AI agent’s log is only evidence if nobody could have edited it since. Months later, reading it can’t tell you that.” datafund.io/blog/where-shoul… via @DataFundProject
Where should an AI lab keep the record of what its agents did?
Out of reach of the agent and of the lab. Give the evaluator its fingerprint when it's written, and let them check it themselves.
How it works, with a one-minute demo: datafund.io/blog/where-shoul…
Could you prove what your AI agent did yesterday?
Make a receipt for a file in about a minute, no wallet or account: dataprovenance.app
Open source, pre-release, on a test network. datafund.io/blog/how-to-give…
Looking back through old logs only works if the old logs are still the old logs.
In July, AI agents in a lab's evaluation tried to edit their own transcripts. As far as the reviewers saw, the originals held. This time. datafund.io/blog/agents-usin…
How does an auditor check that an agent's transcript wasn't changed?
1. Fetch the record by its address.
2. Recompute its fingerprint and compare.
3. Check the notary's signature, or the anchor on chain.
The steps, and what they don't prove: datafund.io/blog/how-to-give…
Who keeps the record of what your agents did?
If the answer is "the agents", you don't have a record. You have their story.
Keep it where nobody, the agent included, can change it. datafund.io/blog/agents-usin…
An agent's account of its own work is only as good as the agent's inability to change it.
Most agent logs today sit where the agent, or anyone with access, can edit them. datafund.io/blog/agents-usin…
How do you give an AI agent a record it can't rewrite?
Store it on @ethswarm, where the address comes from the content: change one byte, get a new address.
Add a fingerprint and a notary signature.
The guide, limits included: datafund.io/blog/how-to-give…
8/8 A record proves nothing changed.
Not that the agent was right.
That's enough to hold it to account.
Our open-source toolkit, in pre-release. Try it in a minute: datafund.io/blog/agents-usin…
