code.vegaprotocol.io/vega@v0.79.0/core/integration/features/spot/orders/0026-AUCT-031.feature (about)

     1  Feature: Spot market
     2  
     3    Background:
     4      Given time is updated to "2024-01-01T00:00:00Z"
     5  
     6      Given the following network parameters are set:
     7        | name                                                | value |
     8        | network.markPriceUpdateMaximumFrequency             | 0s    |
     9        | market.value.windowLength                           | 1h    |
    10      
    11      Given the following assets are registered:
    12        | id  | decimal places |
    13        | ETH | 2              |
    14        | BTC | 2              |
    15  
    16      Given the fees configuration named "fees-config-1":
    17        | maker fee | infrastructure fee |
    18        | 0.01      | 0.03               |
    19      Given the log normal risk model named "lognormal-risk-model-1":
    20        | risk aversion | tau  | mu | r   | sigma |
    21        | 0.001         | 0.01 | 0  | 0.0 | 1.2   |
    22      And the price monitoring named "price-monitoring-1":
    23        | horizon | probability | auction extension |
    24        | 60      | 0.999       | 1                 |
    25  
    26      And the spot markets:
    27        | id      | name    | base asset | quote asset | risk model             | auction duration | fees          | price monitoring   | decimal places | position decimal places | sla params    |
    28        | BTC/ETH | BTC/ETH | BTC        | ETH         | lognormal-risk-model-1 | 1                | fees-config-1 | price-monitoring-1 | 2              | 2                       | default-basic |
    29  
    30      # setup accounts
    31      Given the parties deposit on asset's general account the following amount:
    32        | party  | asset | amount |
    33        | party1 | ETH   | 10000  |
    34        | party2 | ETH   | 10000  |
    35        | party4 | BTC   | 1000   |
    36        | party5 | BTC   | 1000   |
    37      And the average block duration is "1"
    38  
    39    Scenario: When entering an auction, all GFN orders will be cancelled. (0026-AUCT-031)
    40  
    41      # Place some orders that cross so we can leave the auction
    42      And the parties place the following orders:
    43        | party  | market id | side | volume | price | resulting trades | type       | tif     | reference |
    44        | party1 | BTC/ETH   | buy  | 1      | 1000  | 0                | TYPE_LIMIT | TIF_GFA | buy1      |
    45        | party5 | BTC/ETH   | sell | 1      | 1000  | 0                | TYPE_LIMIT | TIF_GFA | sell1     |
    46      And the opening auction period ends for market "BTC/ETH"
    47      When the network moves ahead "1" blocks
    48      Then the trading mode should be "TRADING_MODE_CONTINUOUS" for the market "BTC/ETH"
    49      And the mark price should be "1000" for the market "BTC/ETH"
    50  
    51      # Place some GFN orders into the orderbook
    52      And the parties place the following orders:
    53        | party  | market id | side | volume | price | resulting trades | type       | tif     | reference |
    54        | party1 | BTC/ETH   | buy  | 10     | 980   | 0                | TYPE_LIMIT | TIF_GFN | buy2      |
    55        | party2 | BTC/ETH   | buy  | 10     | 985   | 0                | TYPE_LIMIT | TIF_GFN | buy3      |
    56        | party4 | BTC/ETH   | sell | 10     | 1015  | 0                | TYPE_LIMIT | TIF_GFN | sell2     |
    57        | party5 | BTC/ETH   | sell | 10     | 1020  | 0                | TYPE_LIMIT | TIF_GFN | sell3     |
    58        | party1 | BTC/ETH   | buy  | 1      | 1015  | 0                | TYPE_LIMIT | TIF_GTC | buy4     |
    59   
    60      When the network moves ahead "1" blocks
    61  
    62      # Check we are now in monitoring auction
    63      Then the trading mode should be "TRADING_MODE_MONITORING_AUCTION" for the market "BTC/ETH"
    64  
    65      # Check that all the GFN orders have been cancelled
    66    And the orders should have the following states:
    67      | party  | market id | reference | side | volume | remaining | price | status        |
    68      | party1 | BTC/ETH   | buy2      | buy  | 10     | 10        | 980   | STATUS_CANCELLED |
    69      | party2 | BTC/ETH   | buy3      | buy  | 10     | 10        | 985   | STATUS_CANCELLED |
    70      | party4 | BTC/ETH   | sell2     | sell | 10     | 10        | 1015  | STATUS_CANCELLED |
    71      | party5 | BTC/ETH   | sell3     | sell | 10     | 10        | 1020  | STATUS_CANCELLED |
    72  
    73  
    74