You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently the txo only includes a spent_at to verify if the utxo was spent or not.
I think it would be beneficial to also store the spent_tx BLOB to help identify the tx where the utxo was spent.
A use-case:
imagine a marketplace dapp. The dapp on the backend would have a matcher on the script address. Kupo would have all sell orders and their history and able to track the "active" sell orders. On the UI you don't really care about the buy transaction, only that the item was sold, but you would still want to provide a link to an explorer, where the transaction happened.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently the txo only includes a
spent_at
to verify if the utxo was spent or not.I think it would be beneficial to also store the
spent_tx BLOB
to help identify the tx where the utxo was spent.A use-case:
imagine a marketplace dapp. The dapp on the backend would have a matcher on the script address. Kupo would have all sell orders and their history and able to track the "active" sell orders. On the UI you don't really care about the buy transaction, only that the item was sold, but you would still want to provide a link to an explorer, where the transaction happened.
Beta Was this translation helpful? Give feedback.
All reactions