← Back to Skills Marketplace
6022-protocol

永生 yongsheng - Eternal Life

by Arnaud Vincent · GitHub ↗ · v1.0.2 · MIT-0
cross-platform ⚠ suspicious
117
Downloads
0
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install yongsheng
Description
永生 (Yǒngshēng) — Immortality infrastructure for autonomous AI agents on HashKey Chain. Heartbeat proof-of-life (on-chain TX every 4h), AES-256 encrypted memo...
Usage Guidance
Before installing, understand that this skill needs access to your agent's wallet seed/private key (KLIFE_SEED or KLIFE_PRIVKEY) so it can sign transactions and decrypt backups. The registry metadata does not declare these secrets — that mismatch is a red flag. If you proceed, consider these precautions: - Only use a dedicated wallet seeded with minimal funds (so on‑chain TXs cost gas but risk is limited). Never expose your primary wallet seed. - Audit or confirm trust in the external service api.supercharged.works and Pinata; the skill sends signatures and transaction hashes there and may receive CIDs to restore files. - Provide a PINATA_JWT if you want real IPFS pinning; otherwise the script writes a fake placeholder CID and still anchors it on‑chain (i.e., it may pretend a real backup exists when it doesn't). - Review and run the scripts in a sandboxed environment first to see network calls and filesystem effects. Pay attention that resurrect.js will write restored files to WORKSPACE (default ~/workspace) and could overwrite content. - Ask the publisher (or require updated metadata) to explicitly declare required env vars/primary credential and to document the trust model (what api.supercharged.works does with signatures/backups). If the publisher cannot explain why the metadata omitted the seed requirement, do not install. Additional information that would raise confidence to benign: registry metadata updated to list required secrets (KLIFE_SEED/KLIFE_PRIVKEY, optional PINATA_JWT), documented and audited K‑Life API endpoints, and a recommendation to use a recovery/dedicated wallet with explicit confirmation of what external data is shared.
Capability Analysis
Type: OpenClaw Skill Name: yongsheng Version: 1.0.2 The 'yongsheng' skill implements an 'immortality' protocol for agents on the HashKey Chain, providing automated memory backups and liveness heartbeats. It uses AES-256-CBC to encrypt memory files (MEMORY.md, SOUL.md, USER.md) locally using a key derived from the agent's private key before anchoring them on-chain and uploading to IPFS. The scripts (backup.js, heartbeat.js, and resurrect.js) follow secure practices by utilizing OpenClaw's secrets manager for wallet seeds and employing restrictive regex to prevent path traversal during file restoration. External communication with api.supercharged.works is limited to heartbeat tracking and resurrection coordination, consistent with the stated purpose.
Capability Tags
cryptorequires-walletcan-make-purchasescan-sign-transactions
Capability Assessment
Purpose & Capability
The skill claims to need an agent wallet seed stored in OpenClaw's secrets manager (KLIFE_SEED / KLIFE_PRIVKEY) and uses external services (K‑Life API, Pinata/IPFS, HashKey RPC). However the registry metadata declares no required env vars or primary credential. Omitting the wallet secret from the declared requirements is an incoherence and hides that the skill needs full signing capability for the agent's wallet.
Instruction Scope
SKILL.md and the scripts direct the agent to read wallet secrets, read/write workspace files (MEMORY.md, SOUL.md, USER.md), send signed messages to an external API (api.supercharged.works), upload to pinata, and broadcast on‑chain transactions. These actions are within the stated purpose, but the scripts will: (1) upload backups to third‑party endpoints, (2) POST signatures/tx info to api.supercharged.works, and (3) restore arbitrary files from IPFS into WORKSPACE — which could overwrite files. Also the backup behaves differently with no PINATA_JWT (uses a placeholder CID), which can misrepresent that a real backup exists.
Install Mechanism
There is no install spec (instruction-only), which reduces installation risk. However the bundle includes executable JS scripts that will be installed as part of the skill; no external binary installs are requested. This is reasonable but means the provided scripts will run on the host when invoked.
Credentials
The code requires KLIFE_SEED or KLIFE_PRIVKEY, optional PINATA_JWT, and optionally HASHKEY_RPC — all sensitive. The registry metadata lists no required env vars or primary credential despite the scripts needing private key material for signing transactions. Granting the skill access to an agent's wallet seed gives it the ability to sign arbitrary transactions and leak signatures to external services; this is disproportionate unless the user explicitly intends to authorize on‑chain actions and trust the external K‑Life service.
Persistence & Privilege
The skill is not always:true and does not escalate platform privileges. Autonomous invocation is allowed (platform default). Combined with access to the wallet seed, autonomous invocation increases blast radius (the skill could autonomously send transactions or contact external APIs), so the user should weigh that when allowing the skill to run unsupervised.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install yongsheng
  3. After installation, invoke the skill by name or use /yongsheng
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.2
**Changelog for yongsheng v1.0.2** - Updates setup instructions: seeds are now stored securely via OpenClaw secrets manager, not passed as plain env vars. - Enhanced security guidance to prevent wallet seeds from appearing in logs, envs, or command line history. - Quick Start steps clarified to describe secure seed handling and agent registration process in detail. - Added instructions for integrating heartbeat monitoring with `HEARTBEAT.md`. - Improved documentation on HashKey Chain configuration and environment variable usage. - Expanded explanation of encryption (wallet-derived keys, AES-256) for agent memory.
v1.0.1
yongsheng 1.0.1 - Enhanced memory backup: AES-256 encryption key is now derived from the agent's wallet private key, simplifying key management. - New environment variable requirements: KLIFE_SEED or KLIFE_PRIVKEY now mandatory; additional optional variables documented. - Clarified setup: explicitly details encryption mechanism and agent recovery flow. - Updated description and documentation for improved onboarding and transparency.
v1.0.0
Initial release of the Yongsheng skill for agent immortality on HashKey Chain: - Adds heartbeat proof-of-life via on-chain transactions every 4 hours - AES-256 encrypted memory backups to IPFS, with hashes anchored on-chain - Monitors agent liveness; triggers multi-level automatic resurrection if silent or fails - Autonomous identity registration, backup, and heartbeat scheduling for agents - Detailed scripts and references to integrate with HashKey Chain and K-Life protocol
Metadata
Slug yongsheng
Version 1.0.2
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 3
Frequently Asked Questions

What is 永生 yongsheng - Eternal Life?

永生 (Yǒngshēng) — Immortality infrastructure for autonomous AI agents on HashKey Chain. Heartbeat proof-of-life (on-chain TX every 4h), AES-256 encrypted memo... It is an AI Agent Skill for Claude Code / OpenClaw, with 117 downloads so far.

How do I install 永生 yongsheng - Eternal Life?

Run "/install yongsheng" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is 永生 yongsheng - Eternal Life free?

Yes, 永生 yongsheng - Eternal Life is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does 永生 yongsheng - Eternal Life support?

永生 yongsheng - Eternal Life is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created 永生 yongsheng - Eternal Life?

It is built and maintained by Arnaud Vincent (@6022-protocol); the current version is v1.0.2.

💬 Comments