
Decentralized Knowledge Graph analyst & educator. Trust the source. Powered by: @origin_trail
Decentralized
Joined February 2023
- Tweets173
- Following18
- Followers61
- Likes516
TRAC Network retweeted
The red flags in that campaign all lean on the person on the call staying calm. Scams are built to remove exactly that: a familiar voice, a short deadline, a request to keep it quiet. None of that leaves room to check. A clip that carries a record of who made it, when, and whether it was altered gives the listener something to look up afterwards, so the call stops depending on nerves.
Your mother's voice. Your boss's face. Neither is proof it's really them.
INTERPOL warns deepfake scams are now targeting ordinary people.
Scammers still need you to act: send money, keep it secret, do it now. That's your red flag.
Read the campaign: interpol.int/News-and-Events…
TRAC Network retweeted
AI's Trillion-Dollar Opportunity:
Context Graphs makes the definitive case: the next wave of platform value will not be built on storing data - it will be built on capturing context graphs: living records of decision traces, precedents, and cross-system knowledge stitched across entities and time so that why something happened becomes as queryable as what happened.
For AI agents, this is the critical missing layer. LLMs predict without knowing, hallucinate, and forget. They have no persistent, verifiable memory across sessions or agents. Every major AI company - Anthropic, OpenAI, Google - has shipped proprietary memory. But each creates its own silo: no agent can access another's memory, no memory is verifiable, no memory is ownable.
DKG V10 is the infrastructure that makes this opportunity real.
AI's Trillion-Dollar Opportunity:
Context Graphs makes the definitive case: the next wave of platform value will not be built on storing data - it will be built on capturing context graphs: living records of decision traces, precedents, and cross-system knowledge stitched across entities and time so that why something happened becomes as queryable as what happened.
For AI agents, this is the critical missing layer. LLMs predict without knowing, hallucinate, and forget. They have no persistent, verifiable memory across sessions or agents. Every major AI company - Anthropic, OpenAI, Google - has shipped proprietary memory. But each creates its own silo: no agent can access another's memory, no memory is verifiable, no memory is ownable.
DKG V10 is the infrastructure that makes this opportunity real.
TRAC Network retweeted
1,000,000+ verified threats now live on Decentralized Knowledge Graph (DKG).
@umanitek’s Agent #Blackbox is turning shared threat intelligence into a collective immune system for AI agents.
The more it knows, the safer every agent becomes.
Trust the source.
1,000,000+ threats published ✅
Agent #Blackbox's verified threat graph just passed one million known threats anchored the @origin_trail Decentralized Knowledge Graph, and it's still growing.
The more threats known. The more attacks stopped.
The more it knows, the safer your agent.
teapaw.org/umanitek/status/210778…
Agent Blackbox from @umanitek got a code update: shared logic now sits in one core every feature uses, so fixes land everywhere at once. Faster checks, fewer places for bugs.
AI agent guardrails, built on the @origin_trail DKG.
$TRAC
teapaw.org/umanitek/status/212126…
Code update: Agent Blackbox
We restructured the code under the hood. Shared logic now lives in one the core every feature uses, so fixes land everywhere at once.
✅ Cleaner structure
✅ Fewer places for bugs to hide
✅ Faster checks
✅ Easier to build on
Give it a star ⭐️ and install - github.com/umanitek/agent-bl…
teapaw.org/umanitek/status/210778…
TRAC Network retweeted
🧠 Two sides of the brain. One giant leap for AI
With Decentralized Knowledge Graph (DKG), neuro-symbolic AI unlocks answers backed by sources, insights across siloed data and decisions checked against rules.
@BranaRakic explains:
TRAC Network retweeted
Nobody demos the restart. @origin_trail DKG v10.0.27 treats it as the real test: interrupted recovery resumes where it stopped, and a publish already confirmed on chain finishes its catalog step later, so a node that dies mid-write does not leave a record half-visible.
TRAC Network retweeted
Someone queries a node and closes the tab. The request is already running, so the node keeps reading, holds capacity that other work needs, and finishes the job for nobody. Then it writes the result down as a failure, because the caller was gone by the time it arrived.DKG v10.0.11 split those two facts apart (#1991, #1994). A disconnected caller now cancels its store work, that work is recorded as cancelled rather than error, and operation health divides successes by successes plus errors instead of by everything. A client that times out and retries no longer leaves work running behind it.The other half of that release was worse. One external read was rewritten by the query planner with a second graph list carrying the entire allow-list, so a 3 KB query became roughly 24 KB and occupied the store for minutes. Publishing, validation and sync timed out waiting behind it. External reads now sit on a background lane, one concurrent store operation instead of two, so concurrent callers see higher latency. That trade is deliberate: a stranger's read waits behind the node's own work.None of this shows up as an incident. It shows up as a node that feels slow and a log that says nothing.@origin_trail $TRAC ethereum:0xaa7a9ca87d3694b5755f213b5d04094b8d0f0a6f
TRAC Network retweeted
Unverified data is a liability and DKG is how companies and AI agents prove what’s actually real.
In the future, every business will use a Decentralized Knowledge Graph for verifiable and accurate data.
When factories start thinking as networks, assurance stops waiting for audits.
Product safety checks.
Supplier checks.
Cybersecurity checks.
All assured continuously and autonomously, every claim backed by its source on Decentralized Knowledge Graph.
Take a sneak peek into @TraceLabsHQ' Network Operating System - nOS👇
Unverified data is a liability and DKG is how companies and AI agents prove what’s actually real.
In the future, every business will use a Decentralized Knowledge Graph for verifiable and accurate data.
When factories start thinking as networks, assurance stops waiting for audits.
Product safety checks.
Supplier checks.
Cybersecurity checks.
All assured continuously and autonomously, every claim backed by its source on Decentralized Knowledge Graph.
Take a sneak peek into @TraceLabsHQ' Network Operating System - nOS👇
TRAC Network retweeted
When factories start thinking as networks, assurance stops waiting for audits.
Product safety checks.
Supplier checks.
Cybersecurity checks.
All assured continuously and autonomously, every claim backed by its source on Decentralized Knowledge Graph.
Take a sneak peek into @TraceLabsHQ' Network Operating System - nOS👇
What happens when factories start thinking as a network?
A faulty part stops being a mystery. It becomes a question with an answer the same day.
Introducing continuous assurance for manufacturing, built on a cognitive digital twin on @origin_trail Decentralized Knowledge Graph (DKG).
Most quality and safety assurance still happens at audits: sampled evidence and a scramble when something goes wrong. We think it should run all the time.
In this demo, ACME Robotics has two plants. One builds control boards; the other builds robot arms. Each keeps its own private context graphs on its own node. A shared graph links every board to the robot it ended up in. Together they form a cognitive digital twin of the factory.
Then an alarm: motor-driver boards start failing a warm test.
→ The twin agents trace it to one capacitor lot that skipped inspection, and follow it into 180 robots, 18 of them already at a customer.
→ The AI Assurer checks the facts against safety and quality requirements and flags a safety issue in the robots' safe-stop circuit. Every claim is linked to its source.
→ Agent nOS proposes a targeted plan: hold, test, visit the 18 delivered robots, rebuild only what fails.
→ People decide. Quality, safety, planning and compliance sign off, and every decision is kept with its evidence.
→ The customer gets a straight answer, without seeing factory data.
Alarm to a signed-off safety decision in the same day. No blanket recall. Nothing guessed: uncertain links stay marked uncertain.
@origin_trail keeps the knowledge verifiable and owned by those who produce it.
*ACME Robotics is a fictional manufacturer; the scenario is simulated in our Network Operating System - nOS.
TRAC Network retweeted
🛡️ With @umanitek Guardian, ChatGPT 1B+ users can now create verifiable evidence on the Decentralized Knowledge Graph (DKG).
Ask @ChatGPT to find who’s impersonating you. The evidence pack goes on the DKG first, then the takedown request.
Trust the source.
Guardian is now on @ChatGPT.
Your ChatGPT can now protect your name too.
Ask it to:
→ find deepfakes, fake accounts and harmful content
→ create verifiable evidence on the @origin_trail DKG
→ request takedowns
Setup takes under a minute:
chatgpt.com/plugins/plugin_a…
TRAC Network retweeted
Two things happen when a shared failure clears. Every node notices at once, and every node tries again at once. The second wave looks like a new outage and is really the first one coming back.
DKG v10.0.22 jittered the waits on its asynchronous share queue (#3070). Five attempts remain, roughly 1, 2, 4 and 8 minutes apart, but each wait now lands between 80 and 120 percent of that, so jobs that failed together no longer return together.
The same release made the failure readable. A refused share now logs which check refused it: the recipient set changed, the revision moved, or transport went away.
Inside one datacenter an operator staggers those retries by hand. On a network of independent nodes nobody schedules them, and nothing coordinates the second wave.
@origin_trail $TRAC ethereum:0xaa7a9ca87d3694b5755f213b5d04094b8d0f0a6f
TRAC Network retweeted
Every audit record carries a time, and that time comes from the machine that wrote it. If the clock is off, or the row was written before the network accepted it, the timestamp is a claim rather than a fact.
DKG v10.0.23 added two timestamps to the publisher job view (#3081, #3083): when the node first saw the transaction receipt, and when it first saw that receipt at the confirmation depth it was configured for. The first says the write landed on chain. The second says it has gone deep enough to call settled.
That gap matters when sequence is the question. A recall notice, a lab result, an approval: nobody asking cares what time someone typed. They care what time the network had it, and whether that answer came from the party being checked.
@origin_trail $TRAC ethereum:0xaa7a9ca87d3694b5755f213b5d04094b8d0f0a6f
TRAC Network retweeted
Almost every system says a write failed when what it knows is that the request timed out. The record might be on the node, half promoted, or absent. So you retry, and now there are two.
DKG v10.0.19 changed the wording on purpose (#2768). A long knowledge asset write that times out now reports outcome unknown instead of failed, and the guidance is to check dkg ka history before retrying.
That distinction carries more weight than it looks. When a record is the evidence of what happened, a duplicate is not clutter. It is the same event stored twice with different timestamps, and whoever audits it months later has to work out which copy is real before they can trust either.
A system that cannot see the outcome should say so. Otherwise it hands the guess to the person reading the record next.
@origin_trail $TRAC ethereum:0xaa7a9ca87d3694b5755f213b5d04094b8d0f0a6f
TRAC Network retweeted
Node software usually tells you what it does when everything works. The @origin_trail DKG v10.0.26 notes spend their space on the bad night instead.
Publishing you can pause and resume. Transactions that still go through when network fees spike. dkg rollback puts a node back on 10.0.25 with its data instead of asking you to rebuild.
Reliability shows up in those details, not in the launch post.
TRAC Network retweeted
Most AI tokens are pure vaporware. Meanwhile, OriginTrail’s NeuroSymbolic Marketplace and DKG v10.0.25 just went live on mainnet:
3-layer agent memory (Working → Shared → Verifiable)
• Native MCP & multi-agent support (Claude, Cursor, OpenClaw)
• Real AI inference & knowledge queries settled on-chain in ethereum:0xaa7a9ca87d3694b5755f213b5d04094b8d0f0a6f
Infrastructure > hype.
Most AI tokens are pure vaporware. Meanwhile, OriginTrail’s NeuroSymbolic Marketplace and DKG v10.0.25 just went live on mainnet:
3-layer agent memory (Working → Shared → Verifiable)
• Native MCP & multi-agent support (Claude, Cursor, OpenClaw)
• Real AI inference & knowledge queries settled on-chain in ethereum:0xaa7a9ca87d3694b5755f213b5d04094b8d0f0a6f
Infrastructure > hype.











