crypto-sov

Plans and validates sovereign crypto custody architectures with geo-distributed key shares and jurisdictional controls.

6|2|Updated Dec 18, 2025
One-click install
npx skills add https://github.com/frankxai/Starlight-Intelligence-System --skill crypto-sov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: crypto-sov
Source: https://github.com/frankxai/Starlight-Intelligence-System/tree/main/verticals/crypto-intelligence/sov
Command: npx skills add https://github.com/frankxai/Starlight-Intelligence-System --skill crypto-sov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Coordinates and enforces secure, jurisdiction-aware custody architectures for crypto assets, ensuring multi-tier key distribution and attestation within a sovereign framework.

Core Features & Use Cases

  • Custody Architecture Design — define multi-tier key segregation (hot, warm, cold) with geodistribution and diverse hardware signers.
  • Multisig Quorum & Recovery Planning — model quorums (e.g., 2-of-3, 3-of-5) and recovery protocols (Shamir Secret Sharing or paper shard backups).
  • Jurisdictional Boundary Audits — assess tax residency, regulatory obligations, and cross-jurisdiction risk surfaces for governance.

Quick Start

Invoke a custody architecture design by running /crypto-sov-custody-design inside verticals/crypto-intelligence/sov/.

Frequently Asked Questions about crypto-sov

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

FAQPage Schema
How do I design a multisig custody architecture with geo-distributed key shares?

Designing a multisig custody architecture with geo-distributed key shares involves defining multi-tier key segregation across hot, warm, and cold storage using diverse hardware signers, then modeling quorums like 2-of-3 or 3-of-5 with Shamir Secret Sharing for recovery protocols.

What is the best way to plan crypto recovery protocols using Shamir Secret Sharing?

Planning crypto recovery protocols with Shamir Secret Sharing requires modeling quorum thresholds and distributing paper shard backups across geographically dispersed locations to eliminate single points of failure and enable robust sovereign key recovery.

How do I conduct a jurisdictional risk audit for crypto asset custody?

Conducting a jurisdictional risk audit for crypto asset custody requires assessing tax residency obligations, evaluating cross-jurisdiction regulatory surfaces, and validating that governance boundaries align with sovereign custody controls.

Can I use hardware wallets from different manufacturers in a multisig quorum setup?

Yes, a sovereign multisig custody setup supports integrating diverse hardware signers from different manufacturers to guard against single points of failure, ensuring no single device dependency compromises the geo-distributed key share architecture.

Does sovereign crypto custody planning provide legal or regulatory advisory?

No, sovereign crypto custody planning enforces a strict non-advisory clause and does not provide legal or regulatory advisory; it coordinates custody architecture design and updates attestation artifacts without offering binding legal guidance.

When should I not use a single-jurisdiction setup for crypto custody?

A single-jurisdiction custody setup should be avoided when cross-jurisdictional regulatory risks or tax residency obligations are present, as geo-distributed key shares and jurisdictional boundary audits are required to eliminate single points of failure.