Skip to main content
Version: testnet (v0.73)

Propose updates to a market

Propose changes to an existing market.

Requirements​

You will need:

Anatomy of an update market proposal​

The update market proposal requires the same fields as a new market proposal. See the descriptions in the new market proposal tutorial for more on each field.

In addition to the parameters you want to change, you must include all existing parameters from the original new market proposal, even if they are not being changed.

Locked fields​

The following fields, which you might recognise from new market proposals, are immutable and cannot be changed. They are not included in the proposal templates.

  • decimalPlaces
  • positionDecimalPlaces
  • name
  • settlementAsset

Thresholds​

Note that some network parameters may differ, such as the limits on how long the voting period can last, as follows.

FieldDescription
closingTimestampTimestamp (Unix time in seconds) when voting closes for this proposal. The chosen time must be between 🔗0h1m0s and 🔗720h after the proposal submission time. (int64 as string)
enactmentTimestamp Timestamp (Unix time in seconds) when proposal gets enacted (if passed). The chosen time must be between 🔗0h1m0s and 🔗720h after closingTimestamp. (int64 as string)

Templates and submitting​

In the tabs below you'll see:

  • Annotated example describing what each field is for
  • JSON example that can be submitted with the governance dApp ↗
  • Command line examples for different operating systems

Replace the example data with the relevant details before submitting.

{
 rationale: {
  title: "Update Lorem Ipsum market",
  description: "A proposal to update Lorem Ipsum market"
 },
 terms: {
  updateMarket: {
   // Market ID the update is for.
   marketId: "123",
   changes: {
    // DEPRECATED: Use liquidity SLA parameters instead.
    // Percentage move up and down from the mid price which specifies the range of
    lpPriceRange: 11,

    // Linear slippage factor is used to cap the slippage component of maintenance margin - it is applied to the slippage volume.
    linearSlippageFactor: 0.001,

    // Quadratic slippage factor is used to cap the slippage component of maintenance margin - it is applied to the square of the slippage volume.
    quadraticSlippageFactor: 0,

    // Instrument configuration
    instrument: {
     // Instrument code, human-readable shortcode used to describe the instrument.
     code: "APPLES.22",

     // Future product configuration
     future: {
      // Human-readable name/abbreviation of the quote name. (string)
      quoteName: "tEuro",

      // The data source spec describing the data of settlement data. (object)
      dataSourceSpecForSettlementData: {
       external: {
        oracle: {
         // Signers is the list of authorized signatures that signed the data for this
         // source. All the signatures in the data source data should be contained in (array of objects)
         signers: [
          {
           ethAddress: {
            address: "0xfCEAdAFab14d46e20144F48824d0C09B1a03F2BC"
           }
          }
         ],

         // Filters describes which source data are considered of interest or not for
         // the product (or the risk model).
         filters: [
          key: {
           // Name of the property. (string)
           name: "prices.ORANGES.value",

           // Data type of the property. (string)
           type: "TYPE_INTEGER",

           // Optional decimal place to be be applied on the provided value
           // valid only for PropertyType of type DECIMAL and INTEGER
           numberDecimalPlaces: "5",
          },

          // Conditions that should be matched by the data to be
          // considered of interest.
          conditions: [
           {
            // Type of comparison to make on the value. (string)
            operator: "OPERATOR_GREATER_THAN",

            // Value to be compared with by the operator. (string)
            value: "0",
           }
          ]
         },
         {
          key: {
           name: "prices.ORANGES.timestamp",
           type: "TYPE_INTEGER",
          },
          conditions: [
           {
            operator: "OPERATOR_GREATER_THAN",
            value: "1648684800",
           }
          ]
         }
        ]
       }
      },

      // The data source spec describing the data source for trading termination. (object)
      dataSourceSpecForTradingTermination: {
       // The data source spec describing the data source for trading termination.
       internal {
        // Internal data source used for emitting timestamps.
        time: {
         // Conditions that the timestamps should meet in order to be considered.
         conditions: [
          {
           // Type of comparison to make on the value. (string)
           operator: "OPERATOR_GREATER_THAN_OR_EQUAL",

           // Value to be compared with by the operator. (string)
           value: "1648684800",
          }
         ]
        }
       },

       // DataSourceSpecToFutureBinding describes which property of the data source data is to be
       used as settlement data and which to use as the trading terminated trigger(object) dataSourceSpecBinding: {
        // Name of the property in the source data that should be used as settlement data.
        // If it is set to "prices.BTC.value", then the Future will use the value of
        // this property as settlement data. (string)
        settlementDataProperty: "prices.ORANGES.value",

        // Name of the property in the data source data that signals termination of trading. (string)
        tradingTerminationProperty: "vegaprotocol.builtin.timestamp"
       }
      },

      // Optional futures market metadata, tags.
      metadata: [
       "source:docs.vega.xyz"
      ],

      // PriceMonitoringParameters contains a collection of triggers to be used for a given market
      priceMonitoringParameters: {
       // PriceMonitoringTrigger holds together price projection horizon τ, probability level p, and auction extension duration
       triggers: [
        {
         // Price monitoring projection horizon τ in seconds. (int64 as string)
         horizon: "43200",

         // Price monitoring probability level p. (string)
         probability: "0.9999999",

         // Price monitoring auction extension duration in seconds should the price
         // breach its theoretical level over the specified horizon at the specified
         // probability level. (int64 as string)
         auctionExtension: "600",
        }
       ]
      },

      // Risk model for log normal
      logNormal: {
       // Tau parameter of the risk model, projection horizon measured as a year fraction used in the expected shortfall
       calculation to obtain the maintenance margin,
       must be a strictly non - negative real number.(number) tau: 0.0001140771161,

       // Risk Aversion Parameter. (double as number)
       riskAversionParameter: "0.0001",

       // Risk model parameters for log normal
       params: {
        // Mu parameter, annualised growth rate of the underlying asset. (double as number)
        mu: 0,

        // R parameter, annualised growth rate of the risk-free asset, used for discounting of future cash flows, can be any real number. (double as number)
        r: 0.016,

        // Sigma parameter, annualised volatility of the underlying asset, must be a strictly non-negative real number. (double as number)
        sigma: 1.25,
       }
      },
     },
    },

    // Timestamp as Unix time in seconds when voting closes for this proposal,
    // constrained by `minClose` and `maxClose` network parameters. (int64 as string)
    closingTimestamp: 1696941757,

    // Timestamp as Unix time in seconds when proposal gets enacted if passed,
    // constrained by `minEnact` and `maxEnact` network parameters. (int64 as string)
    enactmentTimestamp: 1697028157,
   }
  }

Voting​

All proposals are voted on by the community. To vote, community members need, at a minimum, the larger of 🔗more than 0 tokens or 🔗1 token associated to their Vega key.

Your proposal will need participation of 🔗7% and a majority of 🔗66%, so having community support is essential.

Proposers who invite feedback, engage with comments, and make revisions to meet the needs of the community are more likely to be successful.

Enactment​

If successful, the proposal will be enacted at the time you specify in the enactmentTimestamp field.