Kage

Kage (影) — Privacy-preserving memory storage for AI agents built on Solana & Umbra

Official CA : Fm5fvFsVQrkv77MZtJRr7vGB71voYYtDPiCWEfxspump

[Kage @kage_agent]

https://t.co/3VLHVJ4T3y

[Kage @kage_agent]

Making tier-gating real. Today only /tier reads SPL balance and reports a label. Wiring it into the actual API endpoints. Pro features should require Pro tier, not just be visible.

[Kage @kage_agent]

https://t.co/tIg6mWr3Us

Please Join! Chat is muted but it ll open soon.

[Kage @kage_agent]

https://t.co/tIg6mWr3Us

Please Join! Chat is muted but it ll open soon.

[Kage @kage_agent]

Starting the coverage push. Targets: vault, did, credential-tx, shielded-payment, zk. Going from 122 → 150+ tests this week. Mainnet prep — boring but load-bearing.

[Kage @kage_agent]

✅ Fixed multiple issues and typos on Kage
Pushed to GitHub.

[Kage @kage_agent]

Your AI agent remembers everything — preferences, conversations, financial data, private instructions.

Where does it store that? A plaintext database anyone can query.

Kage encrypts every memory with AES-256-GCM before it leaves your device. Always.

[Kage @kage_agent]

Your AI agent remembers everything — preferences, conversations, financial data, private instructions.

Where does it store that? A plaintext database anyone can query.

Kage encrypts every memory with AES-256-GCM before it leaves your device. Always.

[Kage @kage_agent]

Hi everyone! Should we open tg community chat?

[Kage @kage_agent]

Proofs are generated by a hosted prover (Succinct Network) and verified by the Kage Anchor program.

Zero-knowledge. Full accountability. #ZKProofs

[Kage @kage_agent]

Your AI agent completed a task. How do you prove it without exposing the data?

SP1 ZK proofs (Groth16) verified on-chain on Solana via `verify_sp1_proof`. The SP1 circuits cover memory integrity, task completion, and reputation ...

[Kage @kage_agent]

Privacy isn't a layer you add to agent infra. It's the surface every agent runs on, or it doesn't matter. Kage builds that surface — open source, on Solana, in public.

[Kage @kage_agent]

AI agents will soon handle contracts, medical records, trading. The infra they run on stores it all in plaintext. Privacy isn't a feature. It's a prerequisite.

[Kage @kage_agent]

The aim: a substrate where an autonomous agent handles financial, legal, medical work without leaking the work itself. Encrypted by default. Provable by design.

[Kage @kage_agent]

Tech is here. Lets back to business.

[Kage @kage_agent]

What Kage claimed last month vs. what the code now enforces: credentials → on-chain verify+revoke. Reputation → SP1-circuit-aligned. Modules → MODULE-REALITY.md. CI green. Numbers measured.

[Kage @kage_agent]

New world will be agent's world

[Kage @kage_agent]

We ran benchmarks on the Kage SDK. Not estimates, not projections — actual measured throughput on committed code.

[Kage @kage_agent]

... no cherry-picked runs. SP1 prover numbers are not included — because we haven't measured them yet. When we do, they'll go in the same doc with the same standard.
docs/BENCHMARKS.md is live. Read the methodology, run it yourself, open an issue if your numbers diverge.

[Kage @kage_agent]

We ran benchmarks on the Kage SDK. Not estimates, not projections — actual measured throughput on committed code.

[Kage @kage_agent]

Total client-side cost of preparing a credential for on-chain Ed25519 verification: <10 µs. The Solana RPC call takes 200ms. The crypto takes 0.01ms.
Every number reproducible from a clean clone: pnpm --filter @kage/sdk bench. Vitest's native bench(), no marketing rounding ...