Regenerated Core API and Gateway API SDK

src/RadixDlt.CoreApiSdk/generated/Api/LTSApi.cs

@@ -63,11 +63,11 @@
  */
 
 /*
- * Radix Core API - Babylon (Anemone)
+ * Radix Core API - Babylon (Bottlenose)
  *
  * This API is exposed by the Babylon Radix node to give clients access to the Radix Engine, Mempool and State in the node.  The default configuration is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Very heavy load may impact the node's function. The node exposes a configuration flag which allows disabling certain endpoints which may be problematic, but monitoring is advised. This configuration parameter is `api.core.flags.enable_unbounded_endpoints` / `RADIXDLT_CORE_API_FLAGS_ENABLE_UNBOUNDED_ENDPOINTS`.  This API exposes queries against the node's current state (see `/lts/state/` or `/state/`), and streams of transaction history (under `/lts/stream/` or `/stream`).  If you require queries against snapshots of historical ledger state, you may also wish to consider using the [Gateway API](https://docs-babylon.radixdlt.com/).  ## Integration and forward compatibility guarantees  Integrators (such as exchanges) are recommended to use the `/lts/` endpoints - they have been designed to be clear and simple for integrators wishing to create and monitor transactions involving fungible transfers to/from accounts.  All endpoints under `/lts/` have high guarantees of forward compatibility in future node versions. We may add new fields, but existing fields will not be changed. Assuming the integrating code uses a permissive JSON parser which ignores unknown fields, any additions will not affect existing code.  Other endpoints may be changed with new node versions carrying protocol-updates, although any breaking changes will be flagged clearly in the corresponding release notes.  All responses may have additional fields added, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects. 
  *
- * The version of the OpenAPI document: v1.1.3
+ * The version of the OpenAPI document: v1.2.0
  * Generated by: https://github.com/openapitools/openapi-generator.git
  */
 

src/RadixDlt.CoreApiSdk/generated/Api/MempoolApi.cs

@@ -63,11 +63,11 @@
  */
 
 /*
- * Radix Core API - Babylon (Anemone)
+ * Radix Core API - Babylon (Bottlenose)
  *
  * This API is exposed by the Babylon Radix node to give clients access to the Radix Engine, Mempool and State in the node.  The default configuration is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Very heavy load may impact the node's function. The node exposes a configuration flag which allows disabling certain endpoints which may be problematic, but monitoring is advised. This configuration parameter is `api.core.flags.enable_unbounded_endpoints` / `RADIXDLT_CORE_API_FLAGS_ENABLE_UNBOUNDED_ENDPOINTS`.  This API exposes queries against the node's current state (see `/lts/state/` or `/state/`), and streams of transaction history (under `/lts/stream/` or `/stream`).  If you require queries against snapshots of historical ledger state, you may also wish to consider using the [Gateway API](https://docs-babylon.radixdlt.com/).  ## Integration and forward compatibility guarantees  Integrators (such as exchanges) are recommended to use the `/lts/` endpoints - they have been designed to be clear and simple for integrators wishing to create and monitor transactions involving fungible transfers to/from accounts.  All endpoints under `/lts/` have high guarantees of forward compatibility in future node versions. We may add new fields, but existing fields will not be changed. Assuming the integrating code uses a permissive JSON parser which ignores unknown fields, any additions will not affect existing code.  Other endpoints may be changed with new node versions carrying protocol-updates, although any breaking changes will be flagged clearly in the corresponding release notes.  All responses may have additional fields added, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects. 
  *
- * The version of the OpenAPI document: v1.1.3
+ * The version of the OpenAPI document: v1.2.0
  * Generated by: https://github.com/openapitools/openapi-generator.git
  */
 

src/RadixDlt.CoreApiSdk/generated/Api/StateApi.cs

@@ -63,11 +63,11 @@
  */
 
 /*
- * Radix Core API - Babylon (Anemone)
+ * Radix Core API - Babylon (Bottlenose)
  *
  * This API is exposed by the Babylon Radix node to give clients access to the Radix Engine, Mempool and State in the node.  The default configuration is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Very heavy load may impact the node's function. The node exposes a configuration flag which allows disabling certain endpoints which may be problematic, but monitoring is advised. This configuration parameter is `api.core.flags.enable_unbounded_endpoints` / `RADIXDLT_CORE_API_FLAGS_ENABLE_UNBOUNDED_ENDPOINTS`.  This API exposes queries against the node's current state (see `/lts/state/` or `/state/`), and streams of transaction history (under `/lts/stream/` or `/stream`).  If you require queries against snapshots of historical ledger state, you may also wish to consider using the [Gateway API](https://docs-babylon.radixdlt.com/).  ## Integration and forward compatibility guarantees  Integrators (such as exchanges) are recommended to use the `/lts/` endpoints - they have been designed to be clear and simple for integrators wishing to create and monitor transactions involving fungible transfers to/from accounts.  All endpoints under `/lts/` have high guarantees of forward compatibility in future node versions. We may add new fields, but existing fields will not be changed. Assuming the integrating code uses a permissive JSON parser which ignores unknown fields, any additions will not affect existing code.  Other endpoints may be changed with new node versions carrying protocol-updates, although any breaking changes will be flagged clearly in the corresponding release notes.  All responses may have additional fields added, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects. 
  *
- * The version of the OpenAPI document: v1.1.3
+ * The version of the OpenAPI document: v1.2.0
  * Generated by: https://github.com/openapitools/openapi-generator.git
  */
 

src/RadixDlt.CoreApiSdk/generated/Api/StatusApi.cs

@@ -63,11 +63,11 @@
  */
 
 /*
- * Radix Core API - Babylon (Anemone)
+ * Radix Core API - Babylon (Bottlenose)
  *
  * This API is exposed by the Babylon Radix node to give clients access to the Radix Engine, Mempool and State in the node.  The default configuration is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Very heavy load may impact the node's function. The node exposes a configuration flag which allows disabling certain endpoints which may be problematic, but monitoring is advised. This configuration parameter is `api.core.flags.enable_unbounded_endpoints` / `RADIXDLT_CORE_API_FLAGS_ENABLE_UNBOUNDED_ENDPOINTS`.  This API exposes queries against the node's current state (see `/lts/state/` or `/state/`), and streams of transaction history (under `/lts/stream/` or `/stream`).  If you require queries against snapshots of historical ledger state, you may also wish to consider using the [Gateway API](https://docs-babylon.radixdlt.com/).  ## Integration and forward compatibility guarantees  Integrators (such as exchanges) are recommended to use the `/lts/` endpoints - they have been designed to be clear and simple for integrators wishing to create and monitor transactions involving fungible transfers to/from accounts.  All endpoints under `/lts/` have high guarantees of forward compatibility in future node versions. We may add new fields, but existing fields will not be changed. Assuming the integrating code uses a permissive JSON parser which ignores unknown fields, any additions will not affect existing code.  Other endpoints may be changed with new node versions carrying protocol-updates, although any breaking changes will be flagged clearly in the corresponding release notes.  All responses may have additional fields added, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects. 
  *
- * The version of the OpenAPI document: v1.1.3
+ * The version of the OpenAPI document: v1.2.0
  * Generated by: https://github.com/openapitools/openapi-generator.git
  */
 
@@ -135,7 +135,7 @@ public interface IStatusApiSync : IApiAccessor
         /// Get Scenarios' results.
         /// </summary>
         /// <remarks>
-        /// Get results of test-oriented \&quot;Genesis Scenarios\&quot; executed on this Network.
+        /// Get results of test \&quot;Scenarios\&quot; executed on this Network. Note: these Scenarios are meant to only be executed on test Networks; on a production Node, the response is expected to be empty. 
         /// </remarks>
         /// <exception cref="RadixDlt.CoreApiSdk.Client.ApiException">Thrown when fails to make API call</exception>
         /// <param name="scenariosRequest"></param>
@@ -146,7 +146,7 @@ public interface IStatusApiSync : IApiAccessor
         /// Get Scenarios&#39; results.
         /// </summary>
         /// <remarks>
-        /// Get results of test-oriented \&quot;Genesis Scenarios\&quot; executed on this Network.
+        /// Get results of test \&quot;Scenarios\&quot; executed on this Network. Note: these Scenarios are meant to only be executed on test Networks; on a production Node, the response is expected to be empty. 
         /// </remarks>
         /// <exception cref="RadixDlt.CoreApiSdk.Client.ApiException">Thrown when fails to make API call</exception>
         /// <param name="scenariosRequest"></param>
@@ -209,7 +209,7 @@ public interface IStatusApiAsync : IApiAccessor
         /// Get Scenarios&#39; results.
         /// </summary>
         /// <remarks>
-        /// Get results of test-oriented \&quot;Genesis Scenarios\&quot; executed on this Network.
+        /// Get results of test \&quot;Scenarios\&quot; executed on this Network. Note: these Scenarios are meant to only be executed on test Networks; on a production Node, the response is expected to be empty. 
         /// </remarks>
         /// <exception cref="RadixDlt.CoreApiSdk.Client.ApiException">Thrown when fails to make API call</exception>
         /// <param name="scenariosRequest"></param>
@@ -221,7 +221,7 @@ public interface IStatusApiAsync : IApiAccessor
         /// Get Scenarios&#39; results.
         /// </summary>
         /// <remarks>
-        /// Get results of test-oriented \&quot;Genesis Scenarios\&quot; executed on this Network.
+        /// Get results of test \&quot;Scenarios\&quot; executed on this Network. Note: these Scenarios are meant to only be executed on test Networks; on a production Node, the response is expected to be empty. 
         /// </remarks>
         /// <exception cref="RadixDlt.CoreApiSdk.Client.ApiException">Thrown when fails to make API call</exception>
         /// <param name="scenariosRequest"></param>
@@ -660,7 +660,7 @@ public RadixDlt.CoreApiSdk.Client.ApiResponse<NetworkStatusResponse> StatusNetwo
         }
 
         /// <summary>
-        /// Get Scenarios&#39; results. Get results of test-oriented \&quot;Genesis Scenarios\&quot; executed on this Network.
+        /// Get Scenarios&#39; results. Get results of test \&quot;Scenarios\&quot; executed on this Network. Note: these Scenarios are meant to only be executed on test Networks; on a production Node, the response is expected to be empty. 
         /// </summary>
         /// <exception cref="RadixDlt.CoreApiSdk.Client.ApiException">Thrown when fails to make API call</exception>
         /// <param name="scenariosRequest"></param>
@@ -672,7 +672,7 @@ public ScenariosResponse StatusScenariosPost(ScenariosRequest scenariosRequest)
         }
 
         /// <summary>
-        /// Get Scenarios&#39; results. Get results of test-oriented \&quot;Genesis Scenarios\&quot; executed on this Network.
+        /// Get Scenarios&#39; results. Get results of test \&quot;Scenarios\&quot; executed on this Network. Note: these Scenarios are meant to only be executed on test Networks; on a production Node, the response is expected to be empty. 
         /// </summary>
         /// <exception cref="RadixDlt.CoreApiSdk.Client.ApiException">Thrown when fails to make API call</exception>
         /// <param name="scenariosRequest"></param>
@@ -716,7 +716,7 @@ public RadixDlt.CoreApiSdk.Client.ApiResponse<ScenariosResponse> StatusScenarios
         }
 
         /// <summary>
-        /// Get Scenarios&#39; results. Get results of test-oriented \&quot;Genesis Scenarios\&quot; executed on this Network.
+        /// Get Scenarios&#39; results. Get results of test \&quot;Scenarios\&quot; executed on this Network. Note: these Scenarios are meant to only be executed on test Networks; on a production Node, the response is expected to be empty. 
         /// </summary>
         /// <exception cref="RadixDlt.CoreApiSdk.Client.ApiException">Thrown when fails to make API call</exception>
         /// <param name="scenariosRequest"></param>
@@ -729,7 +729,7 @@ public RadixDlt.CoreApiSdk.Client.ApiResponse<ScenariosResponse> StatusScenarios
         }
 
         /// <summary>
-        /// Get Scenarios&#39; results. Get results of test-oriented \&quot;Genesis Scenarios\&quot; executed on this Network.
+        /// Get Scenarios&#39; results. Get results of test \&quot;Scenarios\&quot; executed on this Network. Note: these Scenarios are meant to only be executed on test Networks; on a production Node, the response is expected to be empty. 
         /// </summary>
         /// <exception cref="RadixDlt.CoreApiSdk.Client.ApiException">Thrown when fails to make API call</exception>
         /// <param name="scenariosRequest"></param>

src/RadixDlt.CoreApiSdk/generated/Api/StreamApi.cs

@@ -63,11 +63,11 @@
  */
 
 /*
- * Radix Core API - Babylon (Anemone)
+ * Radix Core API - Babylon (Bottlenose)
  *
  * This API is exposed by the Babylon Radix node to give clients access to the Radix Engine, Mempool and State in the node.  The default configuration is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Very heavy load may impact the node's function. The node exposes a configuration flag which allows disabling certain endpoints which may be problematic, but monitoring is advised. This configuration parameter is `api.core.flags.enable_unbounded_endpoints` / `RADIXDLT_CORE_API_FLAGS_ENABLE_UNBOUNDED_ENDPOINTS`.  This API exposes queries against the node's current state (see `/lts/state/` or `/state/`), and streams of transaction history (under `/lts/stream/` or `/stream`).  If you require queries against snapshots of historical ledger state, you may also wish to consider using the [Gateway API](https://docs-babylon.radixdlt.com/).  ## Integration and forward compatibility guarantees  Integrators (such as exchanges) are recommended to use the `/lts/` endpoints - they have been designed to be clear and simple for integrators wishing to create and monitor transactions involving fungible transfers to/from accounts.  All endpoints under `/lts/` have high guarantees of forward compatibility in future node versions. We may add new fields, but existing fields will not be changed. Assuming the integrating code uses a permissive JSON parser which ignores unknown fields, any additions will not affect existing code.  Other endpoints may be changed with new node versions carrying protocol-updates, although any breaking changes will be flagged clearly in the corresponding release notes.  All responses may have additional fields added, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects. 
  *
- * The version of the OpenAPI document: v1.1.3
+ * The version of the OpenAPI document: v1.2.0
  * Generated by: https://github.com/openapitools/openapi-generator.git
  */
 

src/RadixDlt.CoreApiSdk/generated/Api/TransactionApi.cs

@@ -63,11 +63,11 @@
  */
 
 /*
- * Radix Core API - Babylon (Anemone)
+ * Radix Core API - Babylon (Bottlenose)
  *
  * This API is exposed by the Babylon Radix node to give clients access to the Radix Engine, Mempool and State in the node.  The default configuration is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Very heavy load may impact the node's function. The node exposes a configuration flag which allows disabling certain endpoints which may be problematic, but monitoring is advised. This configuration parameter is `api.core.flags.enable_unbounded_endpoints` / `RADIXDLT_CORE_API_FLAGS_ENABLE_UNBOUNDED_ENDPOINTS`.  This API exposes queries against the node's current state (see `/lts/state/` or `/state/`), and streams of transaction history (under `/lts/stream/` or `/stream`).  If you require queries against snapshots of historical ledger state, you may also wish to consider using the [Gateway API](https://docs-babylon.radixdlt.com/).  ## Integration and forward compatibility guarantees  Integrators (such as exchanges) are recommended to use the `/lts/` endpoints - they have been designed to be clear and simple for integrators wishing to create and monitor transactions involving fungible transfers to/from accounts.  All endpoints under `/lts/` have high guarantees of forward compatibility in future node versions. We may add new fields, but existing fields will not be changed. Assuming the integrating code uses a permissive JSON parser which ignores unknown fields, any additions will not affect existing code.  Other endpoints may be changed with new node versions carrying protocol-updates, although any breaking changes will be flagged clearly in the corresponding release notes.  All responses may have additional fields added, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects. 
  *
- * The version of the OpenAPI document: v1.1.3
+ * The version of the OpenAPI document: v1.2.0
  * Generated by: https://github.com/openapitools/openapi-generator.git
  */
 

src/RadixDlt.CoreApiSdk/generated/Client/ApiClient.cs

@@ -63,11 +63,11 @@
  */
 
 /*
- * Radix Core API - Babylon (Anemone)
+ * Radix Core API - Babylon (Bottlenose)
  *
  * This API is exposed by the Babylon Radix node to give clients access to the Radix Engine, Mempool and State in the node.  The default configuration is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Very heavy load may impact the node's function. The node exposes a configuration flag which allows disabling certain endpoints which may be problematic, but monitoring is advised. This configuration parameter is `api.core.flags.enable_unbounded_endpoints` / `RADIXDLT_CORE_API_FLAGS_ENABLE_UNBOUNDED_ENDPOINTS`.  This API exposes queries against the node's current state (see `/lts/state/` or `/state/`), and streams of transaction history (under `/lts/stream/` or `/stream`).  If you require queries against snapshots of historical ledger state, you may also wish to consider using the [Gateway API](https://docs-babylon.radixdlt.com/).  ## Integration and forward compatibility guarantees  Integrators (such as exchanges) are recommended to use the `/lts/` endpoints - they have been designed to be clear and simple for integrators wishing to create and monitor transactions involving fungible transfers to/from accounts.  All endpoints under `/lts/` have high guarantees of forward compatibility in future node versions. We may add new fields, but existing fields will not be changed. Assuming the integrating code uses a permissive JSON parser which ignores unknown fields, any additions will not affect existing code.  Other endpoints may be changed with new node versions carrying protocol-updates, although any breaking changes will be flagged clearly in the corresponding release notes.  All responses may have additional fields added, so clients are advised to use JSON parsers which ignore unknown fields on JSON objects. 
  *
- * The version of the OpenAPI document: v1.1.3
+ * The version of the OpenAPI document: v1.2.0
  * Generated by: https://github.com/openapitools/openapi-generator.git
  */