canton-network-repos
Navigate Canton Network Repository Versions
Canton, DAML, and Splice version mismatches can break builds and package upgrades. This skill gives version maps, file locations, and troubleshooting steps.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "canton-network-repos" from https://skillstore.io/skills/0xbigboss-canton-network-repos.md and its manifest at https://skillstore.io/api/skills/0xbigboss-canton-network-repos/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "canton-network-repos". Why does my community DAR package ID differ from enterprise?
Expected outcome:
The skill explains that LF target, SDK version, source content, and dependency packages affect the package ID. It recommends checking build inputs before replacing packages.
Using "canton-network-repos". Where do I change the Splice LF target?
Expected outcome:
It points to the Splice dependency configuration and package target files. It also notes that DAML SDK version alignment is required.
Using "canton-network-repos". How do I troubleshoot an unknown LF version error?
Expected outcome:
It directs the user to verify compiler target support and upgrade the SDK when the compiler does not know the requested LF version.
Security Audit
SafeAll static findings were adjudicated as false positives. The alerts are Markdown examples, reference links, paths, or a non-secret version variable. No prompt injection, credential exfiltration, or malicious intent was found in SKILL.md.
Risk Factors
⚙️ External commands (23)
🌐 Network access (4)
📁 Filesystem access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/0xbigboss-canton-network-repos/audits/9?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/0xbigboss-canton-network-repos?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/0xbigboss-canton-network-repos?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/0xbigboss-canton-network-repos/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/0xbigboss-canton-network-repos.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
0xBigBoss. (2026). canton-network-repos security audit report (audit version 9) [Author version unspecified]. Skillstore. https://skillstore.io/skills/0xbigboss-canton-network-repos/audits/9BibTeX citation
@techreport{0xbigboss-0xbigboss-canton-network-repos-2026,
author = {0xBigBoss},
title = {canton-network-repos security audit report (audit version 9)},
institution = {Skillstore},
year = {2026},
number = {9},
url = {https://skillstore.io/skills/0xbigboss-canton-network-repos/audits/9},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "canton-network-repos security audit report (audit version 9)"
version: "unspecified"
type: report
authors:
- name: "0xBigBoss"
date-released: "2026-07-06"
url: "https://skillstore.io/skills/0xbigboss-canton-network-repos/audits/9"
identifiers:
- type: other
value: "skillstore:0xbigboss-canton-network-repos:audit:9"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
Plan LF Upgrades
Compare target LF versions and update the key Splice and DAML configuration files.
Debug Package Mismatches
Trace package ID changes to SDK versions, LF targets, source content, and dependency packages.
Review Repository Dependencies
Understand how Splice depends on Canton and how Canton depends on the DAML SDK.
Try These Prompts
Use the Canton Network repository reference to explain how my Splice version maps to Canton, DAML SDK, protocol, and LF versions.
List the files I should inspect before changing a Splice LF target. Explain the purpose of each file.
Help me diagnose why two DAR builds produce different package IDs. Focus on LF target, SDK version, source content, and dependencies.
Create an upgrade checklist for moving a Splice community build to LF 2.2 with SDK 3.4.9. Include validation risks.
Best Practices
- Verify local repository versions before applying the reference table.
- Keep LF target, DAML SDK version, and dependency package versions aligned across all builds.
- Treat package ID differences as compatibility changes until build inputs prove otherwise.
Avoid
- Do not mix enterprise LF 2.2 packages with community LF 2.1 replacements without a compatibility plan.
- Do not assume identical source produces identical package IDs when SDK or dependency packages differ.
- Do not remove build warnings or change targets without checking SDK support.