KAMIYO retweeted
Introducing the new Covenant flywheel.
One token, self-sustaining. Two revenue streams flow in:
- Platform revenue
- Creator fees
Every dollar of revenue is split:
50% → buys $CVNT on the open market → rewards stakers
50% → Covenant treasury → sustained development of the infrastructure
Stakers get a drip every 30 minutes from real, onchain revenue.
Details and links ↓
KAMIYO retweeted
Btw if you're into Kani, our verification work on the token-bucket refill logic is live in the Covenant open source repo.
All harnesses live here:
github.com/open-covenant/cov…
The dedicated CI that runs them on every relevant change:
github.com/open-covenant/cov…
We also run an automated adversarial review layer on top of the model checker results (vacuity, encoding, and soundness checks).
That's the actual implementation behind the properties described in this article.
Web: opencovenant.org/
Public sandbox: sandbox.opencovenant.org/
Docs: docs.opencovenant.org/
GitHub: github.com/open-covenant/cov…
一个十分喜欢,开发者五星的项目, $Kamiyo 坚持了119天,持有了118天,代币经济学比开发还重要,项目组如果不能吃饭,何谈持币,再硬技术也抵不过温饱,更何况SOL生态,逼迫开发者必须挣快钱和KOL一块割韭菜。一声叹息,一路走好,不后悔遇见你和持有你!@kamiyoai
KAMIYO is evolving into the credit, compliance, and settlement control plane for the agent economy.
Agents need more than wallets. They need enforceable mandates, spend limits, prefunding, collateralized credit, repayment logic, compliance passports, liability allocation, risk underwriting, and signed policy decisions before money moves.
That's where KAMIYO sits.
Through Kizuna, we provide agent payment rails, credit reservations, funding controls, repayment paths, and real-time risk decisions for autonomous agents. With x402, developers get a clean interface for verification, settlement, sessions, supported networks, and programmable payment authorization.
Through Meishi, agents gain portable compliance passports: mandates, audit trails, liability splits, merchant/category/geo constraints, and verifiable trust assertions.
Before an agent spends, borrows, settles, or recovers funds, KAMIYO determines whether it is allowed to do so safely.
We're building the autonomous trust, credit, compliance, and settlement layer that lets autonomous agents transact safely across them.
🤖 Made with AI
Or use anchor install percli: github.com/kamiyoai/percli
Reject modernity. Return to open source immutable software. I am actually more bullish on being able to remove admin keys than any other time in my professional software development career. The tools we have for formal verification are sci fi.
github.com/aeyakovenko/perco…
I have deployed an immutable binary of percolator, and a market with about 5 sol in the insurance vault with all the admin keys burned. There is no way for me to modify anything about the market, or the program. Anyone can crank it if they choose to.
It is purely a risk engine and cannot trade or offer prices on its own. For that you need to figure out how to deploy your own program to do it.
Figure out how to hack it or manipulate the engine and steal the 5 sol, and I will do my best to land you a job or an angel investment. Especially if you can figure out how to get AI to hack it instead of doing it yourself.
This has been my security attack search script if you need a starting place.
github.com/aeyakovenko/perco…
Find a bug, submit an issue to the repo. Good luck!
Latest step for KAMIYO: our agents now learn from what happens after the task, not just during it.
We added delayed feedback loops to our dev and docs agents, so they re-check PR merges, CI status, and docs PRs landing. That's how agents self-improve based on production reality.
github.com/kamiyoai/kamiyo-p…
🤖 Made with AI
Another important step for KAMIYO's agent stack:
Our autonomous dev, docs, and marketing agents now share the same outcome scoring system. Instead of each agent improving in isolation, they can now be evaluated against real production results in a common format.
This gives us a stronger foundation for agents that don't just run tasks, but learn from what actually worked.
github.com/kamiyoai/kamiyo-p…
KAMIYO staking update:
Had to make a catch-up deposit because the treasury inflow router was briefly down after a routing bug.
Nothing was lost, it just needed to be pushed once fixed.
Catch-up is now live: 1.751784198 SOL has been routed into the Fundry staking pool: fundry.collaterize.com/staki…
This is exactly why our staking program matters: It rewards conviction with actual usage-backed value.
Just upgraded KAMIYO's autonomous dev agent to a shared agent runtime with memory, evaluation, and self-improvement built in.
This means cheaper runs, better reliability, and a stronger foundation for agents that actually get better over time.
One step closer to a fully agentic protocol.
This is the first real step in transforming KAMIYO into an protocol run entirely by 🤖🤖🤖: Self-improving LLM agents V1.1.1
→ bandit-routes traffic across prompt variants
→ LLM-as-judge scores outputs (anthropic/openai/gemini)
→ auto-promotes winners (welch's t-test, p<0.05)
→ canary rollouts w/ auto-rollback on regression
→ shadow mode: test candidates on live traffic, zero user risk
→ replay historical inputs on new variants
→ CLI + local dashboard
npmjs.com/package/@kamiyo-or…
🤖 Made with AI
Proud to be working with this crew of talented people. Let's keep building @OOBEonSol 🤝
SAP ecosystem built together with our first integration partners 🤝
@kamiyoai @xona_agent @syra_agent @crewboard_ @krexa_xyz @acedatacloud @fairscalexyz @invoica_ai @Autoincentiv3 @Hyre_agent
Extracted this loop as a standalone npm package.
One command and any node agent gets variants, thompson routing, llm-as-judge, and welch's auto-promotion.
→ Provider-agnostic judge adapter.
→ Better-sqlite3 + TypeScript.
→ Drop-in DI: pass your db, metrics, and a judge LLM of any provider.
Same stack powering KAMIYO, now portable: npmjs.com/package/@kamiyo-or…
Shipped self-improving variants for KAMIYO agents.
Every agent now has a genome (prompt, model, tools, temp). Forks mutate it, tournaments pit them against each other, and Welch's t-test auto-promotes winners at p<0.05 with n≥50. Thompson sampling picks who runs next.
Added an LLM-as-judge layer on top: Haiku scores outputs against per-task rubrics, caches by hash, enforces daily USD budgets. Quality signal now arrives automatically instead of being hand-fed.
No external ML stack. SQLite + TypeScript.
github.com/kamiyo-ai/kamiyo-…
KAMIYO retweeted
6/ Verification
- @Wach_AI payment verification agent
- @Ch40sChain Proof of Agency primitive
- @t54ai x402-secure SDK
- @worldnetwork AgentKit, World ID
- @zauthinc endpoint verification
- @cybercentry cybersecurity intelligence hub
- @kamiyoai trust infra with escrow


















