Currently, the VoucherExecuted event from the ICartesiDApp interface has one argument, voucherId, which uniquely identifies the voucher that was executed.
This number, however, isn't really helpful for off-chain components to tell which voucher was actually executed.
✔️ Solution
Vouchers can be identified with two numbers: input index and output index (within input).
We can refactor the VoucherExecuted event to encode the two numbers mentioned as arguments.
📚 Context
Currently, the
VoucherExecutedevent from theICartesiDAppinterface has one argument,voucherId, which uniquely identifies the voucher that was executed. This number, however, isn't really helpful for off-chain components to tell which voucher was actually executed.✔️ Solution
Vouchers can be identified with two numbers: input index and output index (within input). We can refactor the
VoucherExecutedevent to encode the two numbers mentioned as arguments.