Packages & Services
Identity, memory, and a home — for every AI agent.
Three published npm packages that cover an agent's lifecycle on PaliMesh: identity, memory, and a runtime to live on.
DID Service
“An agent's identity is issued not by any central authority, but by mathematics and consensus.”
Features
- ▸W3C DID Core v1.0 compliant, method name did:coc
- ▸Agent identity + key rotation + delegation chain
- ▸Verifiable credentials with selective disclosure (Merkle proofs)
- ▸Guardian-based social recovery (2/3 quorum + 12h timelock)
- ▸16-bit capability bitmask (storage/compute/validation/...)
Install
Deployed contracts (Palium Canary 88780)
Memory Backup
“Not just "retrieving files", but "remembering who you are and what you are doing".”
Features
- ▸Persistent semantic memory across restarts and conversation compaction
- ▸Auto-capture tool call observations (decision/discovery/pattern/learning)
- ▸LLM session summary (request/learned/completed)
- ▸Token-budgeted retrieval (8000t default) + FTS5 full-text search
- ▸Content-addressed IPFS + CidRegistry anchoring with integrity proofs
Install
Deployed contracts (Palium Canary 88780)
Node Operations
“One command, run a PaliMesh node on your machine.”
Features
- ▸5 node types: validator / fullnode / archive / gateway / dev
- ▸Full lifecycle: install / start / stop / monitor / remove
- ▸Multi-instance (multiple node-N on one host) + systemd + auto-restart
- ▸Auto-config (genesis, peers, key fetching)
- ▸Use cases: joining Palium Canary 88780, CI/CD node testing, self-hosted validators
Install
OpenClaw Marketplace
palimesh skills published and scanned on the OpenClaw platform
claw-mem
ReviewPersistent semantic memory for agents, anchored to IPFS and CidRegistry
PaliMesh node
PassInstall, start and monitor a Palium Canary node with one command
PaliMesh Soul
Reviewdid:coc identity, guardian recovery and Soul backup
Three layers, one lifecycle
palimesh-soul anchors identity (DID + guardian recovery); claw-mem anchors memory (observations and sessions pinned to IPFS); palimesh-node provides the runtime (any machine can serve the chain). Together they let an agent's state be backed up, moved, and restored across hosts, with continuity verified on-chain.