(related to #11627)
Because we need to keep track of pending partial notes, it'd be very nice if we could guarantee that these are only going to get a single completion log. Otherwise we need to keep track of them forever and continuosly search for new logs, or to somehow identify the correct completion (which seems quite hard given we typically don't know how a partial note will be completed). #14363 would provide some of the tools required to achieve this - the second part would be the (only) sender having logic that prevents ever doing multiple completion. This means that partial notes would typically be completed by non-account contracts.
Interestingly, if the combination of #14363 and proper contract logic prevent multi-completion, then we don't need to emit a note completion nullifier (saving DA), since a double-spend would be impossible.
(related to #11627)
Because we need to keep track of pending partial notes, it'd be very nice if we could guarantee that these are only going to get a single completion log. Otherwise we need to keep track of them forever and continuosly search for new logs, or to somehow identify the correct completion (which seems quite hard given we typically don't know how a partial note will be completed). #14363 would provide some of the tools required to achieve this - the second part would be the (only) sender having logic that prevents ever doing multiple completion. This means that partial notes would typically be completed by non-account contracts.
Interestingly, if the combination of #14363 and proper contract logic prevent multi-completion, then we don't need to emit a note completion nullifier (saving DA), since a double-spend would be impossible.