It can be challenging to implement in circuits because reading varying numbers of resources is problematic. We need to set a high upper bound for the denomination logic, and each logic must read these resources, including dummies. The simplest approach is to use one ephemeral resource to burn another persistent resource. The logic always expects at most three, including self denomination resource, self kudo resource and the target kudo resource to burn. This method allows burning multiple resources from different owners by composing multiple tuples in a single action. Does it make sense?
Agree! Ephemeral resources generally lack ownership, especially when balancing against persistent resources. Ownership is typically defined and embedded in the value field, but the value is not that useful for ephemeral resources since it’s neither checked nor secure. Additionally, the concept of ownership for unconsumable ephemeral resources feels unnecessary.
Instead, for intent-carrying ephemeral resources, ownership can be embedded in the label. These resources can be created and consumed, probably making them meaningful in practice.