canton-network-repos

Align Canton Network component versions and package IDs across LF releases.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/awfixers-stuff/opencode-config --skill canton-network-repos-awfixers-stuff
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: canton-network-repos
Source: https://github.com/awfixers-stuff/opencode-config/tree/main/skills/canton-network-repos
Command: npx skills add https://github.com/awfixers-stuff/opencode-config --skill canton-network-repos-awfixers-stuff

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Canton Network version management is complex: mismatches between Splice, Canton, and DAML SDK can block deployments and upgrades. This guide clarifies version mappings, supported LF targets, and upgrade considerations to keep dependencies aligned.

Core Features & Use Cases

  • Provides a concise overview of the Canton Network version matrix (Splice, Canton, DAML SDK, LF targets) and how to interpret package IDs.
  • Documents upgrade workflows, compatibility rules, and common troubleshooting steps for LF 2.2 migrations.
  • Serves as a quick reference for configuring repositories, verifying version consistency, and preventing cross-version conflicts in development and production environments.

Quick Start

Review the Version Mapping table, confirm your project's Splice/Canton/DAML SDK targets, and plan an upgrade path aligned with LF 2.2 compatibility.

Frequently Asked Questions about canton-network-repos

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

FAQPage Schema
How do I align Canton Network components to compatible version mappings?

Align Canton Network components by cross-referencing Splice, Canton, and DAML SDK targets against the version matrix to prevent LF version drift. This verifies dependency consistency and specifies necessary version configuration notes for successful deployments.

What is the correct DAML SDK and Splice version configuration for LF 2.2 migrations?

LF 2.2 migrations require matching your DAML SDK and Splice versions to compatible Canton targets using the version matrix. This prevents cross-version conflicts by verifying package IDs and confirming supported LF targets before upgrading.

How do I troubleshoot version mismatches between Canton and DAML SDK?

Troubleshoot Canton and DAML SDK mismatches by reviewing dependency verification checks and compatibility rules. Common issues stem from LF version drift, which you can resolve by validating package IDs and aligning targets across the Canton Network version matrix.

Does this Canton Network version guide work for both development and production environments?

Yes, the version mapping guide applies to both development and production environments. It serves as a quick reference for configuring repositories and verifying version consistency to prevent cross-version conflicts across Splice, Canton, and DAML SDK.

What are the limitations or common issues when planning Splice upgrade workflows?

Splice upgrade workflows are limited by LF version drift and cross-version conflicts between Canton and DAML SDK. Prevent these issues by following documented compatibility rules, validating package IDs, and performing necessary upgrade steps and validation checks.