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
The vtxo contains info about when it expires but not about when it was created.
ATM can determine the creation timestamp for a vtxo with vtxo.ExpiresAt - asp.RoundLifetime but with the assumption that the ASP never changes the round lifetime. Impossible to calculate the timestamp for a pending vtxo instead.
The text was updated successfully, but these errors were encountered:
I would concur that also having a way to carry the data related to the shared output could be useful. You could infer the "genesis" from the block time, but having both is useful
atm the vtxo struct includes a field for the round txid. Don't you think this is enough? storing the same data for many vtxos doesn't seem to me a good idea
The vtxo contains info about when it expires but not about when it was created.
ATM can determine the creation timestamp for a vtxo with
vtxo.ExpiresAt - asp.RoundLifetime
but with the assumption that the ASP never changes the round lifetime. Impossible to calculate the timestamp for a pending vtxo instead.The text was updated successfully, but these errors were encountered: