Chia SplitXCH

Create SplitXCH royalty split addresses from plain language descriptions. Use when the user wants to split XCH payments, royalties, or revenue between multiple recipients. Triggers on "split royalties", "royalty split", "splitxch", "split XCH between", "revenue share", "payment split", "basis points split", or any request to divide Chia payments among wallets. Supports nested/cascading splits for complex hierarchies and 128+ recipients.

Security Scan

The skill's files and instructions are consistent with a SplitXCH client that builds payloads and posts them to splitxch.com; nothing in the bundle attempts unrelated file/system access or requests unrelated credentials, but the package relies on an external service of unknown provenance and omits declaring required CLI tools.

Purpose & Capability

The name/description, SKILL.md, API reference, and script all align: the skill parses user descriptions, computes basis points, and posts a JSON payload to an external SplitXCH API to obtain a computed XCH split address. However, the metadata claims no required binaries while the provided script depends on bash, curl, and jq — the omission is a minor inconsistency (not necessarily malicious) that may cause runtime failures.

Instruction Scope

The runtime instructions stay within the stated purpose: parse inputs, validate addresses/points, optionally perform a dry run, then call the third-party API to create splits. The SKILL.md does not instruct the agent to read unrelated files, environment variables, or system configuration. It does instruct sending recipient names and addresses to an external endpoint (splitxch.com), which is expected for this service but worth noting.

Install Mechanism

There is no install spec (instruction-only with a small helper script). No downloads or archive extraction occur. The bundle contains a small shell script and documentation, which is low-risk from an installation perspective.

Credentials

The skill requests no environment variables, credentials, or config paths, which is proportional for a client that posts payloads to an external web API. There are no unexplained secret requests.

Persistence & Privilege

The skill is not forced-always and does not request persistent system privileges or modify other skills. It uses the default autonomous-invocation setting (normal for skills).

Assessment

This skill appears coherent: it builds a JSON payload and posts it to https://splitxch.com to obtain a split address. Before installing, verify the reputation/trustworthiness of splitxch.com (the skill's source/homepage is missing). Ensure the runtime environment has bash, curl, and jq available (the metadata doesn't declare these). Understand that recipient names and XCH addresses will be sent to the external service — do not submit private data you don't want shared. If you prefer not to call the external API, use the skill's dry-run mode to compute basis points locally and only use the API after you trust the endpoint.

SplitXCH Royalty Split Builder

Create complex XCH royalty distribution addresses from natural language descriptions.

How It Works

SplitXCH creates special Chia blockchain addresses that automatically split incoming payments to multiple recipients based on configured percentages. The API computes a puzzle address; any XCH sent to that address gets distributed automatically on-chain.

Workflow

1. Parse the user's plain-language split description into recipients with percentages
2. Convert percentages to basis points (scale to 9850 total, API adds 150 bps / 1.5% fee)
3. For nested splits (splits-of-splits), build bottom-up: create leaf splits first, then use their addresses as recipients in parent splits
4. Call the SplitXCH API via scripts/splitxch.sh or direct curl
5. Return the generated split address and a summary

Basis Points Conversion

• 10,000 bps = 100%. API fee = 150 bps (1.5%). Recipients get 9,850 bps total.
• Formula: points = round(percentage / 100 * 9850)
• Adjust last recipient so points sum to exactly 9850.

Example: "Split 60/40 between Alice and Bob"

• Alice: round(0.60 * 9850) = 5910
• Bob: 9850 - 5910 = 3940

Building the API Payload

{
  "recipients": [
    {"name": "Alice", "address": "xch1...", "points": 5910, "id": 1},
    {"name": "Bob", "address": "xch1...", "points": 3940, "id": 2}
  ]
}

Save to a temp file and run:

bash <skill_dir>/scripts/splitxch.sh /tmp/split-payload.json

Nested Splits (>128 recipients or hierarchies)

When the user describes groups within groups:

1. Create each leaf-level split first via the API
2. Use the returned address as a recipient in the parent split
3. Each split level incurs its own 150 bps fee

Example: "Team A (Alice 50%, Bob 50%) gets 70%, Charlie gets 30%"

1. Create Team A split: Alice 4925 + Bob 4925 = 9850 → returns xch1teamA...
2. Create parent split: TeamA address 6895 + Charlie 2955 = 9850

Validation Rules

• All addresses must start with xch1 and be valid bech32m
• Max 128 recipients per split
• All addresses unique within a split
• Each recipient's points > 0
• Points must sum to exactly 9850

Output Format

After creating a split, present:

1. Split Address: The generated xch1... address
2. Summary Table: Each recipient's name, address (truncated), and percentage
3. Fee Note: "SplitXCH takes a 1.5% platform fee per split level"
4. Usage: "Send XCH to this address and it will automatically distribute to all recipients"

If nested, show the full tree structure.

API Reference

For detailed API docs, validation rules, and error handling, see references/api.md.

Important Notes

• The user MUST provide valid XCH wallet addresses for all recipients. If addresses are missing, ask for them before calling the API.
• If the user only provides names and percentages without addresses, list what's needed and ask.
• For dry runs / previews, show the calculated basis points without calling the API.