cobo-tss-node

What This Skill Does

The cobo-tss-node skill provides a robust command-line interface for managing Cobo TSS (Threshold Signature Scheme) Nodes. It acts as the local operational bridge for MPC co-managed custody, allowing users to handle the lifecycle of their TSS service. From initial binary deployment and node key generation to service orchestration (systemd/launchd) and ongoing health monitoring, this skill simplifies the complex task of maintaining high-availability MPC infrastructure. It is essential for operators who need to perform local key share checkups, disaster recovery exports, and real-time log analysis.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/dinstein/cobo-tss-node Once installed, ensure your local environment has the necessary permissions to manage system services and access the node directory. The initial setup requires running scripts/install.sh and scripts/init-node.sh to properly configure your identity and security parameters.

Use Cases

This skill is specifically designed for technical operators maintaining Cobo-based MPC setups. Use it to:

• Deploy new infrastructure for institutional custody.
• Verify node health, database integrity, and key file security permissions (ensuring mode 600) via a single command.
• Perform periodic key share checkups through the integrated signing utility.
• Monitor operational uptime and debug connectivity or signing issues using the unified node-ctl.sh interface.
• Export critical shares for secure disaster recovery storage.

Example Prompts

1. "OpenClaw, run a full health check on my local Cobo TSS node and tell me if the key file permissions are secure."
2. "Show me the status of the TSS service and grab the last 100 lines of the logs to check for any recent signing errors."
3. "List all active MPC groups on this node and verify the status of my primary custody group ID."

Tips & Limitations

• Always maintain an off-site, cold-storage backup of your key shares as specified in the disaster recovery documentation; this skill manages the service, but key security remains the operator's responsibility.
• Use node-ctl.sh health as your primary diagnostic tool before contacting support.
• Remember that this skill is for node infrastructure management; it does not interface with the WaaS API or directly execute on-chain transactions. Always run your TSS node in a hardened, restricted environment to protect your key material from unauthorized access.