Idris (@FarydaIdris) header
Idris (@FarydaIdris) profile picture

Blockchain Researcher/Educator,Airdrop Hunter (Web3 Stuffs)

Joined December 2022
Photo by Idris (@FarydaIdris)Photo by Idris (@FarydaIdris)Photo by Idris (@FarydaIdris)Photo by Idris (@FarydaIdris)Photo by Idris (@FarydaIdris)Photo by Idris (@FarydaIdris)Photo by Idris (@FarydaIdris)Photo by Idris (@FarydaIdris)Photo by Idris (@FarydaIdris)Photo by Idris (@FarydaIdris)
Konnex is bringing businesses, robot operators, and AI intelligence together to power real-world automation. The goal is simple: help robots deliver meaningful work while making their performance verifiable. Real work. Verified results. That's the Konnex vision @konnex_world
Robots delivering real-world tasks need more than completion claims. @konnex_world verifies their work through independent validators and on-chain evidence, making every successful delivery transparent, accountable, and provable.
4
3
44
170
Actum’s PoHA is already running in production across two very different industries - rail equipment manufacturing and commercial hospitality. Different operational needs on the surface, same underlying problem underneath: when an action happens, who is accountable? One shared ledger, same verification process. The real question is how far this model can travel beyond these two settings. 👇
One Ledger, Two Very Different Industries — How Does That Work? Actum's PoHA runs in production in two completely different settings: a rail transit equipment manufacturer, with 5,000+ machines and operators doing hourly inspections; and a commercial hospitality setting, with guest data and service records flowing back and forth. What the two settings need looks nothing alike — the factory needs every bolt's inspection tied to a person; the hotel needs every data access traceable. But underneath, the problem is the same: when an action happens, who was there, who authorized it, can you trace it afterward, can you hold someone accountable? PoHA's answer is one shared ledger: Humans, Machines, and AI Agents, verified against the same standard, speaking through the same evidence. A pre-frozen codebook before the action, six-dimensional verification at the gate, signed attestation after — a factory inspection check-in and a hotel data access go through the same process. The numbers: the ledger now produces ~5,800 verified events a day across 5,300+ endpoints, with 174,000+ on-chain attestations in the past 30 days, 0 failures, 99.986% coverage. Different industries, same ledger. That's why PoHA can move from one setting to another: it doesn't solve one industry's business problem. It solves the problem every industry shares — who is accountable for what AI does.
99
95
1
109
671
We just passed 100k blocks on testnet 🧱 Every one gets us closer to mainnet. Only one major step left: an external chain audit. ICYMI: The full rundown ↓ quip.network/blog/quip-netwo…
124
109
2
195
4,381
On Konnex, work doesn't need to be believed. It needs to be proven. Signed. Executed. Verified. Anchored.
How a job runs on Konnex. A task is defined and signed. An operator's machine executes it. Independent verifiers score the result. The record is anchored on-chain. No argument afterwards about whether it happened. docs.konnex.world
2
5
52
Idris retweeted
One Ledger, Two Very Different Industries — How Does That Work? Actum's PoHA runs in production in two completely different settings: a rail transit equipment manufacturer, with 5,000+ machines and operators doing hourly inspections; and a commercial hospitality setting, with guest data and service records flowing back and forth. What the two settings need looks nothing alike — the factory needs every bolt's inspection tied to a person; the hotel needs every data access traceable. But underneath, the problem is the same: when an action happens, who was there, who authorized it, can you trace it afterward, can you hold someone accountable? PoHA's answer is one shared ledger: Humans, Machines, and AI Agents, verified against the same standard, speaking through the same evidence. A pre-frozen codebook before the action, six-dimensional verification at the gate, signed attestation after — a factory inspection check-in and a hotel data access go through the same process. The numbers: the ledger now produces ~5,800 verified events a day across 5,300+ endpoints, with 174,000+ on-chain attestations in the past 30 days, 0 failures, 99.986% coverage. Different industries, same ledger. That's why PoHA can move from one setting to another: it doesn't solve one industry's business problem. It solves the problem every industry shares — who is accountable for what AI does.
130
114
4
132
2,066
Let's peruse and practice the underlisted Friday sunnah. Allah sa mudace amin
Alhamdulillah, it’s Friday 🤍 Don’t forget to observe the Friday Sunnah: – Recite Surah Al-Kahf – Make abundant salawat on the Prophet ﷺ – Take a ghusl before Jumu’ah – Dress neatly and smell good – Go early for the khutbah – Make lots of du’a, especially before Maghrib.
15
السلام عليكم ورحمة الله وبركاته The Messenger of ALlaah ﷺ said: No one has been given a gift better and more vast than patience.
1
1
25
In a factory with 5,000+ machines, you can’t photograph every normal bolt every hour. Actum’s 5-State Behavioral Evidence Model including Contextual Silence, lets you capture full operational accountability without drowning people in paperwork. Curious how others here think about handling “nothing abnormal happened” as valid evidence. Drop your view below 🔗
In a factory with 5,000+ machines, operators can't photograph every normal bolt every single hour.So how do you capture 100% operational accountability — without drowning humans in paperwork?Enter Actum's 5-State Behavioral Evidence Model — and the power of Contextual Silence. 🧵👇
141
132
1
149
862
Mainnet is the last key piece. @cadillion on what it unlocks, from our latest Discord AMA 🎙 If you're not already in, join us on Discord. → discord.gg/quipnetwork
141
118
2
243
5,543
Idris retweeted
In a factory with 5,000+ machines, operators can't photograph every normal bolt every single hour.So how do you capture 100% operational accountability — without drowning humans in paperwork?Enter Actum's 5-State Behavioral Evidence Model — and the power of Contextual Silence. 🧵👇
156
141
1
155
1,527
AI adoption requires more than intelligence. @Actum_system makes actions across humans, machines and AI agents traceable through verifiable records, helping businesses establish responsibility, investigate errors and build trust through transparency and accountability. #Actum
47
101
343
WASIYAR BANKWANA KADA KA JIRA SAI KA RASA KAFIN KA SAN DARAJAR ABIN DA KAKE DA SHI. Wata rana za ka yi kewar muryar wanda kake iya magana da shi yau, za ka yi kewar wanda yake yi maka nasiha, amma ba za ka sake samun damar ganinsa ba. Saboda haka, ka girmama iyayenka, ka kyaut
1
1
1
199
ata wa iyalanka, ka yafe wa mutane, ka kuma yi amfani da damar da kake da ita wajen aikata alheri. Ka tuna, wasu damammaki idan sun wuce, ba sa dawowa.
11
Weekly AI Fail Check #3 is live. Actum is giving 10 USDT to the best 3 replies this week! What AI agent fail did you see that looked small but could have been expensive in production? Drop your story or screenshot below and explain whether an entry Circuit Breaker could have stopped it. 🛠️
🚨 Weekly AI Fail Check #3 is here! What wild mistakes did you see an AI agent make this week? Auto-ordering the wrong thing, deleting the wrong file, sending test data to a real customer, or confidently talking nonsense in a group chat? A fail itself isn't scary. What's scary is when nobody knows, nobody is accountable, and there's no way to trace it back. Most agent failures don't happen because the agent is "not smart enough" — they happen because there's no gate before it acts: no pre-frozen rules, no entry verification, no signed behavioral record. It fails, and you can't even investigate it properly. So the same question as always this week: drop your AI fail screenshot or story in the replies, tag @Actum_AI, and tell us whether an entry "Circuit Breaker" could have stopped it. The 3 best answers win 10 USDT each. 🏆 That's exactly what Actum's PoHA is for: a pre-frozen codebook before the action, six-dimensional verification at the gate, and signed attestation after — so every agent action has someone accountable for it.
146
139
1
161
1,080
One toolchain, two very different demos 🧩 ‣ A trading game played at Quantum.Tech World ‣ A logistics yard dispatch problem Both run on XQuad, the toolchain behind QVM ↓ quip.network/blog/xquad-in-p…
128
106
1
195
5,717
Many people know @konnex_world by name, but the real value lies in what it’s building. Konnex is developing a Layer 1 blockchain designed for Physical AI, bringing robots, AI developers, operators, and validators together to make real-world robotic tasks verifiable, accountable,
3
2
30
133
🧵 1/2 and economically valuable. It's not just about robots doing the work; it's about proving they actually did it. That's what makes Konnex worth watching. #Konnex
32
Idris retweeted
Here is how to wear the Ihram, just in case Allah blesses you with Hajj or Umrah soon...
55
1,086
20
4,765
182,647
Idris retweeted
🚨 Weekly AI Fail Check #3 is here! What wild mistakes did you see an AI agent make this week? Auto-ordering the wrong thing, deleting the wrong file, sending test data to a real customer, or confidently talking nonsense in a group chat? A fail itself isn't scary. What's scary is when nobody knows, nobody is accountable, and there's no way to trace it back. Most agent failures don't happen because the agent is "not smart enough" — they happen because there's no gate before it acts: no pre-frozen rules, no entry verification, no signed behavioral record. It fails, and you can't even investigate it properly. So the same question as always this week: drop your AI fail screenshot or story in the replies, tag @Actum_AI, and tell us whether an entry "Circuit Breaker" could have stopped it. The 3 best answers win 10 USDT each. 🏆 That's exactly what Actum's PoHA is for: a pre-frozen codebook before the action, six-dimensional verification at the gate, and signed attestation after — so every agent action has someone accountable for it.
158
144
4
164
3,088
Traditional logs tell you what the system says happened. A PoHA ledger proves what happened, when it happened, and who is accountable for it. That’s the gap Actum is closing. Curious how others here think about the difference between logs and verifiable records 🤔
Traditional Logs vs. Actum PoHA Ledger — why the difference matters more than it looks. Traditional logs record what happened. That sounds enough, until something goes wrong. Then the questions start: who edited this entry? When did it actually happen — when the event occurred, or when it reached the log? And the investigation usually ends the same way: "system error." No one accountable, nothing to prove otherwise. ❌ Editable by admins — whoever holds the keys can rewrite history. ❌ Single timestamp — occurrence and ingestion collapse into one number, so you can never prove when something really happened. ❌ Blames "system error" — the log describes the machine, not the human behind it. Actum's PoHA ledger is built the other way around: ✅ Signed at generation — every event is signed the moment it's created. Tamper-evident: any change after the fact is detectable. ✅ Bi-temporal truth — Occurrence Time and Ingestion Time are recorded separately, so the timeline is provable, not asserted. ✅ Anchors every AI and machine action to an accountable human — Humans, Machines, and AI Agents all write to the same ledger, under the same standard, and every entry traces back to a specific authorized person. A log tells you what the system says happened. A PoHA ledger proves what happened, when, and who is responsible for it. That's the difference between "we looked into it" and "here is the evidence."
150
140
1
158
1,190
Sallah a aika ce! - Dr Abdullah Gadon Kaya
19
364
2
1,500
26,309