Recovering a Canton participant and its party identity — looking for operator feedback

Hi all — I’m building Tessera for HackCanton S3: operational continuity for Canton participants.

The idea: a participant’s ACS is encrypted and replicated to custodian participants, and both the backup key and the party’s signing key (an external party) are Shamir-split 2-of-3 among them. If the participant dies, the party is re-hosted on a different participant, its state is imported, and counterparties’ ACS commitments verify the result. In my tests on Canton 3.5.18 that takes about a minute, with no manual repair steps.

Repo: github.com/SpaceUY/canton-dr-hackathon

I’d really value input from people who run participants:

• How do you handle participant recovery today?
• Would you trust other participants as custodians of encrypted backups and key shares?

@dr.rabi @Lucas_Allirol @Jatin_Pandya_cf — I saw your posts on node operations and would love your take.