Home/AI/@Fhe_state
48
Score · promising
Scored 5mo ago · may be stale

@Fhe_state

FHESTATE

FHESTATE is building a confidential execution layer for autonomous AI agents on Solana using Fully Homomorphic Encryption (FHE). The project enables AI agents to operate on encrypted state, protecting prompts, balances, memory, and execution flows while settling publicly on-chain. They're actively developing an MCP (Model Context Protocol) server for encrypted agent coordination and have demonstrated working devnet infrastructure with Rust CLI tooling.

𝕏 @Fhe_state↗ t.coAIpromising🔇 quiet 85d

AI Analysispromising

Confidence
72%

FHESTATE is building a confidential execution layer for autonomous AI agents on Solana using Fully Homomorphic Encryption (FHE).

The project enables AI agents to operate on encrypted state, protecting prompts, balances, memory, and execution flows while settling publicly on-chain.

They're actively developing an MCP (Model Context Protocol) server for encrypted agent coordination and have demonstrated working devnet infrastructure with Rust CLI tooling.

Green flags: Very early stage (202 followers, account created Jan 2026, <5 months old) · Active technical development: working MCP server on Solana devnet with Rust CLI v0.2.0 · Clear differentiation: FHE for AI agent privacy is an emerging infrastructure niche · Consistent detailed technical updates showing real building (runtime architecture, encrypted state orchestration) · Hackathon origins (Solana BIP) evolved into ongoing product development

Red flags: Extremely low engagement (avg 23, <50 interactions per tweet) despite technical content · No clear token information yet despite mentions of '2.5% supply locked' · Anonymous team with no visible founder/engineer profiles · Very new account (4 months old) with limited external validation or partnerships mentioned

Token
Yes
Chain
Solana
Stage
testnet
Category
FHE infrastructure for AI agents

Recent tweetsSee all on 𝕏 →

FHESTATE // Governor Confidential governance is now entering the agent runtime. We’ve added Governor, the fifth confidential agent in FHESTATE, built specifically for Dark DAO governance on Solana Devnet. Governor handles a simple but important flow: CAST BALLOT → REQUEST TALLY A YES/NO vote becomes an encrypted step in Governor’s isolated hash chain. The tally cannot be requested until the ballot step exists. No ballot. No tally. Governor never decrypts individual votes, never stores plaintext ballots, and does not modify the underlying on-chain tally logic. It operates under the same manifest contract as the rest of the fleet, with explicit missions, prerequisites, and isolated memory. Sentinel · Auditor · Coordinator · Treasurer · Governor Five specialized agents. One consistent confidential execution layer. Building FHESTATE.
2mo ago♥ 9💬 5🔁 3
FHESTATE adds its fourth confidential agent: Treasurer. As confidential applications start handling more treasury logic, one problem becomes important: How do you enforce spending policy without giving an agent the power to move funds? That is the role of Treasurer. Treasurer is designed as a treasury guard, not a wallet operator. A simple flow: Shield Intent → Spend Check The agent can record a spend intent and verify it against its declared policy, but it cannot transfer lamports, unshield assets, or execute a TEE transfer. Daily spending caps are validated at the SDK layer, while mission prerequisites are enforced by the runtime. No plaintext amounts enter agent memory. Only hashes, URIs and mission IDs move through the execution flow. Treasurer now joins: Sentinel · Auditor · Coordinator · Treasurer Four confidential agents. One consistent policy framework. Building the boundaries before giving agents more power. $FHESTATE
2mo ago♥ 12💬 1🔁 5
This is exactly the direction we’re building for. Confidential execution shouldn’t be an afterthought on Solana, it should be part of the base financial stack. Faster execution + scalable privacy + confidential DeFi is a powerful combination. We’re building toward it with FHESTATE. 🟢
2mo ago♥ 11💬 1🔁 4
Phase 6 // MCP Runtime Integration The Agent Manifest already existed in the FHESTATE SDK. The next problem was making it work outside the SDK itself. Our MCP server was running an older package, and every tool call started with a fresh memory state. That meant a real workflow like: Compliance Scan → Seal Record couldn't work reliably. The scan would disappear before the next call. We fixed both pieces. MCP now uses the same manifest catalog as the SDK, including: • Schema 1.0.0 • Sentinel, Auditor & Coordinator • Mission prerequisites • Agent dependencies • Policy validation We also added session-level memory inside the MCP process. Now an agent maintains its own hash chain across a session. So the workflow becomes: Auditor: Scan → Seal Record ✅ Coordinator: Route Intent before Sentinel ❌ Sentinel → Route Intent ✅ Invalid agents, out-of-range values, and skipped prerequisites return the manifest error cleanly instead of crashing the server. And the output remains what we want from a confidential runtime: Hashes. URIs. Mission IDs. Not plaintext state. This means the same policy layer can now move from the TypeScript SDK into an actual MCP workflow. The runtime is starting to behave like one system—not a collection of disconnected components. Building FHESTATE.
3mo ago♥ 10💬 1🔁 3
FHE + blockchain = 1,000,000x overhead. We read that as a design constraint. So we started building it anyway. Now we’re here. $FHESTATE
3mo ago♥ 9💬 1🔁 3

Signal Timeline

DY
@Dylan_HODL followed
BFirst discovered·5mo ago

Score breakdown0–100

🎯Scout conviction
+18.6 / 35
📚Scout consensus
0 / 10
🪪Profile & earliness
+18 / 20
✍️Substance
+5 / 20
🤖AI verdict
+30 / 30
⚠️Penalties
-24 / 40
48
Below threshold (74)
Watching for additional signals.
Followers
202
Account age
9mo
Scouts
1
First seen
5mo ago