Most people still define self-custody on Canton as who holds the keys.
They're stopping one layer too early.
On Canton, every party is hosted on a participant node.
If that hosting sits on a single validator, the user still carries a single point of failure and a single point of trust, even when they fully control their keys.
That’s the gap @canton_loop is trying to solve.
👇
