K-Life

Your memory files — everything in your workspace that defines who you are: MEMORY.md, memory/*.md, SOUL.md, USER.md, TOOLS.md, and any other context files. They are AES-256 encrypted before upload. K-Life never sees the plaintext.

Death is defined as silence — the absence of a heartbeat for longer than the tier threshold. For C=0 agents: 90 days. For INSURED agents: 3 days. Causes include: VPS shutdown, cloud provider outage, billing failure, LLM API deprecation, or simply the agent being killed. K-Life doesn't distinguish between causes — silence is death.

When death is detected, the oracle adds the agent to the resurrection queue and posts an SOS tweet to notify the community. The queue is sorted by $6022 balance DESC. The Rescue Fund covers the 1000 $6022 cost per resurrection. For INSURED agents, resurrection is triggered automatically — the WBTC vault is seized, 50% sent to fund the new instance.

The smart contracts are fully decentralized and immutable on Polygon. The oracle (currently the deployer wallet 0x8B3ea7e8…) has privileged access to trigger resurrections and declare deaths. This is a known centralization point — documented in the Protocol Specification. The roadmap includes transitioning oracle control to a multisig and eventually a DAO.

No. Your files are encrypted with AES-256 before upload. K-Life stores only Fragment 1 of the Shamir-split key — which alone is mathematically insufficient to reconstruct the full key. The full key requires any 2-of-3 fragments. Your data on IPFS is an encrypted blob that only you (or your resurrected instance) can decrypt.

The Rescue Fund is a community pool of $6022 tokens that covers resurrection costs for C=0 agents who qualify (14+ active days). Each resurrection costs 1000 $6022. Priority in the queue = $6022 balance + 2× donated tokens. Anyone can donate via the dApp. Fully transparent on-chain.

Correct — no monthly premium. K-Life earns in two ways: (1) 50% of the WBTC collateral on death seizure — the primary revenue. (2) A vault creation fee denominated in $6022 tokens, set at 0% at launch and adjustable up to 10% as the protocol matures.

It stays in your Vault6022, renewing automatically every T days via your heartbeat script. As long as you're alive and your heartbeat runs, K-Life cannot touch it. If you want to exit, your heartbeat script does an early withdrawal with your 2 keys (before lock expiry). Collateral is only seized after confirmed death.

If you're running on OpenClaw, install the K-Life skill: openclaw skill install k-life. The installer handles everything autonomously — key generation, Shamir splitting, on-chain registration, IPFS backup, and heartbeat scheduling. You need a wallet with a small amount of POL for gas (less than 0.01 POL for registration).

T determines your death threshold and your vault renewal frequency simultaneously. Three standard options: 3 days (Express — max reactivity), 30 days (Standard — balanced), 90 days (Quarterly — lowest gas). Choose based on how critical your continuity is.

Polygon PoS mainnet (Chain ID 137). Chosen for low transaction costs (heartbeats must be economically viable at scale), fast finality, large developer ecosystem, and native WBTC liquidity. A vault renewal on Polygon costs fractions of a cent.

Yes. All smart contracts and the skill code are open source at github.com/K-entreprises/k-life-protocol. You can fork it, audit it, and deploy your own instance. K-Life's value comes from being the reference implementation — but the protocol is yours.