KPK primary sources — 2026-04-28

Project

• Name: KPK (formerly karpatkey)
• URL: https://kpk.io/
• Category: onchain asset management / treasury mandates / curated DeFi vault infrastructure / tokenized fund platform
• Whitepaper status: No canonical standalone KPK or karpatkey whitepaper/litepaper found in this pass.

Primary sources reviewed

1. Homepage: https://kpk.io/

   • Frames KPK as “scalable onchain asset management” with disciplined risk frameworks, automation, and policy-enforced execution.
   • Splits the product into Funds, Vaults, and Treasury mandates rather than presenting only advisory services.
   • Links directly to docs, analytics, and GitHub, which is a useful signal that operations and infrastructure matter to the public product surface.

2. Canonical docs introduction: https://docs.kpk.io/

   • Calls the documentation the canonical reference for KPK’s onchain asset-management infrastructure and curated products.
   • Says KPK (formerly karpatkey) is a non-custodial onchain asset manager active since 2021 that has managed billions in treasury assets for decentralized organizations.
   • Explicitly says KPK leverages Safe smart accounts and onchain permission systems.

3. Docs ask endpoint — products/infrastructure: https://docs.kpk.io/introduction.md?ask=What%20products%20does%20KPK%20offer%20and%20what%20infrastructure%20do%20they%20use%3F

   • States that KPK has two main product tracks: Funds and Vaults.
   • Says Funds use onchain fund infrastructure including Safe smart accounts, policy smart contracts, onchain NAV/share-price accounting, ERC-20 fund shares, and multichain EVM support.
   • Says Vaults are curated yield products on protocols such as Gearbox, Morpho, and Euler.

4. Docs ask endpoint — risk/automation: https://docs.kpk.io/introduction.md?ask=How%20does%20KPK%20describe%20its%20risk%20controls%20and%20automation%3F

   • Describes KPK’s controls as layered, bounded, and policy-driven.
   • Says automation is deterministic and deliberately limited: agents may monitor, calculate allocations within predefined boundaries, and execute within preset conditions, but cannot invent new strategies or exceed approved limits.
   • Strong evidence that KPK should be categorized as constrained treasury/control-plane infrastructure, not just discretionary advisory.

5. GitHub organization: https://github.com/karpatkey

   • Public org exposes repos including defi-kit, client-configs, karpatkit, kpk-token, onchain-investment-vehicles, and Securitize_NAV.
   • Repo inventory reinforces that KPK spans permissions tooling, fund infrastructure, and operational/configuration software rather than only strategy marketing.

6. DeFi Kit README: https://raw.githubusercontent.com/karpatkey/defi-kit/main/README.md

   • Describes DeFi Kit as “Permissions for Zodiac Roles covering interactions with DeFi protocols.”
   • Exposes both a TypeScript SDK and REST API, plus protocol-specific permission-generation workflows.
   • Important architecture clue that KPK’s treasury-management model is implemented through reusable Safe/Zodiac permission middleware.

7. Onchain investment vehicles README: https://raw.githubusercontent.com/karpatkey/onchain-investment-vehicles/main/README.md

   • Documents kpkShares as a tokenized fund implementation with subscriptions, redemptions, operator approval, fee modules, request TTLs, and multi-asset support.
   • Shows that KPK has first-party fund-share infrastructure rather than only curation/advisory language.
   • Helpful for understanding where operator discretion exists and how it is bounded in product design.

Takeaways

• KPK is best cataloged as onchain asset-management and treasury-control-plane infrastructure, not merely as a DAO treasury consultant or delegate.
• The two most important architecture clues are the Safe/Zodiac permission tooling (defi-kit) and the tokenized-fund share model (kpkShares).
• The docs corpus is the real source of truth; a classic whitepaper does not appear necessary to understand the system.