Loops HouseKR
Kronos

Event
NEAR HACKATHON
Links
Team
1 member- ONOwner
Oni Samuel Ayomide
Overview
Kronos is a security layer for DeFi lending protocols. Most lending exploits are one transaction that leaves the protocol in a state its own rules forbid: a pumped oracle, a share-price inflation, a stolen admin key listing fake collateral. Kronos checks every transaction's outcome in the same transaction and reverts the ones that break those rules.
How it works:
- Analyze: you point Kronos at a repo. Two independent models (GLM and Qwen) running in a NEAR AI Cloud enclave map the entry points and draft invariants from audited templates. A red team attacks the draft on a fork with forge. Where the models disagree, a human decides; the team approves every rule.
- Enforce: the approved guard (one Solidity modifier, EIP-712 intents, a tiered timelock for admin changes, an outflow circuit breaker) is deployed on Aurora testnet and Base Sepolia. Both pass 30/30 on-chain checks, and 6/6 attack replays are blocked on MiniLend.
- Respond: a NEAR registry contract plus a function-call key that can only call tighten. With NEAR Chain Signatures, the registry builds the EVM tightenOutflow transaction itself and NEAR's MPC network signs it, so one tighten-only NEAR key protects every EVM chain and we never hold an EVM monitor key. Loosening is refused at three layers: NEAR, the registry and the guard.
All testnet. ZK proofs and NEAR Intents are roadmap, not claimed. The README has a reproducible quick start, live addresses and a section on what Kronos can't stop.
I also submitted a separate, independent project: BuilderOS (github.com/Wangsamuels/BuilderOS).