Questions on spec

[waalge]

1. I was confused by time_to_live. I guess this is expiration?

2. There are the following constraints specified:

• Spending single LatestPriceDatum UTXO
• Spending single AuxiliaryDatum UTXO

What is the significance of these? I cant think of any safety issues that require these constraints.
I can see an implementation problem: we wont be able to identify these instances from script hashes (easily) .

[codybutz]

I was confused by time_to_live. I guess this is expiration?

Yes, when the latest price is updated, expiration = newest created at + time to live. Agreed that is not well defined in the specification.

I can see an implementation problem: we wont be able to identify these instances from script hashes (easily) .

They will both have the same script hash I do believe. We could identify by inputs with the same payment credential, identifying by Datum. Ex: if input_datum is LatestPriceDatum and if input_datum is AuxiliaryDatum

[waalge]

Per instance, there are two utxo each with a token that necessarily share a hash.
However, the wording ("single") suggest that no other instances appear.
This cannot be known (simply)

Slowly working through the doc. Will have more Qs as they come.

I think the last_created_at is redundant in the one-FS case(s), since it can be inferred from expiration - ttl.
For the two-FS case(s), it can be a single number.
There are a few things like this I will consolidate into a document

[waalge]

Do we need staked addresses? Its either if we dont. Or at least, that the address is fixed for the instance

[codybutz]

I don't suspect a lot of value in the contract UTxOs, so probably best to not bother with staking.