Don’t trust, compute.
Announcing our partnership with Fhenix, building the future of confidentiality with Fully Homomorphic Encryption (FHE).
Supercharged by the Othentic Stack, @fhenix is accelerating private real-world applications.
Shh... it's a secret.
Introducing a new era of private AI, in partnership with @SecretNetwork.
Together, Othentic and Secret power a private and verifiable MCP interface, allowing AVS to be agent-compatible.
Demo, code, and more 🪐
Othentic co-founder @0xYarden took the stage at @ETHDubaiConf to discuss the new era of web3 innovation and the missing pieces.
Hint: off-chain services built as distributed systems.
One system, multichain 🪐
Introducing the Multichain component, allowing distributed systems (”AVS”) to operate in any EVM environment, simultaneously.
⬇️
Introducing MCP interface for distributed systems, designed to bridge AI agents with the world of verifiable data, tools, and resources.
Code, use cases, and more 🧵
We’re excited to be working alongside @0xOthentic as a trusted operator in the restaking ecosystem!
It's remarkable to see how many networks are choosing Othentic as their framework for building open innovations.
We recently witnessed an interesting use case of custom P2P messaging in the Othentic Stack 🏗️
Running a leader election algorithm, when the task is triggered externally. Here's how it works:
Leader election mechanisms are used to determine which operator executes a task at any given time.
1️⃣ When a task is triggered externally using an API, publish the task request to the P2P network using the sendCustomMessage JSON-RPC method.
2️⃣ Whenever a custom message is received on the P2P network, it is forwarded to the /p2p/message endpoint of the Validation Service. At this point, the leader election logic is executed to determine which node will perform the task. The elected leader then executes the task.
Let’s see how this works internally: