Documentation

HackCanton Season 4, registration form answers Run by NODERS LLC. Note it says Season 4, not 3. My earlier figures (up to $50,000, Grand Final 14 October) were Season 3's. Read S4's own prize pool and dates off the form or the announcement. Do not assume they carried over. --- Page

Pending update to the Canton Developer Hub listing Hold until PR #160 is reviewed. That one fixes link rendering for nineteen entries including ours. Filing a third pull request at the same organisation, before the second

How the integration milestone gets done The Dev Fund milestone is two Canton applications the applicant does not own. The package that makes a yes cheap exists. Nobody has been asked. This is the plan for asking: who, when, what, and what makes us stop. Who: Moonsong Labs, and it is not clo

LinkedIn: the Federico fact Status: not posted. The one rule for this post Post what happened. Never what it implies. True, and verifiable by anyone who opens the thread: a Canton Community Tech Partner reviewed the design, found the flaw, and the fix shipped the next day with his name

New forum topic: what a ledger does not record Where: https://forum.canton.network/new-topic Category: App Development. That is where 9114 went, and it is the one that got a substantive reply from a Canton engineer. Tags: daml, canton Status: not posted. The judgment call, s

PR #860: what the email meant, and the one move that follows The email SIG labels auto-detected and applied: regulatory-compliance A robot read the proposal, decided which Special Interest Group it belongs to, and tagged it. That is all it was. It is not approval, not rejection, and not a per

Everything to send, 22 October 2026 Seven messages. Written to be pasted, not edited. Order matters: Arpit first, because his moment closes. One rule across all of them. Nothing here describes work in progress. Every claim is a thing that is built, tested and pushed, per the guardrail in CLAUD

SENT, 13 September 2026 Both went out. Mr_Tuddles at 12:03, t/9059/13. Federico at 12:06, t/9114/4. Nothing here needs doing. Kept as the record of what was said and why, and as the shape for the next one: short

Inside the Canton Network, Episode 11 WEDNESDAY 16 September 2026, 16:00 UK. The listing says "Tuesday". It is wrong. 16 September 2026 is a Wednesday. Register: https://luma.com/xl5u0yt9 (two minutes, still not done) Host: Launchnodes. Guest: Aki Balogh, CEO of BitSafe. What th

Prior art, and who got there first *Compiled 8 October 2026. This file exists because the alternative is being corrected in public by someone who did this search before we did.* Everything here is marked VERIFIED (checked directly from a primary source while writing this file) or REPORTED

Privacy matrix Who signs each contract, who observes it, and who is excluded. The exclusions are the design: on Canton a non-observer receives nothing — not an encrypted payload, not a hash, zero bytes — so a party absent from a row cannot see that the contract exists. *Generated from the Daml

RFP 27: what overlaps, what does not, and what no CIP covers Declared interest, first, because it changes how you should read this. I am the author of #860, one of the three proposals assessed below. I have tried to describe the other two as their authors would recognise them, and where I coul

SIG approach — how these proposals reach a Champion The Development Fund's own process says what to do before submitting, in order: > 3. Discuss the need with the relevant SIG, maintainers, developers, or affected > ecosystem participants. > 4. Gather evidence that the problem is real and sufficie

Three straight answers Written to be acted on, not agreed with. --- 1. Can Federico champion me? No. And I told you the wrong thing last time. I said "technically yes now, since there is no approved list any more." I had read the workflow and not the rule. The rule is CIP-0100, and it i

Threat model What this system defends against, what it does not, and what an attacker gets if each part fails. Written to be argued with. The asset: a float held in one country, spent by an operator in another, under a mandate issued by a principal who cannot be present. **The trust boundary:*

Upgrading the mandate package Canton checks that a new version of a package is a valid upgrade of the one already vetted. This document exists because we failed that check, and the reason was not the one we expected. What happened We added per-period limits to KyaMandate — two Optional fiel

Where do the addresses come from? Every address in this repository is a placeholder. They are well-formed examples with no keys behind them. Nothing here custodies anything, and the system cannot receive a real deposit until that changes. This is the gap between "the rules are tested" and "the

What an automated execution was stopped from doing *A note on auditability for deterministic settlement. September 2026.* The industry says that putting automated execution on a blockchain makes it auditable. Every decision recorded on an immutable ledger, recallable later.[^1] Half of that is tru

What a KYA chain proves, and what it does not The value of this format is not that it produces a record. Anything produces a record. It is that a reader can work out how much of it to believe without trusting whoever handed it to them. That only works if the limits are written down as plainly

knowyouragenticai-receipts Let an automated execution pay, and prove what it couldn't. A tamper-evident record of every payment attempt — including the refusals — for automated Canton applications. Built for Canton Network; works anywhere. Zero dependencies. --- If you let software spend money

KYA Rails Know Your AgenticAI is the evidence layer that sits under a Canton application. An application decides what an autom

Thirteen Checks scoreboard, run before demo 1 Written rules: PASS (THE-RULES.md, read by agent at boot) 2 Plan before code: PASS (job cards committed before code) 3 Small pieces: PASS (three stages) 4 Route not reflex: PASS (agent prints its plan before acting) 5 Done defined: PASS (each job card

Shortcut log. A written shortcut is a debt paid on our schedule. | date | shortcut | why | repay by | |---|---|---|---| | 2026-08-29 | MockLedger mirrors Daml assertions in Python for offline demo | venue network unknown | venue: swap to c8lab DevNet calls | | 2026-08-29 | Charge records value, do

KYA Receipt Chain, version 1.3 A wire format for tamper-evident receipts of agent actions, including the actions that were refused. Status: stable. Reference implementations: kya_chain.py (Python, stdlib only) and verifier.html (b

Status: what is proven, what is mocked, what is pending *Last measured 2026-10-31. Regenerate the numbers with python3 tools/dashboard.py, and the champion figures with python3 tools/champions.py.* This file exists because the team that won the Cantor8 hackathon had one and this repository did

canton-refusal-record A refusal that survives, for any Canton application. One Daml module. No dependencies but daml-prim and daml-stdlib. MIT. The problem In Daml a failed assertMsg aborts the whole transaction. Nothing is written. After a refused action the ledger looks exactly as i

KYA RAILS. THE RULES. Build for Cantor8 "Build on Canton" Hackathon, challenge D1: a spend-limited wallet for Canton Automated Execution. Built with the KYA Method: Promise it. Attack it. Inspect it. Prove it. The promise An automated execution may spend money ONLY under a written mandate: a ca

check/fixtures These are the answers a real, running participant gave. They are not invented examples. One thing in them was edited and it is named below: the package list, from which the standard libraries were removed along with their bytes. CI has no Canton node. So run-check.test.ts stan

Slots nothing judged Generated — apps/backend/src/check/coverage.test.ts writes it and requires it to match. Every slot of every schema a mapped answer can reach has a rule (that is coverage()'s business). This is the other half: whether anything ever *ran* that rule. A rule under a union

Deployment Explorer ships an independently runnable React Frontend and JSON Backend API. Select the authentication profile explicitly; missing, invalid, or mismatched modes fail at build or startup. There is no automatic fallback. Authentication profiles | Frontend VITE_AUTH_MODE | Backend L