Closed bmcd closed 4 years ago
I don't want to be able to add more public keys to an already deployed contract, since that may make users think that doing so will extend the actual private contract to those recipients.
But it could be more clear that the privateFor field above applies to both Deploy and At. Not sure the best solution to this:
I cannot see the privateFor keys dropdown when I tested it.
If that display can function well, I should feel comfortable with the current implementation. When a wrong group of Tessera public keys is selected, we can simply close it and reselect and use At to instantiate again.