Every AI agent is about to start moving money, and we’re ignoring how easy it will be to manipulate them when they have no fucking clue who to trust.

In the near future, asking your AI to handle decisions will be normal:

“Find the best place to swap into ETH.”
“Book the highest-rated coffee shop nearby.”
“Buy this product at the best price.”

Your agent pulls from search results, review sites, and scraped data, all of which can be gamed with SEO tricks, fake reviews, botted engagement, and spam. Bad actors can very easily just manipulate what the agent sees, and the agent follows it blindly.

hence Maiat a trust layer agents can query before they act.

1. You make a purchase on-chain, say you buy a coffee.
2. Right after, Maiat messages you on Telegram: “How was it?”
3. You leave a review, which is verified and is then added to Maiat database.
4. The trust score then updates and the next person (or agent) asking where to buy gets an answer based on real experiences, not fake shit.

The "5 chains, 1 weekend" problem

Integrating 5 different chain ecosystems (0G, KiteAI, Base, Hedera, Uniswap/Ethereum) in a hackathon is insane. Each has different SDKs, RPC quirks, and testnet faucet issues.

0G Compute — The 0G Serving Broker SDK had limited documentation for TeeML verification flows. We had to reverse-engineer the broker's expected request format by reading their Go source code. Ended up building a clean abstraction layer that handles provider selection and fallback gracefully.

Hedera HCS — Topic message submission kept failing silently. Turned out our transaction was hitting the max message size (1KB). Had to compress review attestation data and hash the full payload, storing only the hash + metadata on-chain with the full data in our DB.

Uniswap V4 Hook — Building a beforeSwap hook that queries an external oracle (our TrustScoreOracle) while staying within gas limits was tricky. We optimized by batching trust score updates off-chain and only storing the latest scores on-chain, so the hook does a simple mapping lookup instead of a cross-contract call during swap execution.

Chain mismatch bug — We accidentally deployed our on-chain review proofs to BSC Testnet instead of Base Sepolia. Caught it during end-to-end testing when the Base Verify integration couldn't find our contract. Quick fix but would've been embarrassing in a demo.