Category: non-custodial onchain asset management / DAO treasury-management infrastructure / finance-ops and permissions stack
Summary: KPK is best understood not as a generic treasury consultant but as a productized treasury-control layer for DAOs and other onchain organizations. Its own materials emphasize non-custodial asset management via client-owned Safes, explicit permission scopes, onchain policy enforcement, risk-tiered allocation frameworks, and automated operators. The important mechanism is not just “managing treasury assets” but packaging treasury discretion into a repeatable combination of Safe-based authority, Zodiac-style permissions, curated DeFi access, and real-time monitoring.
What it does:
Manages treasury mandates, funds, and curated vaults for DAOs and institutions
Uses client-owned Safes and limited permissions instead of taking custody of assets
Curates assets, protocols, and strategies using formal due-diligence, tiering, and allocation frameworks
Runs automated and manual operator workflows for subscriptions, redemptions, liquidity management, bridging, and strategy execution
Publishes open-source tooling for permissions, client role configurations, and DeFi action templates built around Zodiac Roles and Safe workflows
Key claims:
KPK’s docs call it a non-custodial onchain asset manager and frame its documentation as the canonical reference for its asset-management infrastructure, curated products, governance, and risk controls
The About page says the operating model was established around non-custodial, permission-based asset management via Safe and Zodiac Roles Modifier, which makes KPK a control-surface builder as much as an allocator
The funds docs describe contract-level Admin and Operator roles, with KPK fund operators and automated agents handling approvals, liquidity management, bridging, and deployment into pre-approved strategies
The investment framework says allocation decisions are derived from structured collateral, protocol, and blockchain assessment and then operationalized through onchain Permission Policies, which is a stronger claim than ordinary advisory work
The vault risk framework describes over 65 due-diligence data points across smart-contract logic, dependencies, governance controls, and market conditions, plus tiered exposure rules and ongoing monitoring of governance actions, upgrades, oracles, utilization, bad debt, and control-structure changes
KPK’s public client-configs repo shows concrete per-client role and permission configuration workflows that export payloads for Zodiac Roles / Safe Transaction Builder execution
Its defi-kit repo further suggests KPK is productizing treasury permissions into reusable protocol-action templates rather than handling every mandate as bespoke human process
Whitepaper: No canonical standalone whitepaper or litepaper surfaced in this pass. The strongest primary materials were KPK’s docs, about page, risk/investment framework pages, and public permissioning repos; see ../whitepapers/kpk-primary-sources-2026-05-07.md.