assetId.
This update is represented by the following tuple,(price, time, name)
, where price
represents the new price, time
is the timestamp of the update and name
is a unique identifier of the assetId
and oracle identity. For more details on how to generate price feeds, read here.system_time
assetId
for which the price is updated. assetId
in the list, it sends a list of (price, time, name, sig)
as well as current_price
that will be de-facto used by StarkEx for the next transactions. assetId
, the entire quorum of signatures that attests to the minimal and maximal prices in a batch. For the rest of the prices, StarkEx only proves that they are between the minimal and maximal price.config[assetId].keys
, on the tuple config[assetId].names
price_validity_period
-hours window. Furthermore, batch_starting_time - price_validity_period
and batch_end_time
.assetId
(including assets that didn't receive an update in this batch), StarkEx verifies the minimal_price
and maximal_price
. This is done by verifying the following conditions for the Oracle Price Tick that attests to each of them. Bear in mind that an Oracle Price Tick contains a list of config[assetId].keys
, on the tuple config[assetId].names
batch_starting_time
and batch_end_time
.system_time >= prev system_time
assetId:
current_price
is bigger than or equals the minimal_price
of this batchcurrent_price
is smaller than or equals the maximal_price
of this batch