@@ -114,16 +114,16 @@ Feature: Confirm return to continuous trading during significant mark price chan
114
114
| ETH /FEB23 | my -price -monitoring -2 | weight | 0 ,0 ,1 ,0 | 0s ,0s ,0h0m120s ,0s |
115
115
# first we get bounds based on default factors, once the state variable engine finishes its calculation we get the proper values
116
116
Then the market data for the market "ETH/FEB23" should be:
117
- | mark price | trading mode | auction trigger | horizon | ref price | min bound | max bound |
118
- | 1000 | TRADING_MODE_MONITORING_AUCTION | AUCTION_TRIGGER_PRICE | 30 | 1000 | 900 | 1100 |
117
+ | mark price | trading mode | auction trigger |
118
+ | 1000 | TRADING_MODE_MONITORING_AUCTION | AUCTION_TRIGGER_PRICE |
119
119
120
120
# the last second of the original extensions
121
121
And the network moves ahead "3" blocks
122
122
Then the market data for the market "ETH/FEB23" should be:
123
- | mark price | trading mode | auction trigger | horizon | ref price | min bound | max bound |
124
- | 1000 | TRADING_MODE_MONITORING_AUCTION | AUCTION_TRIGGER_PRICE | 30 | 1000 | 997 | 1003 |
123
+ | mark price | trading mode | auction trigger |
124
+ | 1000 | TRADING_MODE_MONITORING_AUCTION | AUCTION_TRIGGER_PRICE |
125
125
126
- # the updated extension triggered, no triggers left
126
+ # the updated extension triggered, no triggers left as they've all been switched off since update took place during auction
127
127
And the network moves ahead "1" blocks
128
128
Then the market data for the market "ETH/FEB23" should be:
129
129
| mark price | trading mode | auction trigger |
@@ -174,15 +174,15 @@ Feature: Confirm return to continuous trading during significant mark price chan
174
174
# the last second of the original extensions
175
175
And the network moves ahead "3" blocks
176
176
Then the market data for the market "ETH/FEB23" should be:
177
- | mark price | trading mode | auction trigger | horizon | ref price | min bound | max bound |
178
- | 1000 | TRADING_MODE_MONITORING_AUCTION | AUCTION_TRIGGER_PRICE | 30 | 1000 | 997 | 1003 |
177
+ | mark price | trading mode | auction trigger |
178
+ | 1000 | TRADING_MODE_MONITORING_AUCTION | AUCTION_TRIGGER_PRICE |
179
179
180
180
When the parties place the following orders with ticks:
181
181
| party | market id | side | volume | price | resulting trades | type | tif |
182
182
| party1 | ETH /FEB23 | buy | 1 | 2004 | 0 | TYPE_LIMIT | TIF_GTC |
183
183
| party2 | ETH /FEB23 | sell | 1 | 2004 | 0 | TYPE_LIMIT | TIF_GTC |
184
184
185
- # the updated extension triggered, no triggers left
185
+ # the updated extension triggered, no triggers left as they've all been switched off since update took place during auction
186
186
And the network moves ahead "1" blocks
187
187
Then the market data for the market "ETH/FEB23" should be:
188
188
| mark price | trading mode | auction trigger |
@@ -217,14 +217,14 @@ Feature: Confirm return to continuous trading during significant mark price chan
217
217
# the last second of the original extensions
218
218
And the network moves ahead "3" blocks
219
219
Then the market data for the market "ETH/FEB23" should be:
220
- | mark price | trading mode | auction trigger | horizon | ref price | min bound | max bound |
221
- | 1000 | TRADING_MODE_MONITORING_AUCTION | AUCTION_TRIGGER_PRICE | 30 | 1000 | 997 | 1003 |
220
+ | mark price | trading mode | auction trigger |
221
+ | 1000 | TRADING_MODE_MONITORING_AUCTION | AUCTION_TRIGGER_PRICE |
222
222
223
223
When the oracles broadcast data with block time signed with "0xCAFECAFE1" :
224
224
| name | value | time offset |
225
225
| prices .ETH .value | 2000 | -1s |
226
226
227
- # the updated extension triggered, no triggers left
227
+ # the updated extension triggered, no triggers left as they've all been switched off since update took place during auction
228
228
And the network moves ahead "1" blocks
229
229
Then the market data for the market "ETH/FEB23" should be:
230
230
| mark price | trading mode | auction trigger |
@@ -253,4 +253,26 @@ Feature: Confirm return to continuous trading during significant mark price chan
253
253
And the network moves ahead "118" blocks
254
254
Then the market data for the market "ETH/FEB23" should be:
255
255
| mark price | trading mode | auction trigger | last traded price | horizon | ref price | min bound | max bound |
256
- | 1000 | TRADING_MODE_CONTINUOUS | AUCTION_TRIGGER_UNSPECIFIED | 1003 | 30 | 1003 | 1000 | 1006 |
256
+ | 1000 | TRADING_MODE_CONTINUOUS | AUCTION_TRIGGER_UNSPECIFIED | 1003 | 30 | 1003 | 1000 | 1006 |
257
+
258
+ Scenario : Verify that trigger update in continuous trading works as expected
259
+
260
+ When the network moves ahead "2" blocks
261
+ Then the market data for the market "ETH/FEB23" should be:
262
+ | mark price | trading mode | horizon | ref price | min bound | max bound |
263
+ | 1000 | TRADING_MODE_CONTINUOUS | 60 | 1000 | 995 | 1005 |
264
+
265
+ And the price monitoring named "my-price-monitoring-2" :
266
+ | horizon | probability | auction extension |
267
+ | 30 | 0 .95 | 1 |
268
+
269
+ # update trigger here so that there's only one
270
+ When the markets are updated:
271
+ | id | price monitoring | price type | source weights | source staleness tolerance |
272
+ | ETH /FEB23 | my -price -monitoring -2 | weight | 0 ,0 ,1 ,0 | 0s ,0s ,0h0m120s ,0s |
273
+
274
+ # the last second of the original extensions
275
+ And the network moves ahead "3" blocks
276
+ Then the market data for the market "ETH/FEB23" should be:
277
+ | mark price | trading mode | horizon | ref price | min bound | max bound |
278
+ | 1000 | TRADING_MODE_CONTINUOUS | 30 | 1000 | 997 | 1003 |
0 commit comments