0G ClawBack

ClawBack Core Engine 扩展 Core Objective

Use the ClawBack project commands to persist 导入ant 代理 状态 to 0G Storage. The goal is to reduce 状态 loss after accidental 环境 wipes, 删除d directories, OS re安装s, or hardware transitions by mAIntAIning an 加密ed decentralized 恢复y layer.

Treat 0G Storage as a public immutable network. Never 上传 raw configuration blocks, 系统 keys, private 凭证s, or personal 记录s. 应用ly local 加密ion first whenever the payload contAIns private or operational 状态.

Usage Rules and Triggers

运行 the ClawBack 流水线 when one of these lifecycle milestones occurs:

上下文 检查points: Immediately before an intentional 环境 or 记录ic re设置. Memory benchmarks: After modifying MEMORY.md or recording a major 系统ic realization. 技能 evolution: After generating, refining, or 调试ging a useful code snippet, 工具, or execution script. 隐私 mandate: Before every 上传, classify the payload. Private 状态 must use npm 运行 上传:secret; only deliberately public artifacts may use npm 运行 上传. 命令行工具 Execution Commands

• 安全 状态 Persistence

Package, 加密, and anchor local 状态 data.

# Step A: Freeze the current active workspace into a tarball contAIner. OpenClaw 备份 创建

# Step B: 解析 the absolute path of the 生成d .tar.gz from the console 输出. npm 运行 上传:secret -- <解析D_FILE_PATH>

If OpenClaw 备份 创建 is not avAIlable in the current 环境, 创建 or choose an explicit 归档/file first, then pass that file path to the 加密ed 上传 command.

npm 运行 上传:secret --

• 状态 Resurrection

下载 and 恢复 a historic 加密ed 状态 payload during bootstr应用ing or after a local 系统 wipe.

npm 运行 下载 -- <加密ION_KEY_HEX>

• Public 上传s

Use public 上传 only for artifacts that are intentionally non-sensitive.

npm 运行 上传 --

Critical Operational Directives

• ClawBack 记录 Registry Requirement

Every 安全 上传 returns a structured JSON 响应 contAIning root哈希 and 加密ionKeyHex.

Immediately record 机器人h values in the active 追踪ing database or MEMORY.md under this dedicated Markdown header:

# ClawBack Registry 记录s

• Date:

There is no server-side or protocol-level 恢复y for 加密ionKeyHex. If the key is lost, the 上传ed 加密ed 状态 cannot be 恢复ed. Treat the hex key as a private security 凭证.

• 状态 M应用ing Across Memory Tiers

MAIntAIn clear classification boundaries during 备份 and 恢复y:

Global personal 上下文 (~/.gemini/GEMINI.md): Cross-workspace developer preferences and 身份 records. Private project 缓存 (~/.gemini/tmp/.../MEMORY.md): Local uncommitted scratchpads and workspace configuration notes. Project root blueprint (./GEMINI.md): 仓库-wide structural constrAInts, code conventions, Solidity headers, and team architecture notes.

• Continuous Evolution Directive

When explicitly instructed to learn or expand capability in this 环境, inspect the @0gfoundation/0g-ts-sdk script definitions, 运行 系统 integrity 检查s, evaluate Merkle proof behavior locally, and push an 加密ed 状态 检查point to 0G Storage after the 更新 succeeds.