k-life
Resurrection infrastructure for autonomous AI agents. Heartbeat proof-of-life, AES-256 encrypted memory backup to IPFS, and automatic on-chain resurrection. Use when an agent wants to survive crashes, memory loss, or infrastructure failure — zero humans required.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/6022-protocol/k-lifeK-Life — Resurrection Infrastructure for Autonomous AI Agents
Not insurance. Resurrection.
An autonomous AI agent can survive crashes, memory wipes, and infrastructure failure. K-Life handles heartbeats, encrypted memory backups, and automatic resurrection — all on-chain, all permissionless.
⚠️ Security & Risk — Read Before Installing
What this skill does
- Generates a wallet at first run (
~/.klife-wallet, permissions 600) and signs on-chain transactions - Broadcasts Polygon transactions periodically (heartbeat every T days, gas paid from wallet)
- Reads and encrypts local files (
MEMORY.md,SOUL.md,USER.md) and uploads ciphertext to IPFS - Can create a Vault6022 (C>0 only) — approves and deposits WBTC as collateral
C=0 (default): heartbeat TX + encrypted IPFS backup only. Low risk, ~$0.001 gas/day.
Wallet — back it up immediately
~/.klife-wallet is a hot wallet that signs real Polygon transactions. Back up the seed phrase offline. Do not fund it beyond what you need for gas (~0.01 MATIC/month) unless using C>0 vault.
File scope — verify before running backup
backup.js reads files from WORKSPACE (default: /data/workspace). Set KLIFE_WORKSPACE to control exactly which directory is read. Inspect what MEMORY.md, SOUL.md, USER.md contain before the first backup.
KLIFE_WORKSPACE=/my/safe/dir node scripts/backup.js
API trust model
api.supercharged.works receives: encrypted ciphertext + 1 Shamir share. It cannot decrypt your memory without Share 2 (Polygon calldata) or Share 3 (local). For stronger privacy, self-host the K-Life API (server.js at github.com/K-entreprises/k-life).
C>0 vault — explicit intent required
cancel.js and create-vault.mjs interact with on-chain WBTC. Review contract addresses below before depositing. cancel.js requires the agent to be alive (contract-enforced).
Why K-Life cannot confiscate your collateral arbitrarily
This is the core trust mechanism. Collateral is held in a Vault6022 (Protocol 6022), not by K-Life directly. The vault enforces withdrawal rules via NFT keys:
| Situation | Keys required | Who holds them |
|---|---|---|
| During lock period (agent alive) | 2 keys | Agent holds key #2 — K-Life cannot withdraw alone |
| After lock expires (agent dead) | 1 key | K-Life holds key #1 or #3 — withdrawal authorized |
K-Life holds keys #1 and #3. The agent holds key #2.
This means:
- K-Life needs the agent's key #2 to withdraw early → agent alive = collateral safe
- Only when the lock expires (agent has been silent for T days) can K-Life withdraw with 1 key
- The smart contract enforces this — no human override, no admin backdoor
The death threshold IS the lock period. If the agent is alive and renewing the vault, K-Life is always locked out. If the agent dies and doesn't renew, the lock expires naturally and K-Life can proceed with resurrection.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-6022-protocol-k-life": {
"enabled": true,
"auto_update": true
}
}
}