LEARN · DOCUMENTATION
Documentation
Pages from 29 sources, kept in sync: the official Canton Network and Digital Asset docs, documentation from teams building on Canton, and readmes from their code. Search all of it, or start from a path below.
3,253pages
synced 4h ago29 sources
1 more source4 pages
Code
dominicrume/cantor8_kya_rails: docs/drafts/reply-karnatak-9084.md
Post-To: https://forum.canton.network/t/9084 (Reply) Arpit, you wrote that there was no standard pattern out there for committing refused actions on-chain, and that this was why #627 keeps those logs off ledger. That sentence is now quoted in a CIP draft on cip-discuss, because it is better evidence
Code
dominicrume/cantor8_kya_rails: docs/drafts/reply-leonid-9114.md
Post-To: https://forum.canton.network/t/9114 (Reply, and tick PREDGE's post 6 as the solution while you are there) The use case, and your first three paragraphs move where it sits. An agent holds a spending mandate. Its principal has to answer one question to an auditor: did it ever try to exceed it
Code
dominicrume/cantor8_kya_rails: docs/drafts/reply-meier-cip-discuss.md
Post-To: https://lists.sync.global/g/cip-discuss/message/910 (log in, press Reply, keep the subject) Simon, you are right on both counts about the mechanism, and I had built only the expensive one. RefuseSignalled is in now. No contract, and the arguments reach the exercise's informees, the auditor
Code
dominicrume/cantor8_kya_rails: docs/drafts/reply-radev-9323-b.md
Post-To: https://forum.canton.network/t/9323 (Reply at the bottom) That last line is the one I needed, and it splits the claim in two. Who is named is on the ledger. The guardian and the auditor are signatories of the journal, so a reader of the contract sees which parties they are with no Admin API
Code
dominicrume/cantor8_kya_rails: docs/drafts/reply-radev-9323.md
Post-To: https://forum.canton.network/t/9323 (Reply at the bottom) You were right on both counts, and I went and tested the rest of your list. Implicit Archive is gated by the signatory line, so the owner alone fails. The bypass is submitting as both, which succeeds with the counter at zero: testSub
Code
dominicrume/cantor8_kya_rails: docs/drafts/review-dpm-334.md
Review-On: https://github.com/digital-asset/dpm/pull/334 How: Files changed tab > Review changes > "Comment" > Submit review. NOT the comment box at the bottom of the Conversation tab. Only the Files-changed route makes GitHub count you in reviewed-by:dominicrume. Approve. os.Kill is SIGKILL and c
Code
dominicrume/cantor8_kya_rails: docs/drafts/sig-membership-route.md
The documented route from here to a Champion Everything below was read on 4 November 2026 from github.com/canton-foundation/canton-dev-fund and is cited by file and line. The gate we had wrong sig-directory.md line 39: "Under CIP-0100, an external Development Fund proposal requires a Champion
Code
dominicrume/cantor8_kya_rails: docs/evidence/archive/forum-9059.md
forum.canton.network/t/9059 [Feedback welcome] OpenZeppelin’s Daml development stack is public and open for review Archived 2026-09-13T23:49:00Z from https://forum.canton.network/t/9059.json, the public Discourse endpoint. The untouched response is beside this file as forum-9059.json; this
Code
dominicrume/cantor8_kya_rails: docs/evidence/archive/forum-9114.md
forum.canton.network/t/9114 How do you prove your app didn't do something? Archived 2026-09-13T23:49:00Z from https://forum.canton.network/t/9114.json, the public Discourse endpoint. The untouched response is beside this file as forum-9114.json; this is a rendering of it. 4 posts, 57 views
Code
dominicrume/cantor8_kya_rails: docs/evidence/index.md
Evidence index Every public artefact, with the date it appeared and where to verify it. Generated by tools/evidence_pack.py on 2026-09-24 20:34 UTC from the GitHub, PyPI and Canton forum APIs. Regenerate before submitting anything: numbers move, and a stale figure is the one an assessor chec
Code
dominicrume/cantor8_kya_rails: docs/examples/README.md
An example disclosure settlement-refusals.json is a real run of the real library, with invented figures. No money moved, no ledger saw it, and none of these merchants exist. It is here so you can check the format before you produce one of your own. What it is A settlement agent ran seven step
Code
dominicrume/cantor8_kya_rails: docs/findings-openzeppelin.md
Mutation testing three OpenZeppelin Canton repositories Run on 2026-09-07 with tools/daml_mutate.py, answering the standing invitation in OpenZeppelin's [forum thread](https://forum.canton.network/t/feedback-welcome-openzeppelin-s-daml-development-stack-is-public-and-o
Code
dominicrume/cantor8_kya_rails: docs/findings/the-scanner-read-the-file-every-run.md
My scanner read the file every run and missed the breach *24 October 2026. Every claim here is one command. The commands are at the bottom.* **Published at <https://dominicrume.github.io/cantor8_kya_rails/writing/defeated-by-punctuation.html>.** That is a plain URL on the public web, served by Git
Code
dominicrume/cantor8_kya_rails: docs/measured-against-the-winners.md
Measured against the people who beat us *Measured 17 October 2026 from their repositories, not from memory or from what they said on the day. Re-measure before quoting any of it.* Cantor8 "Build on Canton", London, 29 August 2026. This project placed 3rd as Vorem. 1st was Team Mandate, 2nd
Code
dominicrume/cantor8_kya_rails: docs/moving-to-a-vorem-org.md
Moving this repository to a Vorem GitHub organisation *Written 17 October 2026. Every claim marked VERIFIED was read off GitHub's own docs or measured in this tree today. Everything else is marked as a judgement.* Short answer: do it, but not this week, and not before the dinner. There is exac
Code
dominicrume/cantor8_kya_rails: docs/opportunities.md
Every opportunity, and what each is actually waiting on *Checked 26 September 2026. Numbers from the GitHub, PyPI and CoinGecko APIs, not from memory. Re-measured 26 October 2026: CC at $0.0990.* Income to date Zero. Not "early". Not "pre-revenue". Nothing has ever been invoiced or received
Code
dominicrume/cantor8_kya_rails: docs/outreach/ask-back.md
Asking back Eleven unpaid contributions to two other teams. Nothing asked in return, ever. That was right at the time, and it is a portfolio now rather than charity. Three asks, smallest first. Send them in this order. --- 1. Cantor8, on toolkit PR #10 Costs them: thirty seconds. **Gets you
Code
dominicrume/cantor8_kya_rails: docs/outreach/ask-cantor8-for-devnet.md
Ask Cantor8 for a DevNet secret Status: not sent. This is not a cold ask, and the draft treated it as one There are four open pull requests against Cantor8/hackathon-toolkit, filed on 31 August, with no comment on any of them since: | | | |---|---| | [#7](https://github.com/Cantor8/ha
Code
dominicrume/cantor8_kya_rails: docs/outreach/contracts-and-the-clock.md
Paid work, and the twelve-month clock Two goals that turn out to point at the same people. Income. Daml and Canton contract work, now. Global Talent. Three letters are required, each from somebody who has known the work for at least twelve months. Every Canton relationship is too young
Code
dominicrume/cantor8_kya_rails: docs/outreach/do-this-next.md
Do this next Seven steps, in order. Each one says where to go, what to click, and what to paste. Nothing here needs any more writing. Tick a step off by putting an x in the box. --- [ ] 1. Register for the webinar (2 minutes, do today) Go to: https://luma.com/xl5u0yt9 Click Register.
Code
dominicrume/cantor8_kya_rails: docs/outreach/five-firms.md
Five firms, one question, one afternoon The question, and it is the same every time: > Do you ever subcontract Daml work when a client lands? It is not a favour and not a job application. A firm with more work than people says yes. One without says no. Neither costs you anything, which is why
Code
dominicrume/cantor8_kya_rails: docs/outreach/float-on-cip-discuss.md
Float it on cip-discuss before writing the CIP Where: https://lists.sync.global/g/cip-discuss/topics (join is open to anyone) Status: not sent. Why this and not a finished CIP cip-0000 says it plainly: talk to the community early, because floating an idea before writing a full CIP sav
Code
dominicrume/cantor8_kya_rails: docs/outreach/forum-new-thread-switched-off.md
New thread: a control the audited party can switch off Where: forum.canton.network, App Development. Tags daml, canton. Why a thread and not a reply: the only topic this account has started is 9114, on 8 September. Six weeks of replying to other people. Replies make you useful. Thr
Code
dominicrume/cantor8_kya_rails: docs/outreach/forum-post-openzeppelin.md
Forum post: reply in OpenZeppelin's feedback thread Where: https://forum.canton.network/t/feedback-welcome-openzeppelin-s-daml-development-stack-is-public-and-open-for-review/9059 As: a reply in that thread, not a new topic. It carries the invitation this answers, and it already has an aud
Code
dominicrume/cantor8_kya_rails: docs/outreach/forum-post-own-topic.md
Forum post: our own topic Where: https://forum.canton.network/ — App Development category, tags discuss and feedback. A NEW topic, not a reply. When: a day or two after the OpenZeppelin reply (post #8, 2026-09-08). Two posts in one afternoon reads as promotion. **Links verified 2026-09
Code
dominicrume/cantor8_kya_rails: docs/outreach/forum-reply-federico.md
Reply to Federico, forum 9114 Thread: https://forum.canton.network/t/how-do-you-prove-your-app-didnt-do-something/9114 Our own thread. Last post ours, 13 Sept. 112 views. He asked for nothing. So this is a short update, not an essay. He gave the review for free and the only right response
Code
dominicrume/cantor8_kya_rails: docs/outreach/forum-reply-scheduled-actions.md
Reply to Archana Nigam, forum 9314 Thread: https://forum.canton.network/t/implementing-scheduled-and-recurring-actions-in-daml-3-5 Posted: 17 October 2026, 09:41, by nigam_archana. App Development. Zero replies. Her use cases are EOD trade close, monthly interest payments, and maturi
Code
dominicrume/cantor8_kya_rails: docs/outreach/forum-reply-vacuumlabs.md
Reply to Vacuumlabs, forum 9084 Thread: https://forum.canton.network/t/9084 Posted: 27 Aug 2026 by arpitkarnatak_vl. 58 views, no replies. Their PR: canton-dev-fund #627. Open, needs-champion. Three drafts were binned. The reason was the same every time: length. 1. 600 words. To
Code
dominicrume/cantor8_kya_rails: docs/outreach/get-a-champion.md
Getting a champion: the blueprint *Written 17 October 2026, the night before the Cantor8 winners' dinner.* Why this is the only thing that matters on the proposal The Dev Fund review process says a proposal moves to "In Review" once it has been assigned to a champion. No champion, no review
Code
dominicrume/cantor8_kya_rails: docs/outreach/hackcanton-s3-entry.md
HackCanton Season 3, solo entry Register: https://appsfactory.cc/hackathons Grand Final: 14 October 2026. Prize pool: up to $50,000. Solo entries allowed. Season 2 paid $10K cash + $25.2K NaaS credits + 100K CC. Check the submission deadline the moment you land on the page. Tha
Showing 211 to 240 of 738Search all sources →