evolve-soul-registry

Coordinate soul-registry changes across Solidity contracts, DynamoDB state, and governance workflows.

3|Updated Feb 3, 2026
One-click install
npx skills add https://github.com/equaltoai/lesser-host --skill evolve-soul-registry
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evolve-soul-registry
Source: https://github.com/equaltoai/lesser-host/tree/main/.codex/skills/evolve-soul-registry
Command: npx skills add https://github.com/equaltoai/lesser-host --skill evolve-soul-registry

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates end-to-end evolution of the soul registry by coordinating on-chain contracts, off-chain state, and governance workflows, reducing risk of divergence and manual missteps.

Core Features & Use Cases

  • Contract integrity checks (Slither + hardhat + solhint) and deployment discipline across Solidity and Go components.
  • Off-chain reconciliation and state synchronization with DynamoDB mirrors to keep on-chain references in sync.
  • Safe-ready governance payload preparation and multisig coordination for on-chain mutations (including mint-signer handling and namespace updates).

Quick Start

Describe your planned soul-registry change and let this Skill outline the end-to-end coordination, governance steps, and validation required.

Frequently Asked Questions about evolve-soul-registry

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I coordinate soul-registry changes across on-chain contracts and off-chain data stores?

Soul-registry changes are coordinated by validating on-chain Solidity and Go code, reconciling off-chain DynamoDB state, and preparing Safe-ready governance payloads for multisig approval.

What is the best way to synchronize off-chain DynamoDB state with on-chain soul-registry contracts?

Off-chain reconciliation keeps DynamoDB mirrors in sync with on-chain references, reducing the risk of state divergence during soul-registry mutations and namespace updates.

How do I validate Solidity contracts before deploying soul-registry updates from testnet to mainnet?

Contract integrity is validated using Slither, Hardhat, and Solhint checks, ensuring deployment discipline and security before soul-registry updates move from testnet to mainnet.

Can I use this to prepare governance payloads for mint-signer key updates?

Yes, Safe-ready governance payload preparation and multisig coordination are supported for on-chain mutations, specifically including mint-signer key handling and namespace updates.

Does this workflow handle both Solidity contracts and on-chain Go code for registry mutations?

Yes, the workflow coordinates and validates changes across Solidity contracts and on-chain Go code, applying contract integrity checks and deployment discipline to both components.

Why do I need end-to-end coordination for soul-registry namespace updates?

End-to-end coordination automates the evolution of the soul registry across on-chain contracts, off-chain state, and governance workflows, reducing the risk of divergence and manual missteps.