Justin Atwell

Darn Simple Daml #4: Never cache a contractId across a workflow! Consuming choices don’t update a contract. They archive it and mint a brand new one with a brand new contractId. That contractId you captured before the exercise is gone forever. Found this out the hard way building MarginCalls. Methods were re-fetching by the old contractId after the exercise. Every one threw “contract not found” on success. Fix is simple: capture your stable business key before the exercise. Re-fetch by that after. Never the contractId. The contractId is a pointer into an immutable snapshot. Consuming choices invalidate the snapshot. Your code holding the old reference just doesn’t know it yet. $CC #Daml #Canton #BuildOnCanton

Zenith has been selected to join @progmat_en's Tokenized JGB / On-Chain Repo Working Group, a consortium backed by Japan's largest financial institutions including MUFG Bank, Mizuho Bank, SMBC, BlackRock Japan, State Street, SBI Securities, and Japan Exchange Group. The group is targeting the tokenization of Japan's ¥250–270 trillion ($1.6 trillion) JGB repo market, which represents approximately 10% of the global government bond-backed repo market. Zenith, as the EVM execution layer of Canton Network, will contribute to protocol design, interoperability standards, and regulatory-compliant infrastructure for the on-chain repo system using tokenized JGB collateral paired with stablecoin cash legs. The Working Group kicked off in May 2026. A comprehensive report is expected in October 2026, with tokenized JGB issuance pilots targeted for later this year. This announcement follows Japan's tokenized securities market already surpassing JPY 333–360 billion in cumulative issuance, with the Progmat-led effort now targeting institutional-scale JGB tokenization. Zth.

STACKED IFW 👊 Prelims - 5pmET Main Card - 9pmET [ #UFC329 LIVE on @ParamountPlus | B2YB: @ForthePeople ]

Darn Simple Daml #3: The codegen import you’re going to get right because you read this tweet. 😭 First time generating Java bindings from your Daml model, you’ll hit an import like: com.canton.etf.model.canton.etf.{module}.{templatename} It repeats your package path. Looks like a copy-paste bug but It’s not. Daml codegen mirrors your module hierarchy inside a generated package root, so your own canton.etf.X namespacing gets nested under the tools own model package. The duplication is intentional, and it’ll trip up literally every team the first time they see it. Once you know the pattern, it’s not confusing. it’s just new y’all. Here’s an example! github.com/justin-atwell/… #Daml #Canton #BuildOnCanton