Canton’s sub-transaction privacy gives each party only its own slice of a transaction, made of three permissions, stakeh | Hanami
Canton’s sub-transaction privacy gives each party only its own slice of a transaction, made of three permissions, stakeholder visibility, divulgence, and disclosure.
@Hackenclub has put together examples showing how keeping them distinct decides which party can act on what. https://x.com/hackenclub/status/2113222369888043358
Quoted @hackenclub: On @CantonNetwork, "who can see this contract?" sounds simple. It is actually three questions: who was told about it, who saw it and who is permitted to use it.
Get the distinction wrong and your KYC provider could see the loan rate.
Hacken's new research works through a loan example:
• A KYC provider added as an observer on the loan sees every field, including the amount, rate and lender.
• If the identity moves to a separate contract but is fetched inside the loan's Accept choice, every witness of Accept sees it.
• A better approach is to fetch only a pass/fail attestation rather than the full identity record.
To remove an observer, the contract must be archived and recreated, because Daml contracts are immutable.
The Ledger API is not the boundary. Divulged copies remain in participant storage until pruning, and the receiving party's validator operator can read them.
None of this shows up as a failing test.
Full analysis, with a five-point Daml privacy audit checklist: https://hackenio.cc/auditing-daml-privacy-on-canton-network(Historical earnings: For fiscal 2026 full year (period ended 2026-09-03), Micron reported basic EPS of 75.38, diluted EPS of 74.33, net income of USD 84.969 billion, and revenue of USD 133.188 billion.
Consensus expectations: For the next upcoming period (2027Q1, event date 2026-12-15), consensus expects EPS of 37.93 and revenue of USD 63.793 billion.)