Get network limits

GET 
/api/v2/network/limits

Get the network limits relating to asset and market creation

Responses

200

A successful response.

application/json

Schema

Schema

limits object

List of received network limits.

canProposeAsset boolean

Are asset proposals allowed at this point in time.

canProposeMarket boolean

Are market proposals allowed at this point in time.

canProposePerpetualMarket boolean

Are perpetual market proposals allowed at this point in time.

canProposeSpotMarket boolean

Are spot market proposals allowed at this point in time.

canUseAmm boolean

Can parties use AMM related transactions.

genesisLoaded boolean

True once the genesis file is loaded.

proposeAssetEnabled boolean

Are asset proposals enabled on this chain.

proposeAssetEnabledFrom int64

Timestamp in Unix nanoseconds at which asset proposals will be enabled (0 indicates not set).

proposeMarketEnabled boolean

Are market proposals enabled on this chain.

proposeMarketEnabledFrom int64

Timestamp in Unix nanoseconds at which market proposals will be enabled (0 indicates not set).

Example (from schema)

{
  "limits": {
    "canProposeAsset": true,
    "canProposeMarket": true,
    "canProposePerpetualMarket": true,
    "canProposeSpotMarket": true,
    "canUseAmm": true,
    "genesisLoaded": true,
    "proposeAssetEnabled": true,
    "proposeAssetEnabledFrom": "string",
    "proposeMarketEnabled": true,
    "proposeMarketEnabledFrom": "string"
  }
}

500

An internal server error

application/json

Schema

Schema

code int32
details object[]
Array [
@type string
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:
• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.
Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.
]
message string

Example (from schema)

{
  "code": 0,
  "details": [
    {
      "@type": "string"
    }
  ],
  "message": "string"
}

default

An unexpected error response.

application/json

Schema

Schema

code int32
details object[]
Array [
@type string
A URL/resource name that uniquely identifies the type of the serialized protocol buffer message. This string must contain at least one "/" character. The last segment of the URL's path must represent the fully qualified name of the type (as in path/google.protobuf.Duration). The name should be in a canonical form (e.g., leading "." is not accepted).
In practice, teams usually precompile into the binary all types that they expect it to use in the context of Any. However, for URLs which use the scheme http, https, or no scheme, one can optionally set up a type server that maps type URLs to message definitions as follows:
• If no scheme is provided, https is assumed.
• An HTTP GET on the URL must yield a [google.protobuf.Type][] value in binary format, or produce an error.
• Applications are allowed to cache lookup results based on the URL, or have them precompiled into a binary to avoid any lookup. Therefore, binary compatibility needs to be preserved on changes to types. (Use versioned type names to manage breaking changes.)
Note: this functionality is not currently available in the official protobuf release, and it is not used for type URLs beginning with type.googleapis.com.
Schemes other than http, https (or the empty scheme) might be used with implementation specific semantics.
]
message string

Example (from schema)

{
  "code": 0,
  "details": [
    {
      "@type": "string"
    }
  ],
  "message": "string"
}

Loading...