Kamino $KMNO markets "Verifiable Build" as a security guarantee. I checked it. The deployed Kamino Lend binary matches public commit a0876097, verify.osec.io confirms is_verified true. That part holds.

But verified only describes today's binary. The program is upgradeable (is_frozen false). It's controlled by a 5-of-10 Squads multisig with a 1-day timelock, and the Security page never mentions upgradeability at all. You can repeat this yourself. verify.osec.io/status/KLend2g3cP87fffoy8q1mQqGKjrxjC8boSyAYavgmjD shows is_frozen false, and the Solscan Program Multisig tab shows 5-of-10 with an 86,400s timelock.

So the multisig can ship a new unverified build about a day after deciding to. My question for the team: is there a public upgrade notification channel so users can review or exit before a new build takes effect? The fix I'd suggest: publish the upgrade authority, threshold and timelock right next to the Verifiable Build badge, and re-attest after every upgrade so verified can never silently go stale.