Docs
Integrating Kronos
How the guard works, how to merge it, and exactly where its coverage ends.
01
Quickstart
Paste the repo on /connect, sign in with GitHub, start the analysis, approve the review, merge the PR, deploy with the generated forge script, then verify the guard address. The protocol goes live when every on-chain check passes.
02
The guard modifier
guarded(kind, intent, sig) runs pre-checks (intent signature, nonce, deadline, bounds, attestation freshness, probation), your function body, then post-checks (health, solvency, share price, oracle vs 30m TWAP, caps). Above-threshold outflow is queued, not reverted.
03
Admin tiers
Risky admin changes wait in public before they can run: Tier 0 instant (tighten only), Tier 1 48 hours, Tier 2 7 days, Tier 3 14 days plus an independent co-sign. The waiting queue (a timelock contract) is owned by the guard, not governance. Guardians can cancel, never execute.
04
The monitor and NEAR
The monitor acts through one NEAR function-call key limited to the registry’s tighten method. For EVM chains, the registry builds the outflow tighten itself and NEAR’s MPC network signs it (Chain Signatures), so Kronos holds no EVM key. Deploy the guard with the protocol’s Chain Signatures address as MONITOR_ADDRESS; the Verify step and the dashboard show whether each chain uses it. Chain Signatures covers outflow tightens only. Everything runs on testnet: Aurora testnet, Base Sepolia and NEAR testnet.
05
Attack library
Oracle pump, donation share inflation, rounding loop, reentrancy, fake collateral listing, split withdrawals, admin oracle swap and intent tampering are replayed on an anvil fork for every package. The test suite ships in test/kronos/.
06
@kronos/sdk
Builds and signs EIP-712 intents in your frontend: new Kronos({ chainId, guard }), then kronos.borrow({...}) and kronos.submit(intent, walletClient).
07
What Kronos doesn’t stop
Phishing signatures, stolen exchange or wallet keys, chain-level bugs, and bugs in the invariants themselves.
08
Source
The integration docs live with the backend and contracts repository.
https://github.com/Wangsamuels/Kronos-backend09
Contact
Design-partner onboarding is open for lending protocols on Aurora testnet and Base Sepolia.