Continuing the discussion from Impact of package unvetting by observers on usability of existing contracts:
Hi, I found this while looking at Canton Coin allocations.
From my understanding, committed allocations on Token Standard V2 are not safe against the case described here: “if you turn off a signatory participant that then just refuses to participate in the transaction confirmation process”. The owner can’t withdraw a committed allocation, but settlement still archives or creates contracts the owner signs (the allocation, the `LockedAmulet` and the payout `Amulet`), so the owner’s node can block settlement just by staying silent until the deadline.
Could a model where the owner is only an observer of these contracts, since the DSO is already trusted for the custody of the asset, fix it, or would it conflict with something else ?
There is also this problem: “If a participant forcefully unvets a package, the contract is blocked. Same happens if a participant removes a party.”
From my understanding, the protocol checks, at the moment a transaction is submitted, if the participant node of the observer party has vetted that package. I’m assuming the main reason for this check is that an observer’s node needs the package to process the transaction, and, besides being a security measure, vetting informs other nodes that this node has this package. Otherwise, the observer party can’t correctly perform the “role” of observer, maybe there is another reason I’m not aware of.
The protocol gets this guarantee but allows the observers to block transactions that do not require their confirmation.
I suspect we could get the same guarantee if instead of requiring the participant nodes of the observers to have vetted the package at the time the transaction is submitted, require only that they vetted it when the contract was created, and not require the observer to still be hosted somewhere. This protects against an observer that later unvets the package or removes its party to block transactions that don’t need its confirmation. Since it vetted it when the contract was created, the participant node has shown that it can process the transaction. Contracts created by a choice that archives a contract the observer already sees, with the same package (like the payout created when the allocation is settled), would be treated the same way. Unvetting would still stop the observer from being added to new contracts.
Could something like this work ?