diff --git a/.gitignore b/.gitignore index 2169825..4ee33b1 100644 --- a/.gitignore +++ b/.gitignore @@ -1,2 +1,3 @@ env -target \ No newline at end of file +target +.venv diff --git a/generated-clients/core-api-client/async-client/.openapi-generator/FILES b/generated-clients/core-api-client/async-client/.openapi-generator/FILES index 4879b76..d1c2f7c 100644 --- a/generated-clients/core-api-client/async-client/.openapi-generator/FILES +++ b/generated-clients/core-api-client/async-client/.openapi-generator/FILES @@ -6,8 +6,6 @@ README.md docs/AccessControllerFieldStateSubstate.md docs/AccessControllerFieldStateValue.md docs/AccessRule.md -docs/AccessRuleNode.md -docs/AccessRuleNodeType.md docs/AccessRuleType.md docs/AccountAddressKey.md docs/AccountAuthorizedDepositorEntrySubstate.md @@ -24,18 +22,20 @@ docs/ActiveValidator.md docs/ActiveValidatorIndex.md docs/ActiveValidatorKey.md docs/AddressType.md -docs/AllOfAccessRuleNode.md -docs/AllOfProofRule.md +docs/AllOfBasicRequirement.md +docs/AllOfCompositeRequirement.md docs/AlwaysVisibleGlobalNodesVersion.md -docs/AmountOfProofRule.md -docs/AnyOfAccessRuleNode.md -docs/AnyOfProofRule.md +docs/AmountOfBasicRequirement.md +docs/AnyOfBasicRequirement.md +docs/AnyOfCompositeRequirement.md docs/AttachedModuleId.md docs/AuthConfig.md docs/AuthorizedDepositorBadge.md docs/AuthorizedDepositorBadgeType.md docs/AuthorizedDepositorKey.md docs/BasicErrorResponse.md +docs/BasicRequirement.md +docs/BasicRequirementType.md docs/BinaryPlaintextMessageContent.md docs/BlueprintCollectionSchema.md docs/BlueprintCollectionSchemaType.md @@ -66,7 +66,10 @@ docs/CommittedIntentMetadata.md docs/CommittedStateIdentifier.md docs/CommittedTransaction.md docs/CommittedTransactionBalanceChanges.md +docs/CompiledPreviewTransaction.md docs/ComponentMethodTargetIdentifier.md +docs/CompositeRequirement.md +docs/CompositeRequirementType.md docs/ConsensusLedgerProofOrigin.md docs/ConsensusManagerFieldConfigSubstate.md docs/ConsensusManagerFieldConfigValue.md @@ -86,7 +89,7 @@ docs/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstate.md docs/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.md docs/CostingModuleConfig.md docs/CostingParameters.md -docs/CountOfProofRule.md +docs/CountOfBasicRequirement.md docs/CreatedSubstate.md docs/DataStruct.md docs/DefaultDepositRule.md @@ -162,6 +165,7 @@ docs/InstructionResourceChanges.md docs/IntentCoreV2.md docs/IntentHeaderV2.md docs/IntentSignatures.md +docs/InvalidTransactionPreviewV2ErrorDetails.md docs/KeyValueBasedStructure.md docs/KeyValueBlueprintCollectionSchema.md docs/KeyValueStoreEntryStructure.md @@ -220,6 +224,7 @@ docs/LtsTransactionSubmitRejectedErrorDetails.md docs/LtsTransactionSubmitRequest.md docs/LtsTransactionSubmitResponse.md docs/MainMethodKey.md +docs/ManifestValidationRuleset.md docs/MapSubstateKey.md docs/MempoolApi.md docs/MempoolListRequest.md @@ -228,6 +233,7 @@ docs/MempoolTransactionHashes.md docs/MempoolTransactionRequest.md docs/MempoolTransactionResponse.md docs/MempoolTransactionResponsePayloadsInner.md +docs/MessageValidationConfig.md docs/MetadataKey.md docs/MetadataModuleEntrySubstate.md docs/MetadataModuleEntryValue.md @@ -323,12 +329,14 @@ docs/PlaintextMessageContent.md docs/PlaintextMessageContentType.md docs/PlaintextTransactionMessage.md docs/PoolVault.md +docs/PreparationSettings.md docs/PresentedBadge.md docs/PresentedBadgeType.md +docs/PreviewFlags.md +docs/PreviewTransaction.md +docs/PreviewTransactionType.md docs/PrimaryRoleRecoveryAttempt.md -docs/ProofAccessRuleNode.md -docs/ProofRule.md -docs/ProofRuleType.md +docs/ProofRuleCompositeRequirement.md docs/ProposerReward.md docs/ProtectedAccessRule.md docs/ProtocolUpdateLedgerProofOrigin.md @@ -345,7 +353,7 @@ docs/RecoveryRoleRecoveryAttempt.md docs/ReferenceType.md docs/RemoteGenericSubstitution.md docs/RequestedStateVersionOutOfBoundsErrorDetails.md -docs/RequireProofRule.md +docs/RequireBasicRequirement.md docs/Requirement.md docs/RequirementType.md docs/ResourceAmount.md @@ -471,10 +479,15 @@ docs/TransactionParseResponse.md docs/TransactionPayloadDetails.md docs/TransactionPayloadStatus.md docs/TransactionPreviewRequest.md -docs/TransactionPreviewRequestFlags.md docs/TransactionPreviewResponse.md docs/TransactionPreviewResponseLogsInner.md docs/TransactionPreviewResponseOptions.md +docs/TransactionPreviewV2ErrorDetails.md +docs/TransactionPreviewV2ErrorDetailsType.md +docs/TransactionPreviewV2ErrorResponse.md +docs/TransactionPreviewV2Request.md +docs/TransactionPreviewV2Response.md +docs/TransactionPreviewV2ResponseOptions.md docs/TransactionReceipt.md docs/TransactionReceiptRequest.md docs/TransactionReceiptResponse.md @@ -494,6 +507,7 @@ docs/TransactionTrackerCollectionEntryValue.md docs/TransactionTrackerFieldStateSubstate.md docs/TransactionTrackerFieldStateValue.md docs/TransactionTrackerTransactionStatus.md +docs/TransactionValidationConfig.md docs/TwoResourcePoolFieldStateSubstate.md docs/TwoResourcePoolFieldStateValue.md docs/TypeInfoDetails.md @@ -525,8 +539,6 @@ src/lib.rs src/models/access_controller_field_state_substate.rs src/models/access_controller_field_state_value.rs src/models/access_rule.rs -src/models/access_rule_node.rs -src/models/access_rule_node_type.rs src/models/access_rule_type.rs src/models/account_address_key.rs src/models/account_authorized_depositor_entry_substate.rs @@ -543,18 +555,20 @@ src/models/active_validator.rs src/models/active_validator_index.rs src/models/active_validator_key.rs src/models/address_type.rs -src/models/all_of_access_rule_node.rs -src/models/all_of_proof_rule.rs +src/models/all_of_basic_requirement.rs +src/models/all_of_composite_requirement.rs src/models/always_visible_global_nodes_version.rs -src/models/amount_of_proof_rule.rs -src/models/any_of_access_rule_node.rs -src/models/any_of_proof_rule.rs +src/models/amount_of_basic_requirement.rs +src/models/any_of_basic_requirement.rs +src/models/any_of_composite_requirement.rs src/models/attached_module_id.rs src/models/auth_config.rs src/models/authorized_depositor_badge.rs src/models/authorized_depositor_badge_type.rs src/models/authorized_depositor_key.rs src/models/basic_error_response.rs +src/models/basic_requirement.rs +src/models/basic_requirement_type.rs src/models/binary_plaintext_message_content.rs src/models/blueprint_collection_schema.rs src/models/blueprint_collection_schema_type.rs @@ -585,7 +599,10 @@ src/models/committed_intent_metadata.rs src/models/committed_state_identifier.rs src/models/committed_transaction.rs src/models/committed_transaction_balance_changes.rs +src/models/compiled_preview_transaction.rs src/models/component_method_target_identifier.rs +src/models/composite_requirement.rs +src/models/composite_requirement_type.rs src/models/consensus_ledger_proof_origin.rs src/models/consensus_manager_field_config_substate.rs src/models/consensus_manager_field_config_value.rs @@ -605,7 +622,7 @@ src/models/consensus_manager_registered_validators_by_stake_index_entry_substate src/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs src/models/costing_module_config.rs src/models/costing_parameters.rs -src/models/count_of_proof_rule.rs +src/models/count_of_basic_requirement.rs src/models/created_substate.rs src/models/data_struct.rs src/models/default_deposit_rule.rs @@ -681,6 +698,7 @@ src/models/instruction_resource_changes.rs src/models/intent_core_v2.rs src/models/intent_header_v2.rs src/models/intent_signatures.rs +src/models/invalid_transaction_preview_v2_error_details.rs src/models/key_value_based_structure.rs src/models/key_value_blueprint_collection_schema.rs src/models/key_value_store_entry_structure.rs @@ -738,6 +756,7 @@ src/models/lts_transaction_submit_rejected_error_details.rs src/models/lts_transaction_submit_request.rs src/models/lts_transaction_submit_response.rs src/models/main_method_key.rs +src/models/manifest_validation_ruleset.rs src/models/map_substate_key.rs src/models/mempool_list_request.rs src/models/mempool_list_response.rs @@ -745,6 +764,7 @@ src/models/mempool_transaction_hashes.rs src/models/mempool_transaction_request.rs src/models/mempool_transaction_response.rs src/models/mempool_transaction_response_payloads_inner.rs +src/models/message_validation_config.rs src/models/metadata_key.rs src/models/metadata_module_entry_substate.rs src/models/metadata_module_entry_value.rs @@ -841,12 +861,14 @@ src/models/plaintext_message_content.rs src/models/plaintext_message_content_type.rs src/models/plaintext_transaction_message.rs src/models/pool_vault.rs +src/models/preparation_settings.rs src/models/presented_badge.rs src/models/presented_badge_type.rs +src/models/preview_flags.rs +src/models/preview_transaction.rs +src/models/preview_transaction_type.rs src/models/primary_role_recovery_attempt.rs -src/models/proof_access_rule_node.rs -src/models/proof_rule.rs -src/models/proof_rule_type.rs +src/models/proof_rule_composite_requirement.rs src/models/proposer_reward.rs src/models/protected_access_rule.rs src/models/protocol_update_ledger_proof_origin.rs @@ -863,7 +885,7 @@ src/models/recovery_role_recovery_attempt.rs src/models/reference_type.rs src/models/remote_generic_substitution.rs src/models/requested_state_version_out_of_bounds_error_details.rs -src/models/require_proof_rule.rs +src/models/require_basic_requirement.rs src/models/requirement.rs src/models/requirement_type.rs src/models/resource_amount.rs @@ -985,10 +1007,15 @@ src/models/transaction_parse_response.rs src/models/transaction_payload_details.rs src/models/transaction_payload_status.rs src/models/transaction_preview_request.rs -src/models/transaction_preview_request_flags.rs src/models/transaction_preview_response.rs src/models/transaction_preview_response_logs_inner.rs src/models/transaction_preview_response_options.rs +src/models/transaction_preview_v2_error_details.rs +src/models/transaction_preview_v2_error_details_type.rs +src/models/transaction_preview_v2_error_response.rs +src/models/transaction_preview_v2_request.rs +src/models/transaction_preview_v2_response.rs +src/models/transaction_preview_v2_response_options.rs src/models/transaction_receipt.rs src/models/transaction_receipt_request.rs src/models/transaction_receipt_response.rs @@ -1008,6 +1035,7 @@ src/models/transaction_tracker_collection_entry_value.rs src/models/transaction_tracker_field_state_substate.rs src/models/transaction_tracker_field_state_value.rs src/models/transaction_tracker_transaction_status.rs +src/models/transaction_validation_config.rs src/models/two_resource_pool_field_state_substate.rs src/models/two_resource_pool_field_state_value.rs src/models/type_info_details.rs diff --git a/generated-clients/core-api-client/async-client/README.md b/generated-clients/core-api-client/async-client/README.md index ad846f7..7cf39f7 100644 --- a/generated-clients/core-api-client/async-client/README.md +++ b/generated-clients/core-api-client/async-client/README.md @@ -34,7 +34,7 @@ fields on JSON objects. This API client was generated by the [OpenAPI Generator](https://openapi-generator.tech) project. By using the [openapi-spec](https://openapis.org) from a remote server, you can easily generate an API client. -- API version: v1.2.3 +- API version: v1.3.0 - Package version: 1.0.0 - Generator version: 7.6.0 - Build package: `org.openapitools.codegen.languages.RustClientCodegen` @@ -78,7 +78,8 @@ Class | Method | HTTP request | Description *StreamApi* | [**stream_transactions_post**](docs/StreamApi.md#stream_transactions_post) | **POST** /stream/transactions | Get Committed Transactions *TransactionApi* | [**transaction_call_preview_post**](docs/TransactionApi.md#transaction_call_preview_post) | **POST** /transaction/call-preview | Scrypto Call Preview *TransactionApi* | [**transaction_parse_post**](docs/TransactionApi.md#transaction_parse_post) | **POST** /transaction/parse | Parse Transaction Payload -*TransactionApi* | [**transaction_preview_post**](docs/TransactionApi.md#transaction_preview_post) | **POST** /transaction/preview | Transaction Preview +*TransactionApi* | [**transaction_preview_post**](docs/TransactionApi.md#transaction_preview_post) | **POST** /transaction/preview | Transaction Preview V1 +*TransactionApi* | [**transaction_preview_v2_post**](docs/TransactionApi.md#transaction_preview_v2_post) | **POST** /transaction/preview-v2 | Transaction Preview V2 *TransactionApi* | [**transaction_receipt_post**](docs/TransactionApi.md#transaction_receipt_post) | **POST** /transaction/receipt | Get Transaction Receipt *TransactionApi* | [**transaction_status_post**](docs/TransactionApi.md#transaction_status_post) | **POST** /transaction/status | Get Transaction Status *TransactionApi* | [**transaction_submit_post**](docs/TransactionApi.md#transaction_submit_post) | **POST** /transaction/submit | Transaction Submit @@ -89,8 +90,6 @@ Class | Method | HTTP request | Description - [AccessControllerFieldStateSubstate](docs/AccessControllerFieldStateSubstate.md) - [AccessControllerFieldStateValue](docs/AccessControllerFieldStateValue.md) - [AccessRule](docs/AccessRule.md) - - [AccessRuleNode](docs/AccessRuleNode.md) - - [AccessRuleNodeType](docs/AccessRuleNodeType.md) - [AccessRuleType](docs/AccessRuleType.md) - [AccountAddressKey](docs/AccountAddressKey.md) - [AccountAuthorizedDepositorEntrySubstate](docs/AccountAuthorizedDepositorEntrySubstate.md) @@ -107,18 +106,20 @@ Class | Method | HTTP request | Description - [ActiveValidatorIndex](docs/ActiveValidatorIndex.md) - [ActiveValidatorKey](docs/ActiveValidatorKey.md) - [AddressType](docs/AddressType.md) - - [AllOfAccessRuleNode](docs/AllOfAccessRuleNode.md) - - [AllOfProofRule](docs/AllOfProofRule.md) + - [AllOfBasicRequirement](docs/AllOfBasicRequirement.md) + - [AllOfCompositeRequirement](docs/AllOfCompositeRequirement.md) - [AlwaysVisibleGlobalNodesVersion](docs/AlwaysVisibleGlobalNodesVersion.md) - - [AmountOfProofRule](docs/AmountOfProofRule.md) - - [AnyOfAccessRuleNode](docs/AnyOfAccessRuleNode.md) - - [AnyOfProofRule](docs/AnyOfProofRule.md) + - [AmountOfBasicRequirement](docs/AmountOfBasicRequirement.md) + - [AnyOfBasicRequirement](docs/AnyOfBasicRequirement.md) + - [AnyOfCompositeRequirement](docs/AnyOfCompositeRequirement.md) - [AttachedModuleId](docs/AttachedModuleId.md) - [AuthConfig](docs/AuthConfig.md) - [AuthorizedDepositorBadge](docs/AuthorizedDepositorBadge.md) - [AuthorizedDepositorBadgeType](docs/AuthorizedDepositorBadgeType.md) - [AuthorizedDepositorKey](docs/AuthorizedDepositorKey.md) - [BasicErrorResponse](docs/BasicErrorResponse.md) + - [BasicRequirement](docs/BasicRequirement.md) + - [BasicRequirementType](docs/BasicRequirementType.md) - [BinaryPlaintextMessageContent](docs/BinaryPlaintextMessageContent.md) - [BlueprintCollectionSchema](docs/BlueprintCollectionSchema.md) - [BlueprintCollectionSchemaType](docs/BlueprintCollectionSchemaType.md) @@ -149,7 +150,10 @@ Class | Method | HTTP request | Description - [CommittedStateIdentifier](docs/CommittedStateIdentifier.md) - [CommittedTransaction](docs/CommittedTransaction.md) - [CommittedTransactionBalanceChanges](docs/CommittedTransactionBalanceChanges.md) + - [CompiledPreviewTransaction](docs/CompiledPreviewTransaction.md) - [ComponentMethodTargetIdentifier](docs/ComponentMethodTargetIdentifier.md) + - [CompositeRequirement](docs/CompositeRequirement.md) + - [CompositeRequirementType](docs/CompositeRequirementType.md) - [ConsensusLedgerProofOrigin](docs/ConsensusLedgerProofOrigin.md) - [ConsensusManagerFieldConfigSubstate](docs/ConsensusManagerFieldConfigSubstate.md) - [ConsensusManagerFieldConfigValue](docs/ConsensusManagerFieldConfigValue.md) @@ -169,7 +173,7 @@ Class | Method | HTTP request | Description - [ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue](docs/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.md) - [CostingModuleConfig](docs/CostingModuleConfig.md) - [CostingParameters](docs/CostingParameters.md) - - [CountOfProofRule](docs/CountOfProofRule.md) + - [CountOfBasicRequirement](docs/CountOfBasicRequirement.md) - [CreatedSubstate](docs/CreatedSubstate.md) - [DataStruct](docs/DataStruct.md) - [DefaultDepositRule](docs/DefaultDepositRule.md) @@ -245,6 +249,7 @@ Class | Method | HTTP request | Description - [IntentCoreV2](docs/IntentCoreV2.md) - [IntentHeaderV2](docs/IntentHeaderV2.md) - [IntentSignatures](docs/IntentSignatures.md) + - [InvalidTransactionPreviewV2ErrorDetails](docs/InvalidTransactionPreviewV2ErrorDetails.md) - [KeyValueBasedStructure](docs/KeyValueBasedStructure.md) - [KeyValueBlueprintCollectionSchema](docs/KeyValueBlueprintCollectionSchema.md) - [KeyValueStoreEntryStructure](docs/KeyValueStoreEntryStructure.md) @@ -302,6 +307,7 @@ Class | Method | HTTP request | Description - [LtsTransactionSubmitRequest](docs/LtsTransactionSubmitRequest.md) - [LtsTransactionSubmitResponse](docs/LtsTransactionSubmitResponse.md) - [MainMethodKey](docs/MainMethodKey.md) + - [ManifestValidationRuleset](docs/ManifestValidationRuleset.md) - [MapSubstateKey](docs/MapSubstateKey.md) - [MempoolListRequest](docs/MempoolListRequest.md) - [MempoolListResponse](docs/MempoolListResponse.md) @@ -309,6 +315,7 @@ Class | Method | HTTP request | Description - [MempoolTransactionRequest](docs/MempoolTransactionRequest.md) - [MempoolTransactionResponse](docs/MempoolTransactionResponse.md) - [MempoolTransactionResponsePayloadsInner](docs/MempoolTransactionResponsePayloadsInner.md) + - [MessageValidationConfig](docs/MessageValidationConfig.md) - [MetadataKey](docs/MetadataKey.md) - [MetadataModuleEntrySubstate](docs/MetadataModuleEntrySubstate.md) - [MetadataModuleEntryValue](docs/MetadataModuleEntryValue.md) @@ -404,12 +411,14 @@ Class | Method | HTTP request | Description - [PlaintextMessageContentType](docs/PlaintextMessageContentType.md) - [PlaintextTransactionMessage](docs/PlaintextTransactionMessage.md) - [PoolVault](docs/PoolVault.md) + - [PreparationSettings](docs/PreparationSettings.md) - [PresentedBadge](docs/PresentedBadge.md) - [PresentedBadgeType](docs/PresentedBadgeType.md) + - [PreviewFlags](docs/PreviewFlags.md) + - [PreviewTransaction](docs/PreviewTransaction.md) + - [PreviewTransactionType](docs/PreviewTransactionType.md) - [PrimaryRoleRecoveryAttempt](docs/PrimaryRoleRecoveryAttempt.md) - - [ProofAccessRuleNode](docs/ProofAccessRuleNode.md) - - [ProofRule](docs/ProofRule.md) - - [ProofRuleType](docs/ProofRuleType.md) + - [ProofRuleCompositeRequirement](docs/ProofRuleCompositeRequirement.md) - [ProposerReward](docs/ProposerReward.md) - [ProtectedAccessRule](docs/ProtectedAccessRule.md) - [ProtocolUpdateLedgerProofOrigin](docs/ProtocolUpdateLedgerProofOrigin.md) @@ -426,7 +435,7 @@ Class | Method | HTTP request | Description - [ReferenceType](docs/ReferenceType.md) - [RemoteGenericSubstitution](docs/RemoteGenericSubstitution.md) - [RequestedStateVersionOutOfBoundsErrorDetails](docs/RequestedStateVersionOutOfBoundsErrorDetails.md) - - [RequireProofRule](docs/RequireProofRule.md) + - [RequireBasicRequirement](docs/RequireBasicRequirement.md) - [Requirement](docs/Requirement.md) - [RequirementType](docs/RequirementType.md) - [ResourceAmount](docs/ResourceAmount.md) @@ -548,10 +557,15 @@ Class | Method | HTTP request | Description - [TransactionPayloadDetails](docs/TransactionPayloadDetails.md) - [TransactionPayloadStatus](docs/TransactionPayloadStatus.md) - [TransactionPreviewRequest](docs/TransactionPreviewRequest.md) - - [TransactionPreviewRequestFlags](docs/TransactionPreviewRequestFlags.md) - [TransactionPreviewResponse](docs/TransactionPreviewResponse.md) - [TransactionPreviewResponseLogsInner](docs/TransactionPreviewResponseLogsInner.md) - [TransactionPreviewResponseOptions](docs/TransactionPreviewResponseOptions.md) + - [TransactionPreviewV2ErrorDetails](docs/TransactionPreviewV2ErrorDetails.md) + - [TransactionPreviewV2ErrorDetailsType](docs/TransactionPreviewV2ErrorDetailsType.md) + - [TransactionPreviewV2ErrorResponse](docs/TransactionPreviewV2ErrorResponse.md) + - [TransactionPreviewV2Request](docs/TransactionPreviewV2Request.md) + - [TransactionPreviewV2Response](docs/TransactionPreviewV2Response.md) + - [TransactionPreviewV2ResponseOptions](docs/TransactionPreviewV2ResponseOptions.md) - [TransactionReceipt](docs/TransactionReceipt.md) - [TransactionReceiptRequest](docs/TransactionReceiptRequest.md) - [TransactionReceiptResponse](docs/TransactionReceiptResponse.md) @@ -571,6 +585,7 @@ Class | Method | HTTP request | Description - [TransactionTrackerFieldStateSubstate](docs/TransactionTrackerFieldStateSubstate.md) - [TransactionTrackerFieldStateValue](docs/TransactionTrackerFieldStateValue.md) - [TransactionTrackerTransactionStatus](docs/TransactionTrackerTransactionStatus.md) + - [TransactionValidationConfig](docs/TransactionValidationConfig.md) - [TwoResourcePoolFieldStateSubstate](docs/TwoResourcePoolFieldStateSubstate.md) - [TwoResourcePoolFieldStateValue](docs/TwoResourcePoolFieldStateValue.md) - [TypeInfoDetails](docs/TypeInfoDetails.md) diff --git a/generated-clients/core-api-client/async-client/docs/AnyOfProofRule.md b/generated-clients/core-api-client/async-client/docs/AllOfBasicRequirement.md similarity index 93% rename from generated-clients/core-api-client/async-client/docs/AnyOfProofRule.md rename to generated-clients/core-api-client/async-client/docs/AllOfBasicRequirement.md index 3638041..46ee379 100644 --- a/generated-clients/core-api-client/async-client/docs/AnyOfProofRule.md +++ b/generated-clients/core-api-client/async-client/docs/AllOfBasicRequirement.md @@ -1,4 +1,4 @@ -# AnyOfProofRule +# AllOfBasicRequirement ## Properties diff --git a/generated-clients/core-api-client/async-client/docs/AllOfCompositeRequirement.md b/generated-clients/core-api-client/async-client/docs/AllOfCompositeRequirement.md new file mode 100644 index 0000000..2fafd2f --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/AllOfCompositeRequirement.md @@ -0,0 +1,11 @@ +# AllOfCompositeRequirement + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**access_rules** | [**Vec**](CompositeRequirement.md) | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/AmountOfProofRule.md b/generated-clients/core-api-client/async-client/docs/AmountOfBasicRequirement.md similarity index 93% rename from generated-clients/core-api-client/async-client/docs/AmountOfProofRule.md rename to generated-clients/core-api-client/async-client/docs/AmountOfBasicRequirement.md index ab7ccf8..87a5039 100644 --- a/generated-clients/core-api-client/async-client/docs/AmountOfProofRule.md +++ b/generated-clients/core-api-client/async-client/docs/AmountOfBasicRequirement.md @@ -1,4 +1,4 @@ -# AmountOfProofRule +# AmountOfBasicRequirement ## Properties diff --git a/generated-clients/core-api-client/sync-client/docs/AnyOfProofRule.md b/generated-clients/core-api-client/async-client/docs/AnyOfBasicRequirement.md similarity index 93% rename from generated-clients/core-api-client/sync-client/docs/AnyOfProofRule.md rename to generated-clients/core-api-client/async-client/docs/AnyOfBasicRequirement.md index 3638041..a3df737 100644 --- a/generated-clients/core-api-client/sync-client/docs/AnyOfProofRule.md +++ b/generated-clients/core-api-client/async-client/docs/AnyOfBasicRequirement.md @@ -1,4 +1,4 @@ -# AnyOfProofRule +# AnyOfBasicRequirement ## Properties diff --git a/generated-clients/core-api-client/async-client/docs/AnyOfCompositeRequirement.md b/generated-clients/core-api-client/async-client/docs/AnyOfCompositeRequirement.md new file mode 100644 index 0000000..4e0c336 --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/AnyOfCompositeRequirement.md @@ -0,0 +1,11 @@ +# AnyOfCompositeRequirement + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**access_rules** | [**Vec**](CompositeRequirement.md) | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/AccessRuleNode.md b/generated-clients/core-api-client/async-client/docs/BasicRequirement.md similarity index 91% rename from generated-clients/core-api-client/async-client/docs/AccessRuleNode.md rename to generated-clients/core-api-client/async-client/docs/BasicRequirement.md index 1def3a2..7a31d59 100644 --- a/generated-clients/core-api-client/async-client/docs/AccessRuleNode.md +++ b/generated-clients/core-api-client/async-client/docs/BasicRequirement.md @@ -1,4 +1,4 @@ -# AccessRuleNode +# BasicRequirement ## Enum Variants diff --git a/generated-clients/core-api-client/sync-client/docs/ProofRuleType.md b/generated-clients/core-api-client/async-client/docs/BasicRequirementType.md similarity index 93% rename from generated-clients/core-api-client/sync-client/docs/ProofRuleType.md rename to generated-clients/core-api-client/async-client/docs/BasicRequirementType.md index 5599976..82d05f9 100644 --- a/generated-clients/core-api-client/sync-client/docs/ProofRuleType.md +++ b/generated-clients/core-api-client/async-client/docs/BasicRequirementType.md @@ -1,4 +1,4 @@ -# ProofRuleType +# BasicRequirementType ## Enum Variants diff --git a/generated-clients/core-api-client/async-client/docs/BootLoaderModuleFieldTransactionValidationConfigurationSubstate.md b/generated-clients/core-api-client/async-client/docs/BootLoaderModuleFieldTransactionValidationConfigurationSubstate.md index 30e151e..780ecce 100644 --- a/generated-clients/core-api-client/async-client/docs/BootLoaderModuleFieldTransactionValidationConfigurationSubstate.md +++ b/generated-clients/core-api-client/async-client/docs/BootLoaderModuleFieldTransactionValidationConfigurationSubstate.md @@ -4,6 +4,7 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- +**config** | [**models::TransactionValidationConfig**](TransactionValidationConfig.md) | | **is_locked** | **bool** | | [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/async-client/docs/CompiledPreviewTransaction.md b/generated-clients/core-api-client/async-client/docs/CompiledPreviewTransaction.md new file mode 100644 index 0000000..dd1218f --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/CompiledPreviewTransaction.md @@ -0,0 +1,11 @@ +# CompiledPreviewTransaction + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**preview_transaction_hex** | **String** | A hex-encoded, compiled `RawPreviewTransaction`. As of Cuttlefish, only `PreviewTransactionV2` is supported. A `PreviewTransactionV2` can be created with a v2 transaction builder: * If using Rust, it can be created with a `TransactionV2Builder` using `build_preview_transaction()` and then converted to hex with `preview_transaction.to_raw().unwrap().to_hex()` * If using the toolkit, you can create this using the v2 transaction builder. Some subtleties: * Partial transactions can't be previewed. Instead, they must be wrapped inside a transaction wrapper, so that the engine knows how to yield to them appropriately. * Currently the builder assumes that the signed partial transactions have real signatures. This isn't strictly required, and we may create a builder in future which allows providing public keys when building partial transactions for use in preview. * If you don't have signatures to hand, you can simply not sign the partial transactions, and then use the `assume_all_signature_proofs` preview flag, although be advised that this may result in the fee estimate being slightly lower during preview. * We may create more ergonomic builders for PreviewTransactions which allow use of public keys to denote the signers of subintents. Let us know if this is important for your use case. | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/CompositeRequirement.md b/generated-clients/core-api-client/async-client/docs/CompositeRequirement.md new file mode 100644 index 0000000..67d649d --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/CompositeRequirement.md @@ -0,0 +1,10 @@ +# CompositeRequirement + +## Enum Variants + +| Name | Value | +|---- | -----| + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/AccessRuleNodeType.md b/generated-clients/core-api-client/async-client/docs/CompositeRequirementType.md similarity index 91% rename from generated-clients/core-api-client/sync-client/docs/AccessRuleNodeType.md rename to generated-clients/core-api-client/async-client/docs/CompositeRequirementType.md index ee21c81..557b5fb 100644 --- a/generated-clients/core-api-client/sync-client/docs/AccessRuleNodeType.md +++ b/generated-clients/core-api-client/async-client/docs/CompositeRequirementType.md @@ -1,4 +1,4 @@ -# AccessRuleNodeType +# CompositeRequirementType ## Enum Variants diff --git a/generated-clients/core-api-client/async-client/docs/CostingParameters.md b/generated-clients/core-api-client/async-client/docs/CostingParameters.md index 8f7c149..035c650 100644 --- a/generated-clients/core-api-client/async-client/docs/CostingParameters.md +++ b/generated-clients/core-api-client/async-client/docs/CostingParameters.md @@ -9,7 +9,8 @@ Name | Type | Description | Notes **execution_cost_unit_price** | **String** | The string-encoded decimal representing the XRD price of a single cost unit of transaction execution. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. | **finalization_cost_unit_limit** | **u64** | An integer between `0` and `2^32 - 1`, representing the maximum amount of cost units available for the transaction finalization. | **finalization_cost_unit_price** | **String** | The string-encoded decimal representing the XRD price of a single cost unit of transaction finalization. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. | -**tip_percentage** | **u32** | An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to 1% of the fee. | +**tip_percentage** | **u32** | NOTE: V2 transactions specify the tip in basis points, which gets rounded down for this `tip_percentage` field. It is recommended to instead use the `tip_proportion` field to get a fully accurate value. An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to 1% of the fee. | +**tip_proportion** | Option<**String**> | A string-encoded decimal, giving the validator tip as a proportional amount. A value of `\"0.01\"` corresponds to 1% of the fee being paid as a tip. NOTE: This field is not marked as required for Cuttlefish launch, to permit cuttlefish clients to talk to pre-cuttlefish nodes. This can be changed after Cuttlefish enactment once all nodes are on Cuttlefish. | [optional] **xrd_archive_storage_price** | **String** | The string-encoded decimal representing the price of 1 byte of archive storage, expressed in XRD. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. | **xrd_storage_price** | **String** | The string-encoded decimal representing the price of 1 byte of state storage, expressed in XRD. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. | **xrd_usd_price** | **String** | The string-encoded decimal representing what amount of XRD is consumed by a Royalty of 1 USD. This is fixed for a given protocol version, so is not an accurate representation of the XRD price. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. | diff --git a/generated-clients/core-api-client/sync-client/docs/CountOfProofRule.md b/generated-clients/core-api-client/async-client/docs/CountOfBasicRequirement.md similarity index 93% rename from generated-clients/core-api-client/sync-client/docs/CountOfProofRule.md rename to generated-clients/core-api-client/async-client/docs/CountOfBasicRequirement.md index 33e8018..499ae6d 100644 --- a/generated-clients/core-api-client/sync-client/docs/CountOfProofRule.md +++ b/generated-clients/core-api-client/async-client/docs/CountOfBasicRequirement.md @@ -1,4 +1,4 @@ -# CountOfProofRule +# CountOfBasicRequirement ## Properties diff --git a/generated-clients/core-api-client/async-client/docs/ErrorResponseType.md b/generated-clients/core-api-client/async-client/docs/ErrorResponseType.md index 8972e62..00508c4 100644 --- a/generated-clients/core-api-client/async-client/docs/ErrorResponseType.md +++ b/generated-clients/core-api-client/async-client/docs/ErrorResponseType.md @@ -7,6 +7,7 @@ | Basic | Basic | | TransactionSubmit | TransactionSubmit | | LtsTransactionSubmit | LtsTransactionSubmit | +| TransactionPreviewV2 | TransactionPreviewV2 | | StreamTransactions | StreamTransactions | | StreamProofs | StreamProofs | diff --git a/generated-clients/core-api-client/async-client/docs/InvalidTransactionPreviewV2ErrorDetails.md b/generated-clients/core-api-client/async-client/docs/InvalidTransactionPreviewV2ErrorDetails.md new file mode 100644 index 0000000..c55e383 --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/InvalidTransactionPreviewV2ErrorDetails.md @@ -0,0 +1,11 @@ +# InvalidTransactionPreviewV2ErrorDetails + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**validation_error** | **String** | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.md b/generated-clients/core-api-client/async-client/docs/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.md index 29b3ebf..1b0f399 100644 --- a/generated-clients/core-api-client/async-client/docs/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.md +++ b/generated-clients/core-api-client/async-client/docs/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.md @@ -4,8 +4,10 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- -**min_tip_percentage_required** | Option<**u32**> | A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] -**tip_percentage** | **u32** | Tip percentage of the submitted (and rejected) transaction. | +**min_tip_percentage_required** | Option<**u32**> | NOTE: This is kept for backwards compatibility, but we recommend using `min_tip_proportion_required` instead. A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] +**min_tip_proportion_required** | Option<**String**> | A lower bound for tip proportion at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] +**tip_percentage** | **u32** | NOTE: This is kept for backwards compatibility, but we recommend using `tip_proportion` instead. Tip percentage of the submitted (and rejected) transaction. For V2 transactions specifying basis point tips, the amount is rounded down. | +**tip_proportion** | Option<**String**> | The string-encoded decimal tip proportion of the submitted (and rejected) transaction. This field will always be present on Cuttlefish nodes, but is marked as not-required for Cuttlefish launch, to avoid a dependency on clients to update after the node is updated. | [optional] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/async-client/docs/ManifestValidationRuleset.md b/generated-clients/core-api-client/async-client/docs/ManifestValidationRuleset.md new file mode 100644 index 0000000..ae51f3e --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/ManifestValidationRuleset.md @@ -0,0 +1,13 @@ +# ManifestValidationRuleset + +## Enum Variants + +| Name | Value | +|---- | -----| +| Basic | Basic | +| Cuttlefish | Cuttlefish | + + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/MessageValidationConfig.md b/generated-clients/core-api-client/async-client/docs/MessageValidationConfig.md new file mode 100644 index 0000000..a14efcc --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/MessageValidationConfig.md @@ -0,0 +1,14 @@ +# MessageValidationConfig + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**max_decryptors** | **String** | | +**max_encrypted_message_length** | **String** | | +**max_mime_type_length** | **String** | | +**max_plaintext_message_length** | **String** | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/NetworkConfigurationResponseWellKnownAddresses.md b/generated-clients/core-api-client/async-client/docs/NetworkConfigurationResponseWellKnownAddresses.md index 84226e3..ebf3eaf 100644 --- a/generated-clients/core-api-client/async-client/docs/NetworkConfigurationResponseWellKnownAddresses.md +++ b/generated-clients/core-api-client/async-client/docs/NetworkConfigurationResponseWellKnownAddresses.md @@ -28,8 +28,10 @@ Name | Type | Description | Notes **royalty_module_package** | **String** | | **secp256k1_signature_virtual_badge** | **String** | | **system_transaction_badge** | **String** | | +**test_utils_package** | Option<**String**> | | [optional] **transaction_processor_package** | **String** | | **transaction_tracker** | **String** | | +**transaction_tracker_package** | Option<**String**> | | [optional] **validator_owner_badge** | **String** | | **xrd** | **String** | | diff --git a/generated-clients/core-api-client/async-client/docs/NetworkStatusResponse.md b/generated-clients/core-api-client/async-client/docs/NetworkStatusResponse.md index 20d557c..4a758c1 100644 --- a/generated-clients/core-api-client/async-client/docs/NetworkStatusResponse.md +++ b/generated-clients/core-api-client/async-client/docs/NetworkStatusResponse.md @@ -6,7 +6,7 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **current_epoch_round** | Option<[**models::EpochRound**](EpochRound.md)> | The current epoch and round of the ledger. It is not present until genesis has been run. | [optional] **current_protocol_version** | **String** | A descriptor for the current protocol version that the node is running. | -**current_state_identifier** | Option<[**models::CommittedStateIdentifier**](CommittedStateIdentifier.md)> | The current state identifier at the top of the node's copy of the ledger (ie as of the latest committed transaction). It is not present until genesis has been run. | [optional] +**current_state_identifier** | [**models::CommittedStateIdentifier**](CommittedStateIdentifier.md) | The current state identifier at the top of the node's copy of the ledger (i.e. as of the latest committed transaction). | **genesis_epoch_round** | Option<[**models::EpochRound**](EpochRound.md)> | The epoch details for the genesis epoch and round. The genesis epoch will be the last Olympia epoch + 1, and have a \"fake\" round-number 1 (because there is no round for the genesis transaction). In the Gateway, this can be used for the epoch and round number before the first RoundUpdate transaction. It is not present until genesis has been run. | [optional] **post_genesis_epoch_round** | Option<[**models::EpochRound**](EpochRound.md)> | The post-genesis epoch and round. | [optional] **post_genesis_state_identifier** | Option<[**models::CommittedStateIdentifier**](CommittedStateIdentifier.md)> | The ledger state after the genesis transactions have been executed. It is not present until genesis has been run. | [optional] diff --git a/generated-clients/core-api-client/async-client/docs/PreparationSettings.md b/generated-clients/core-api-client/async-client/docs/PreparationSettings.md new file mode 100644 index 0000000..73653f6 --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/PreparationSettings.md @@ -0,0 +1,16 @@ +# PreparationSettings + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**max_blobs** | **String** | | +**max_child_subintents_per_intent** | **String** | | +**max_ledger_payload_length** | **String** | | +**max_subintents_per_transaction** | **String** | | +**max_user_payload_length** | **String** | | +**v2_transactions_permitted** | **bool** | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/PreviewFlags.md b/generated-clients/core-api-client/async-client/docs/PreviewFlags.md new file mode 100644 index 0000000..0757dd5 --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/PreviewFlags.md @@ -0,0 +1,14 @@ +# PreviewFlags + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**assume_all_signature_proofs** | Option<**bool**> | If enabled, each manifest processor's auth zone will be given a simulated proof of every signature, which can be used to pass signature access rules. This can be used to preview transactions even if the required signatures are not known ahead of time. See the documentation on [advanced access rules](https://docs.radixdlt.com/docs/advanced-accessrules#signature-requirements) for more information. | [optional] +**disable_auth_checks** | Option<**bool**> | If enabled, all authorization checks are skipped during execution. This could be used to e.g.: * Preview protocol update style transactions. * Mint resources for previewing trades with resources you don't own. If doing this, be warned: only resources which were potentially mintable/burnable at creation time will be mintable/burnable, due to feature flags on the resource. Warning: this mode of operation is quite a departure from normal operation: * Calculated fees will likely be lower than a standard execution. * This mode can subtly break invariants some dApp code might rely on, or result in unexpected behaviour, so the execution result might not be valid for your needs. For example, if this flag was used to mint pool units to preview a redemption (or some dApp interaction which behind the scenes redeemed them), they'd redeem for less than they're currently worth, because the blueprint code relies on the total supply of the pool units to calculate their redemption worth, and you've just inflated the total supply through the mint operation. | [optional] +**skip_epoch_check** | Option<**bool**> | If enabled, the various runtime epoch-related verifications are skipped: - The `start_epoch_inclusive` and `end_epoch_exclusive` parameters, if specified, are ignored. - The duplicate intent checks (which rely on the expiry epoch) are also ignored. However, if the start and end epoch are provided, they must still be statically valid. We recommend using a value of `start_epoch_inclusive = 1` and `end_epoch_exclusive = 2` in this case. | [optional] +**use_free_credit** | Option<**bool**> | If enabled, a large simulated pool of XRD is marked as locked. This mode can be used to estimate fees. To get a reliable estimate, we recommend that your transaction is as close as possible to the real transaction. For example: - You should still use a lock fee command, but you can set it to lock a fee of 0. - You should include the public keys that will sign the transaction, so the cost of signature verification and payload size can be accounted for. | [optional] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/ProofRule.md b/generated-clients/core-api-client/async-client/docs/PreviewTransaction.md similarity index 91% rename from generated-clients/core-api-client/async-client/docs/ProofRule.md rename to generated-clients/core-api-client/async-client/docs/PreviewTransaction.md index 69d81e0..e26eb83 100644 --- a/generated-clients/core-api-client/async-client/docs/ProofRule.md +++ b/generated-clients/core-api-client/async-client/docs/PreviewTransaction.md @@ -1,4 +1,4 @@ -# ProofRule +# PreviewTransaction ## Enum Variants diff --git a/generated-clients/core-api-client/async-client/docs/PreviewTransactionType.md b/generated-clients/core-api-client/async-client/docs/PreviewTransactionType.md new file mode 100644 index 0000000..1eb0a0b --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/PreviewTransactionType.md @@ -0,0 +1,12 @@ +# PreviewTransactionType + +## Enum Variants + +| Name | Value | +|---- | -----| +| Compiled | Compiled | + + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/ProofAccessRuleNode.md b/generated-clients/core-api-client/async-client/docs/ProofAccessRuleNode.md deleted file mode 100644 index 8c97498..0000000 --- a/generated-clients/core-api-client/async-client/docs/ProofAccessRuleNode.md +++ /dev/null @@ -1,11 +0,0 @@ -# ProofAccessRuleNode - -## Properties - -Name | Type | Description | Notes ------------- | ------------- | ------------- | ------------- -**proof_rule** | [**models::ProofRule**](ProofRule.md) | | - -[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) - - diff --git a/generated-clients/core-api-client/async-client/docs/AnyOfAccessRuleNode.md b/generated-clients/core-api-client/async-client/docs/ProofRuleCompositeRequirement.md similarity index 72% rename from generated-clients/core-api-client/async-client/docs/AnyOfAccessRuleNode.md rename to generated-clients/core-api-client/async-client/docs/ProofRuleCompositeRequirement.md index 3ad23c0..4797af8 100644 --- a/generated-clients/core-api-client/async-client/docs/AnyOfAccessRuleNode.md +++ b/generated-clients/core-api-client/async-client/docs/ProofRuleCompositeRequirement.md @@ -1,10 +1,10 @@ -# AnyOfAccessRuleNode +# ProofRuleCompositeRequirement ## Properties Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- -**access_rules** | [**Vec**](AccessRuleNode.md) | | +**proof_rule** | [**models::BasicRequirement**](BasicRequirement.md) | | [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/async-client/docs/ProtectedAccessRule.md b/generated-clients/core-api-client/async-client/docs/ProtectedAccessRule.md index 9bd76fc..1a6ea16 100644 --- a/generated-clients/core-api-client/async-client/docs/ProtectedAccessRule.md +++ b/generated-clients/core-api-client/async-client/docs/ProtectedAccessRule.md @@ -4,7 +4,7 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- -**access_rule** | [**models::AccessRuleNode**](AccessRuleNode.md) | | +**access_rule** | [**models::CompositeRequirement**](CompositeRequirement.md) | | [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/sync-client/docs/RequireProofRule.md b/generated-clients/core-api-client/async-client/docs/RequireBasicRequirement.md similarity index 92% rename from generated-clients/core-api-client/sync-client/docs/RequireProofRule.md rename to generated-clients/core-api-client/async-client/docs/RequireBasicRequirement.md index 6ca08d7..d1ab006 100644 --- a/generated-clients/core-api-client/sync-client/docs/RequireProofRule.md +++ b/generated-clients/core-api-client/async-client/docs/RequireBasicRequirement.md @@ -1,4 +1,4 @@ -# RequireProofRule +# RequireBasicRequirement ## Properties diff --git a/generated-clients/core-api-client/async-client/docs/SystemVersion.md b/generated-clients/core-api-client/async-client/docs/SystemVersion.md index 7a4daf2..7b51a7d 100644 --- a/generated-clients/core-api-client/async-client/docs/SystemVersion.md +++ b/generated-clients/core-api-client/async-client/docs/SystemVersion.md @@ -6,6 +6,7 @@ |---- | -----| | V1 | V1 | | V2 | V2 | +| V3 | V3 | [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/async-client/docs/TransactionApi.md b/generated-clients/core-api-client/async-client/docs/TransactionApi.md index 3b367cc..70b7e26 100644 --- a/generated-clients/core-api-client/async-client/docs/TransactionApi.md +++ b/generated-clients/core-api-client/async-client/docs/TransactionApi.md @@ -6,7 +6,8 @@ Method | HTTP request | Description ------------- | ------------- | ------------- [**transaction_call_preview_post**](TransactionApi.md#transaction_call_preview_post) | **POST** /transaction/call-preview | Scrypto Call Preview [**transaction_parse_post**](TransactionApi.md#transaction_parse_post) | **POST** /transaction/parse | Parse Transaction Payload -[**transaction_preview_post**](TransactionApi.md#transaction_preview_post) | **POST** /transaction/preview | Transaction Preview +[**transaction_preview_post**](TransactionApi.md#transaction_preview_post) | **POST** /transaction/preview | Transaction Preview V1 +[**transaction_preview_v2_post**](TransactionApi.md#transaction_preview_v2_post) | **POST** /transaction/preview-v2 | Transaction Preview V2 [**transaction_receipt_post**](TransactionApi.md#transaction_receipt_post) | **POST** /transaction/receipt | Get Transaction Receipt [**transaction_status_post**](TransactionApi.md#transaction_status_post) | **POST** /transaction/status | Get Transaction Status [**transaction_submit_post**](TransactionApi.md#transaction_submit_post) | **POST** /transaction/submit | Transaction Submit @@ -76,9 +77,9 @@ No authorization required ## transaction_preview_post > models::TransactionPreviewResponse transaction_preview_post(transaction_preview_request) -Transaction Preview +Transaction Preview V1 -Preview a transaction against the latest network state, and returns the preview receipt. +Preview a transaction against the latest network state, and returns the preview receipt. If the node has enabled it, you may be able to also preview against recent network state. For V2 transactions (and beyond) the `/preview-v2` endpoint should be used instead. ### Parameters @@ -103,6 +104,36 @@ No authorization required [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) +## transaction_preview_v2_post + +> models::TransactionPreviewV2Response transaction_preview_v2_post(transaction_preview_v2_request) +Transaction Preview V2 + +Previews a transaction against the latest network state, and returns the preview receipt. If the node has enabled it, you may be able to also preview against recent network state. This endpoint supports V2 transactions (and beyond). If you still need to preview V1 transactions, you should use the `/preview` endpoint instead. + +### Parameters + + +Name | Type | Description | Required | Notes +------------- | ------------- | ------------- | ------------- | ------------- +**transaction_preview_v2_request** | [**TransactionPreviewV2Request**](TransactionPreviewV2Request.md) | | [required] | + +### Return type + +[**models::TransactionPreviewV2Response**](TransactionPreviewV2Response.md) + +### Authorization + +No authorization required + +### HTTP request headers + +- **Content-Type**: application/json +- **Accept**: application/json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + + ## transaction_receipt_post > models::TransactionReceiptResponse transaction_receipt_post(transaction_receipt_request) diff --git a/generated-clients/core-api-client/async-client/docs/TransactionPreviewRequest.md b/generated-clients/core-api-client/async-client/docs/TransactionPreviewRequest.md index 27e8406..25a66bf 100644 --- a/generated-clients/core-api-client/async-client/docs/TransactionPreviewRequest.md +++ b/generated-clients/core-api-client/async-client/docs/TransactionPreviewRequest.md @@ -6,18 +6,18 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **at_ledger_state** | Option<[**models::LedgerStateSelector**](LedgerStateSelector.md)> | | [optional] **blobs_hex** | Option<**Vec**> | An array of hex-encoded blob data, if referenced by the manifest. | [optional] -**end_epoch_exclusive** | Option<**u64**> | An integer between `0` and `10^10`, marking the epoch at which the transaction is no longer valid. If omitted, a maximum epoch (relative to the `start_epoch_inclusive`) will be used. | [optional] -**flags** | [**models::TransactionPreviewRequestFlags**](TransactionPreviewRequest_flags.md) | | +**end_epoch_exclusive** | Option<**u64**> | An integer between `0` and `10^10`, marking the epoch at which the transaction is no longer valid. If not provided, a maximum epoch (relative to the `start_epoch_inclusive`) will be used. | [optional] +**flags** | Option<[**models::PreviewFlags**](PreviewFlags.md)> | | [optional] **manifest** | **String** | A text representation of a transaction manifest. | **message** | Option<[**models::TransactionMessage**](TransactionMessage.md)> | An optional transaction message. Only affects the costing. | [optional] **network** | **String** | The logical name of the network | -**nonce** | **u64** | An integer between `0` and `2^32 - 1`, chosen to allow a unique intent to be created (to enable submitting an otherwise identical/duplicate intent). | -**notary_is_signatory** | Option<**bool**> | Whether the notary should count as a signatory (defaults to `false`). | [optional] -**notary_public_key** | Option<[**models::PublicKey**](PublicKey.md)> | The notary public key to use (optional). | [optional] -**options** | Option<[**models::TransactionPreviewResponseOptions**](TransactionPreviewResponseOptions.md)> | A set of flags to configure the response of the transaction preview. | [optional] -**signer_public_keys** | [**Vec**](PublicKey.md) | A list of public keys to be used as transaction signers | -**start_epoch_inclusive** | Option<**u64**> | An integer between `0` and `10^10`, marking the epoch at which the transaction starts being valid. If omitted, the current epoch will be used (taking into account the `at_ledger_state`, if specified). | [optional] -**tip_percentage** | **u32** | An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to a 1% fee. | +**nonce** | Option<**u64**> | An integer between `0` and `2^32 - 1`, chosen to allow a unique intent to be created (to enable submitting an otherwise identical/duplicate intent). If not provided, this defaults to 0. | [optional] +**notary_is_signatory** | Option<**bool**> | Whether the notary should be used as a signer (optional). If not provided, this defaults to false. | [optional] +**notary_public_key** | Option<[**models::PublicKey**](PublicKey.md)> | The notary public key to use. If not provided, this defaults to a fixed public key. | [optional] +**options** | Option<[**models::TransactionPreviewResponseOptions**](TransactionPreviewResponseOptions.md)> | | [optional] +**signer_public_keys** | Option<[**Vec**](PublicKey.md)> | A list of public keys to be used as transaction signers. If not provided, this defaults to an empty array. | [optional] +**start_epoch_inclusive** | Option<**u64**> | An integer between `0` and `10^10`, marking the epoch at which the transaction starts being valid. If not provided, the current epoch will be used (taking into account the `at_ledger_state`, if specified). | [optional] +**tip_percentage** | Option<**u32**> | An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to a 1% fee. If not provided, this defaults to 0. | [optional] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/async-client/docs/TransactionPreviewRequestFlags.md b/generated-clients/core-api-client/async-client/docs/TransactionPreviewRequestFlags.md deleted file mode 100644 index 942a720..0000000 --- a/generated-clients/core-api-client/async-client/docs/TransactionPreviewRequestFlags.md +++ /dev/null @@ -1,14 +0,0 @@ -# TransactionPreviewRequestFlags - -## Properties - -Name | Type | Description | Notes ------------- | ------------- | ------------- | ------------- -**assume_all_signature_proofs** | **bool** | Whether the virtual signature proofs should be automatically placed in the auth zone. | -**disable_auth_checks** | Option<**bool**> | Whether to skip the auth checks during execution. This could be used to e.g.: * Preview protocol update style transactions. * Mint resources for previewing trades with resources you don't own. If doing this, be warned: * Only resources which were potentially mintable/burnable at creation time will be mintable/burnable, due to feature flags on the resource. * Please see the below warning about unexpected results if using this approach. Warning: this mode of operation is quite a departure from normal operation: * Calculated fees will likely be lower than a standard execution. * This mode can subtly break invariants some dApp code might rely on, or result in unexpected behaviour, so the resulting execution result might not be valid for your needs. For example, if I used this flag to mint pool units to preview a redemption (or some dApp interaction which behind the scenes redeemed them), they'd redeem for less than they're currently worth, because the blueprint code relies on the total supply of the pool units to calculate their redemption worth, and you've just inflated the total supply through the mint operation. | [optional] -**skip_epoch_check** | **bool** | Whether to skip the epoch range check (i.e. ignoring the `start_epoch_inclusive` and `end_epoch_exclusive` parameters, if specified). Note: effectively, without an epoch range, the Radix Engine cannot perform the *intent hash duplicate* detection, which means that this check will be skipped as well. | -**use_free_credit** | **bool** | Whether to use a virtual, preview-only pool of XRD to pay for all execution fees. | - -[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) - - diff --git a/generated-clients/core-api-client/async-client/docs/TransactionPreviewResponse.md b/generated-clients/core-api-client/async-client/docs/TransactionPreviewResponse.md index 9d13f79..e69fe39 100644 --- a/generated-clients/core-api-client/async-client/docs/TransactionPreviewResponse.md +++ b/generated-clients/core-api-client/async-client/docs/TransactionPreviewResponse.md @@ -8,7 +8,7 @@ Name | Type | Description | Notes **encoded_receipt** | **String** | The hex-sbor-encoded receipt. This field is deprecated and will be removed from the API with the release of the next protocol update, cuttlefish. This field was provided primarily for use with the Radix Engine Toolkit and its execution summary functionality. If you still wish to use this functionality update your Radix Engine Toolkit and use the receipt provided in the `radix_engine_toolkit_receipt` field of this response. | **instruction_resource_changes** | [**Vec**](InstructionResourceChanges.md) | | **logs** | [**Vec**](TransactionPreviewResponse_logs_inner.md) | | -**radix_engine_toolkit_receipt** | Option<[**serde_json::Value**](.md)> | An optional field which is only provided if the `request_radix_engine_toolkit_receipt` flag is set to true when requesting a transaction preview from the API. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. | [optional] +**radix_engine_toolkit_receipt** | Option<[**serde_json::Value**](.md)> | An optional field which is only provided if the `radix_engine_toolkit_receipt` flag is set to true when requesting a transaction preview from the API. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. | [optional] **receipt** | [**models::TransactionReceipt**](TransactionReceipt.md) | | [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ErrorDetails.md b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ErrorDetails.md new file mode 100644 index 0000000..0e4416b --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ErrorDetails.md @@ -0,0 +1,10 @@ +# TransactionPreviewV2ErrorDetails + +## Enum Variants + +| Name | Value | +|---- | -----| + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ErrorDetailsType.md b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ErrorDetailsType.md new file mode 100644 index 0000000..cfa6be4 --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ErrorDetailsType.md @@ -0,0 +1,12 @@ +# TransactionPreviewV2ErrorDetailsType + +## Enum Variants + +| Name | Value | +|---- | -----| +| Invalid | Invalid | + + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ErrorResponse.md b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ErrorResponse.md new file mode 100644 index 0000000..6d24cd0 --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ErrorResponse.md @@ -0,0 +1,14 @@ +# TransactionPreviewV2ErrorResponse + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**code** | **i32** | A numeric code corresponding to the given HTTP error code. | +**details** | Option<[**models::TransactionPreviewV2ErrorDetails**](TransactionPreviewV2ErrorDetails.md)> | | [optional] +**message** | **String** | A human-readable error message. | +**trace_id** | Option<**String**> | A GUID to be used when reporting errors, to allow correlation with the Core API's error logs, in the case where the Core API details are hidden. | [optional] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2Request.md b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2Request.md new file mode 100644 index 0000000..481cfe8 --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2Request.md @@ -0,0 +1,15 @@ +# TransactionPreviewV2Request + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**at_ledger_state** | Option<[**models::LedgerStateSelector**](LedgerStateSelector.md)> | | [optional] +**flags** | Option<[**models::PreviewFlags**](PreviewFlags.md)> | | [optional] +**network** | **String** | The logical name of the network | +**options** | Option<[**models::TransactionPreviewV2ResponseOptions**](TransactionPreviewV2ResponseOptions.md)> | | [optional] +**preview_transaction** | [**models::PreviewTransaction**](PreviewTransaction.md) | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2Response.md b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2Response.md new file mode 100644 index 0000000..486c5ee --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2Response.md @@ -0,0 +1,14 @@ +# TransactionPreviewV2Response + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**at_ledger_state** | [**models::LedgerStateSummary**](LedgerStateSummary.md) | A summarized state of the ledger on top of which the preview was performed. | +**logs** | Option<[**Vec**](TransactionPreviewResponse_logs_inner.md)> | An optional field which is only provided if the `logs` flag is set to true in the `options` property of the request. If present, it gives the emitted logs from the transaction execution. | [optional] +**radix_engine_toolkit_receipt** | Option<[**serde_json::Value**](.md)> | An optional field which is only provided if the `radix_engine_toolkit_receipt` flag is set to true in the `options` property of the request. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. | [optional] +**receipt** | Option<[**models::TransactionReceipt**](TransactionReceipt.md)> | This is provided unless the `core_api_receipt` flag is set to false in the `options` property of the request. | [optional] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ResponseOptions.md b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ResponseOptions.md new file mode 100644 index 0000000..e032b27 --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/TransactionPreviewV2ResponseOptions.md @@ -0,0 +1,13 @@ +# TransactionPreviewV2ResponseOptions + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**core_api_receipt** | Option<**bool**> | This flag controls whether the preview response will include a Core API receipt or not. If not provided, this defaults to `false` and no core api receipt is provided in the response. | [optional] +**logs** | Option<**bool**> | This flag controls whether the preview response will include execution logs. If not provided, this defaults to `false` and no logs will be provided in the response. | [optional] +**radix_engine_toolkit_receipt** | Option<**bool**> | This flag controls whether the preview response will include a Radix Engine Toolkit serializable receipt or not. If not provided, this defaults to `false` and no toolkit receipt is provided in the response. | [optional] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/TransactionReceipt.md b/generated-clients/core-api-client/async-client/docs/TransactionReceipt.md index 3428842..69286c7 100644 --- a/generated-clients/core-api-client/async-client/docs/TransactionReceipt.md +++ b/generated-clients/core-api-client/async-client/docs/TransactionReceipt.md @@ -5,13 +5,13 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **costing_parameters** | [**models::CostingParameters**](CostingParameters.md) | | -**error_message** | Option<**String**> | Error message (only present if status is `Failed` or `Rejected`) | [optional] +**error_message** | Option<**String**> | The error message. This property is only present if the status is `Failed` or `Rejected`. | [optional] **events** | Option<[**Vec**](Event.md)> | | [optional] **fee_destination** | Option<[**models::FeeDestination**](FeeDestination.md)> | Only present if the `status` is not `Rejected`. | [optional] **fee_source** | Option<[**models::FeeSource**](FeeSource.md)> | Only present if the `status` is not `Rejected`. | [optional] **fee_summary** | [**models::FeeSummary**](FeeSummary.md) | | **next_epoch** | Option<[**models::NextEpoch**](NextEpoch.md)> | | [optional] -**output** | Option<[**Vec**](SborData.md)> | The manifest line-by-line engine return data (only present if `status` is `Succeeded`) | [optional] +**output** | Option<[**Vec**](SborData.md)> | The return data for each line of the transaction intent's manifest. This property is only present if the `status` is `Succeeded`. | [optional] **state_updates** | [**models::StateUpdates**](StateUpdates.md) | | **status** | [**models::TransactionStatus**](TransactionStatus.md) | | diff --git a/generated-clients/core-api-client/async-client/docs/TransactionSubmitPriorityThresholdNotMetErrorDetails.md b/generated-clients/core-api-client/async-client/docs/TransactionSubmitPriorityThresholdNotMetErrorDetails.md index 49bd332..9d1b2a2 100644 --- a/generated-clients/core-api-client/async-client/docs/TransactionSubmitPriorityThresholdNotMetErrorDetails.md +++ b/generated-clients/core-api-client/async-client/docs/TransactionSubmitPriorityThresholdNotMetErrorDetails.md @@ -4,8 +4,10 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- -**min_tip_percentage_required** | Option<**u32**> | A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] -**tip_percentage** | **u32** | Tip percentage of the submitted (and rejected) transaction. | +**min_tip_percentage_required** | Option<**u32**> | NOTE: This is kept for backwards compatibility, but we recommend using `min_tip_proportion_required` instead. A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] +**min_tip_proportion_required** | Option<**String**> | A lower bound for tip proportion at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] +**tip_percentage** | **u32** | NOTE: This is kept for backwards compatibility, but we recommend using `tip_proportion` instead. Tip percentage of the submitted (and rejected) transaction. For V2 transactions specifying basis point tips, the amount is rounded down. | +**tip_proportion** | Option<**String**> | The string-encoded decimal tip proportion of the submitted (and rejected) transaction. This field will always be present on Cuttlefish nodes, but is marked as not-required for Cuttlefish launch, to avoid a dependency on clients to update after the node is updated. | [optional] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/async-client/docs/TransactionValidationConfig.md b/generated-clients/core-api-client/async-client/docs/TransactionValidationConfig.md new file mode 100644 index 0000000..15767be --- /dev/null +++ b/generated-clients/core-api-client/async-client/docs/TransactionValidationConfig.md @@ -0,0 +1,26 @@ +# TransactionValidationConfig + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**manifest_validation** | [**models::ManifestValidationRuleset**](ManifestValidationRuleset.md) | | +**max_epoch_range** | **String** | | +**max_instructions** | **String** | | +**max_references_per_intent** | **String** | | +**max_signer_signatures_per_intent** | **String** | | +**max_subintent_depth** | **String** | | +**max_tip_basis_points** | **u64** | | +**max_tip_percentage** | **u32** | Only applies to V1 transactions | +**max_total_references** | **String** | | +**max_total_signature_validations** | **String** | | +**message_validation** | [**models::MessageValidationConfig**](MessageValidationConfig.md) | | +**min_tip_basis_points** | **u64** | | +**min_tip_percentage** | **u32** | Only applies to V1 transactions | +**preparation_settings** | [**models::PreparationSettings**](PreparationSettings.md) | | +**v1_transactions_allow_notary_to_duplicate_signer** | **bool** | | +**v2_transactions_allowed** | **bool** | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/src/apis/configuration.rs b/generated-clients/core-api-client/async-client/src/apis/configuration.rs index e959c70..2132ad0 100644 --- a/generated-clients/core-api-client/async-client/src/apis/configuration.rs +++ b/generated-clients/core-api-client/async-client/src/apis/configuration.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -41,7 +41,7 @@ impl Default for Configuration { fn default() -> Self { Configuration { base_path: "http://localhost:3333/core".to_owned(), - user_agent: Some("OpenAPI-Generator/v1.2.3/rust".to_owned()), + user_agent: Some("OpenAPI-Generator/v1.3.0/rust".to_owned()), client: reqwest::Client::new(), basic_auth: None, oauth_access_token: None, diff --git a/generated-clients/core-api-client/async-client/src/apis/lts_api.rs b/generated-clients/core-api-client/async-client/src/apis/lts_api.rs index aa8366e..20a30c1 100644 --- a/generated-clients/core-api-client/async-client/src/apis/lts_api.rs +++ b/generated-clients/core-api-client/async-client/src/apis/lts_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/apis/mempool_api.rs b/generated-clients/core-api-client/async-client/src/apis/mempool_api.rs index 6289c6f..9f09a55 100644 --- a/generated-clients/core-api-client/async-client/src/apis/mempool_api.rs +++ b/generated-clients/core-api-client/async-client/src/apis/mempool_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/apis/state_api.rs b/generated-clients/core-api-client/async-client/src/apis/state_api.rs index 0856360..ed4291e 100644 --- a/generated-clients/core-api-client/async-client/src/apis/state_api.rs +++ b/generated-clients/core-api-client/async-client/src/apis/state_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/apis/status_api.rs b/generated-clients/core-api-client/async-client/src/apis/status_api.rs index 4d30690..596a5ba 100644 --- a/generated-clients/core-api-client/async-client/src/apis/status_api.rs +++ b/generated-clients/core-api-client/async-client/src/apis/status_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/apis/stream_api.rs b/generated-clients/core-api-client/async-client/src/apis/stream_api.rs index 33a7974..cbed2ca 100644 --- a/generated-clients/core-api-client/async-client/src/apis/stream_api.rs +++ b/generated-clients/core-api-client/async-client/src/apis/stream_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/apis/transaction_api.rs b/generated-clients/core-api-client/async-client/src/apis/transaction_api.rs index b84c39d..bbf73e0 100644 --- a/generated-clients/core-api-client/async-client/src/apis/transaction_api.rs +++ b/generated-clients/core-api-client/async-client/src/apis/transaction_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -42,6 +42,15 @@ pub enum TransactionPreviewPostError { UnknownValue(serde_json::Value), } +/// struct for typed errors of method [`transaction_preview_v2_post`] +#[derive(Debug, Clone, Serialize, Deserialize)] +#[serde(untagged)] +pub enum TransactionPreviewV2PostError { + Status400(models::TransactionPreviewV2ErrorResponse), + Status500(models::TransactionPreviewV2ErrorResponse), + UnknownValue(serde_json::Value), +} + /// struct for typed errors of method [`transaction_receipt_post`] #[derive(Debug, Clone, Serialize, Deserialize)] #[serde(untagged)] @@ -129,7 +138,7 @@ pub async fn transaction_parse_post(configuration: &configuration::Configuration } } -/// Preview a transaction against the latest network state, and returns the preview receipt. +/// Preview a transaction against the latest network state, and returns the preview receipt. If the node has enabled it, you may be able to also preview against recent network state. For V2 transactions (and beyond) the `/preview-v2` endpoint should be used instead. pub async fn transaction_preview_post(configuration: &configuration::Configuration, transaction_preview_request: models::TransactionPreviewRequest) -> Result> { let local_var_configuration = configuration; @@ -158,6 +167,35 @@ pub async fn transaction_preview_post(configuration: &configuration::Configurati } } +/// Previews a transaction against the latest network state, and returns the preview receipt. If the node has enabled it, you may be able to also preview against recent network state. This endpoint supports V2 transactions (and beyond). If you still need to preview V1 transactions, you should use the `/preview` endpoint instead. +pub async fn transaction_preview_v2_post(configuration: &configuration::Configuration, transaction_preview_v2_request: models::TransactionPreviewV2Request) -> Result> { + let local_var_configuration = configuration; + + let local_var_client = &local_var_configuration.client; + + let local_var_uri_str = format!("{}/transaction/preview-v2", local_var_configuration.base_path); + let mut local_var_req_builder = local_var_client.request(reqwest::Method::POST, local_var_uri_str.as_str()); + + if let Some(ref local_var_user_agent) = local_var_configuration.user_agent { + local_var_req_builder = local_var_req_builder.header(reqwest::header::USER_AGENT, local_var_user_agent.clone()); + } + local_var_req_builder = local_var_req_builder.json(&transaction_preview_v2_request); + + let local_var_req = local_var_req_builder.build()?; + let local_var_resp = local_var_client.execute(local_var_req).await?; + + let local_var_status = local_var_resp.status(); + let local_var_content = local_var_resp.text().await?; + + if !local_var_status.is_client_error() && !local_var_status.is_server_error() { + serde_json::from_str(&local_var_content).map_err(Error::from) + } else { + let local_var_entity: Option = serde_json::from_str(&local_var_content).ok(); + let local_var_error = ResponseContent { status: local_var_status, content: local_var_content, entity: local_var_entity }; + Err(Error::ResponseError(local_var_error)) + } +} + /// Gets the transaction receipt for a committed transaction. pub async fn transaction_receipt_post(configuration: &configuration::Configuration, transaction_receipt_request: models::TransactionReceiptRequest) -> Result> { let local_var_configuration = configuration; diff --git a/generated-clients/core-api-client/async-client/src/models/access_controller_field_state_substate.rs b/generated-clients/core-api-client/async-client/src/models/access_controller_field_state_substate.rs index 895f65d..d709a22 100644 --- a/generated-clients/core-api-client/async-client/src/models/access_controller_field_state_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/access_controller_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/access_controller_field_state_value.rs b/generated-clients/core-api-client/async-client/src/models/access_controller_field_state_value.rs index f056d24..3e43f16 100644 --- a/generated-clients/core-api-client/async-client/src/models/access_controller_field_state_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/access_controller_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/access_rule.rs b/generated-clients/core-api-client/async-client/src/models/access_rule.rs index ab2ec13..0eba7da 100644 --- a/generated-clients/core-api-client/async-client/src/models/access_rule.rs +++ b/generated-clients/core-api-client/async-client/src/models/access_rule.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,6 +11,7 @@ use crate::models; use serde::{Deserialize, Serialize}; +/// AccessRule : A representation of an access rule in the Radix Engine. Note that some of the field and discriminator names use an older naming schema, for backwards compatibility. See the [advanced access rules](https://docs.radixdlt.com/docs/advanced-accessrules) docs for more information. #[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] #[serde(tag = "type")] pub enum AccessRule { diff --git a/generated-clients/core-api-client/async-client/src/models/access_rule_type.rs b/generated-clients/core-api-client/async-client/src/models/access_rule_type.rs index 1bbe63a..a073343 100644 --- a/generated-clients/core-api-client/async-client/src/models/access_rule_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/access_rule_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/account_address_key.rs b/generated-clients/core-api-client/async-client/src/models/account_address_key.rs index 0109dce..08d53ac 100644 --- a/generated-clients/core-api-client/async-client/src/models/account_address_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/account_address_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/account_authorized_depositor_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/account_authorized_depositor_entry_substate.rs index 4ed5b8f..88eada4 100644 --- a/generated-clients/core-api-client/async-client/src/models/account_authorized_depositor_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/account_authorized_depositor_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/account_authorized_depositor_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/account_authorized_depositor_entry_value.rs index d95d188..edeb3a7 100644 --- a/generated-clients/core-api-client/async-client/src/models/account_authorized_depositor_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/account_authorized_depositor_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/account_field_state_substate.rs b/generated-clients/core-api-client/async-client/src/models/account_field_state_substate.rs index ededb98..a8ae81a 100644 --- a/generated-clients/core-api-client/async-client/src/models/account_field_state_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/account_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/account_field_state_value.rs b/generated-clients/core-api-client/async-client/src/models/account_field_state_value.rs index bbdb649..5bb8eac 100644 --- a/generated-clients/core-api-client/async-client/src/models/account_field_state_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/account_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/account_locker_account_claims_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/account_locker_account_claims_entry_substate.rs index 82fccd2..13ce6d8 100644 --- a/generated-clients/core-api-client/async-client/src/models/account_locker_account_claims_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/account_locker_account_claims_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/account_locker_account_claims_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/account_locker_account_claims_entry_value.rs index 99a1f66..8cffb50 100644 --- a/generated-clients/core-api-client/async-client/src/models/account_locker_account_claims_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/account_locker_account_claims_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/account_resource_preference_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/account_resource_preference_entry_substate.rs index 4f27cd5..7421080 100644 --- a/generated-clients/core-api-client/async-client/src/models/account_resource_preference_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/account_resource_preference_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/account_resource_preference_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/account_resource_preference_entry_value.rs index 3f82e1a..a1fadb7 100644 --- a/generated-clients/core-api-client/async-client/src/models/account_resource_preference_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/account_resource_preference_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/account_vault_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/account_vault_entry_substate.rs index 880178f..57692a3 100644 --- a/generated-clients/core-api-client/async-client/src/models/account_vault_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/account_vault_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/account_vault_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/account_vault_entry_value.rs index 53f6a68..d54f8ae 100644 --- a/generated-clients/core-api-client/async-client/src/models/account_vault_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/account_vault_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/active_validator.rs b/generated-clients/core-api-client/async-client/src/models/active_validator.rs index e8512aa..a6836aa 100644 --- a/generated-clients/core-api-client/async-client/src/models/active_validator.rs +++ b/generated-clients/core-api-client/async-client/src/models/active_validator.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/active_validator_index.rs b/generated-clients/core-api-client/async-client/src/models/active_validator_index.rs index 55fd828..26da2d6 100644 --- a/generated-clients/core-api-client/async-client/src/models/active_validator_index.rs +++ b/generated-clients/core-api-client/async-client/src/models/active_validator_index.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/active_validator_key.rs b/generated-clients/core-api-client/async-client/src/models/active_validator_key.rs index acc55a9..371e491 100644 --- a/generated-clients/core-api-client/async-client/src/models/active_validator_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/active_validator_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/address_type.rs b/generated-clients/core-api-client/async-client/src/models/address_type.rs index bbf8a30..4c2ae85 100644 --- a/generated-clients/core-api-client/async-client/src/models/address_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/address_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/all_of_proof_rule.rs b/generated-clients/core-api-client/async-client/src/models/all_of_basic_requirement.rs similarity index 90% rename from generated-clients/core-api-client/async-client/src/models/all_of_proof_rule.rs rename to generated-clients/core-api-client/async-client/src/models/all_of_basic_requirement.rs index c8cf7b9..c630f64 100644 --- a/generated-clients/core-api-client/async-client/src/models/all_of_proof_rule.rs +++ b/generated-clients/core-api-client/async-client/src/models/all_of_basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct AllOfProofRule { +pub struct AllOfBasicRequirement { #[serde(rename = "list")] pub list: Vec, } -impl AllOfProofRule { - pub fn new(list: Vec) -> AllOfProofRule { - AllOfProofRule { +impl AllOfBasicRequirement { + pub fn new(list: Vec) -> AllOfBasicRequirement { + AllOfBasicRequirement { list, } } diff --git a/generated-clients/core-api-client/sync-client/src/models/all_of_access_rule_node.rs b/generated-clients/core-api-client/async-client/src/models/all_of_composite_requirement.rs similarity index 87% rename from generated-clients/core-api-client/sync-client/src/models/all_of_access_rule_node.rs rename to generated-clients/core-api-client/async-client/src/models/all_of_composite_requirement.rs index 441cb14..7603b02 100644 --- a/generated-clients/core-api-client/sync-client/src/models/all_of_access_rule_node.rs +++ b/generated-clients/core-api-client/async-client/src/models/all_of_composite_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct AllOfAccessRuleNode { +pub struct AllOfCompositeRequirement { #[serde(rename = "access_rules")] - pub access_rules: Vec, + pub access_rules: Vec, } -impl AllOfAccessRuleNode { - pub fn new(access_rules: Vec) -> AllOfAccessRuleNode { - AllOfAccessRuleNode { +impl AllOfCompositeRequirement { + pub fn new(access_rules: Vec) -> AllOfCompositeRequirement { + AllOfCompositeRequirement { access_rules, } } diff --git a/generated-clients/core-api-client/async-client/src/models/always_visible_global_nodes_version.rs b/generated-clients/core-api-client/async-client/src/models/always_visible_global_nodes_version.rs index ad022e7..5d20ff5 100644 --- a/generated-clients/core-api-client/async-client/src/models/always_visible_global_nodes_version.rs +++ b/generated-clients/core-api-client/async-client/src/models/always_visible_global_nodes_version.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/amount_of_proof_rule.rs b/generated-clients/core-api-client/async-client/src/models/amount_of_basic_requirement.rs similarity index 90% rename from generated-clients/core-api-client/sync-client/src/models/amount_of_proof_rule.rs rename to generated-clients/core-api-client/async-client/src/models/amount_of_basic_requirement.rs index c019f33..0772c94 100644 --- a/generated-clients/core-api-client/sync-client/src/models/amount_of_proof_rule.rs +++ b/generated-clients/core-api-client/async-client/src/models/amount_of_basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,7 +12,7 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct AmountOfProofRule { +pub struct AmountOfBasicRequirement { #[serde(rename = "amount")] pub amount: String, /// The Bech32m-encoded human readable version of the resource address @@ -20,9 +20,9 @@ pub struct AmountOfProofRule { pub resource: String, } -impl AmountOfProofRule { - pub fn new(amount: String, resource: String) -> AmountOfProofRule { - AmountOfProofRule { +impl AmountOfBasicRequirement { + pub fn new(amount: String, resource: String) -> AmountOfBasicRequirement { + AmountOfBasicRequirement { amount, resource, } diff --git a/generated-clients/core-api-client/sync-client/src/models/any_of_proof_rule.rs b/generated-clients/core-api-client/async-client/src/models/any_of_basic_requirement.rs similarity index 90% rename from generated-clients/core-api-client/sync-client/src/models/any_of_proof_rule.rs rename to generated-clients/core-api-client/async-client/src/models/any_of_basic_requirement.rs index 69f8e89..aac58bd 100644 --- a/generated-clients/core-api-client/sync-client/src/models/any_of_proof_rule.rs +++ b/generated-clients/core-api-client/async-client/src/models/any_of_basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct AnyOfProofRule { +pub struct AnyOfBasicRequirement { #[serde(rename = "list")] pub list: Vec, } -impl AnyOfProofRule { - pub fn new(list: Vec) -> AnyOfProofRule { - AnyOfProofRule { +impl AnyOfBasicRequirement { + pub fn new(list: Vec) -> AnyOfBasicRequirement { + AnyOfBasicRequirement { list, } } diff --git a/generated-clients/core-api-client/async-client/src/models/any_of_access_rule_node.rs b/generated-clients/core-api-client/async-client/src/models/any_of_composite_requirement.rs similarity index 87% rename from generated-clients/core-api-client/async-client/src/models/any_of_access_rule_node.rs rename to generated-clients/core-api-client/async-client/src/models/any_of_composite_requirement.rs index e481eb4..dacd1c0 100644 --- a/generated-clients/core-api-client/async-client/src/models/any_of_access_rule_node.rs +++ b/generated-clients/core-api-client/async-client/src/models/any_of_composite_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct AnyOfAccessRuleNode { +pub struct AnyOfCompositeRequirement { #[serde(rename = "access_rules")] - pub access_rules: Vec, + pub access_rules: Vec, } -impl AnyOfAccessRuleNode { - pub fn new(access_rules: Vec) -> AnyOfAccessRuleNode { - AnyOfAccessRuleNode { +impl AnyOfCompositeRequirement { + pub fn new(access_rules: Vec) -> AnyOfCompositeRequirement { + AnyOfCompositeRequirement { access_rules, } } diff --git a/generated-clients/core-api-client/async-client/src/models/attached_module_id.rs b/generated-clients/core-api-client/async-client/src/models/attached_module_id.rs index 16418ee..459d61d 100644 --- a/generated-clients/core-api-client/async-client/src/models/attached_module_id.rs +++ b/generated-clients/core-api-client/async-client/src/models/attached_module_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/auth_config.rs b/generated-clients/core-api-client/async-client/src/models/auth_config.rs index 116ce09..6208cee 100644 --- a/generated-clients/core-api-client/async-client/src/models/auth_config.rs +++ b/generated-clients/core-api-client/async-client/src/models/auth_config.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/authorized_depositor_badge.rs b/generated-clients/core-api-client/async-client/src/models/authorized_depositor_badge.rs index 524ecb1..354e837 100644 --- a/generated-clients/core-api-client/async-client/src/models/authorized_depositor_badge.rs +++ b/generated-clients/core-api-client/async-client/src/models/authorized_depositor_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/authorized_depositor_badge_type.rs b/generated-clients/core-api-client/async-client/src/models/authorized_depositor_badge_type.rs index 65c5a8c..089b7b2 100644 --- a/generated-clients/core-api-client/async-client/src/models/authorized_depositor_badge_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/authorized_depositor_badge_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/authorized_depositor_key.rs b/generated-clients/core-api-client/async-client/src/models/authorized_depositor_key.rs index 88a0527..4593708 100644 --- a/generated-clients/core-api-client/async-client/src/models/authorized_depositor_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/authorized_depositor_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/basic_error_response.rs b/generated-clients/core-api-client/async-client/src/models/basic_error_response.rs index 6737a21..ae0f8c8 100644 --- a/generated-clients/core-api-client/async-client/src/models/basic_error_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/basic_error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/proof_rule.rs b/generated-clients/core-api-client/async-client/src/models/basic_requirement.rs similarity index 87% rename from generated-clients/core-api-client/async-client/src/models/proof_rule.rs rename to generated-clients/core-api-client/async-client/src/models/basic_requirement.rs index 2c8585d..da6fa0f 100644 --- a/generated-clients/core-api-client/async-client/src/models/proof_rule.rs +++ b/generated-clients/core-api-client/async-client/src/models/basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -13,20 +13,20 @@ use serde::{Deserialize, Serialize}; #[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] #[serde(tag = "type")] -pub enum ProofRule { +pub enum BasicRequirement { #[serde(rename="Require")] - Require(models::RequireProofRule), + Require(models::RequireBasicRequirement), #[serde(rename="AmountOf")] - AmountOf(models::AmountOfProofRule), + AmountOf(models::AmountOfBasicRequirement), #[serde(rename="AllOf")] - AllOf(models::AllOfProofRule), + AllOf(models::AllOfBasicRequirement), #[serde(rename="AnyOf")] - AnyOf(models::AnyOfProofRule), + AnyOf(models::AnyOfBasicRequirement), #[serde(rename="CountOf")] - CountOf(models::CountOfProofRule), + CountOf(models::CountOfBasicRequirement), } -impl Default for ProofRule { +impl Default for BasicRequirement { fn default() -> Self { Self::Require(Default::default()) } diff --git a/generated-clients/core-api-client/async-client/src/models/proof_rule_type.rs b/generated-clients/core-api-client/async-client/src/models/basic_requirement_type.rs similarity index 92% rename from generated-clients/core-api-client/async-client/src/models/proof_rule_type.rs rename to generated-clients/core-api-client/async-client/src/models/basic_requirement_type.rs index 8bdb708..dae9ac0 100644 --- a/generated-clients/core-api-client/async-client/src/models/proof_rule_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/basic_requirement_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -13,7 +13,7 @@ use serde::{Deserialize, Serialize}; /// #[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] -pub enum ProofRuleType { +pub enum BasicRequirementType { #[serde(rename = "Require")] Require, #[serde(rename = "AmountOf")] @@ -27,7 +27,7 @@ pub enum ProofRuleType { } -impl std::fmt::Display for ProofRuleType { +impl std::fmt::Display for BasicRequirementType { fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { match self { Self::Require => write!(f, "Require"), @@ -39,8 +39,8 @@ impl std::fmt::Display for ProofRuleType { } } -impl Default for ProofRuleType { - fn default() -> ProofRuleType { +impl Default for BasicRequirementType { + fn default() -> BasicRequirementType { Self::Require } } diff --git a/generated-clients/core-api-client/async-client/src/models/binary_plaintext_message_content.rs b/generated-clients/core-api-client/async-client/src/models/binary_plaintext_message_content.rs index abe301c..c6876a1 100644 --- a/generated-clients/core-api-client/async-client/src/models/binary_plaintext_message_content.rs +++ b/generated-clients/core-api-client/async-client/src/models/binary_plaintext_message_content.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_collection_schema.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_collection_schema.rs index 54f34f8..9a19ad5 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_collection_schema.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_collection_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_collection_schema_type.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_collection_schema_type.rs index 3515099..ad74392 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_collection_schema_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_collection_schema_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_definition.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_definition.rs index 56e8e2f..3baaf1f 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_definition.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_definition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_dependencies.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_dependencies.rs index ec5606a..95fe488 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_dependencies.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_dependencies.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_function_target_identifier.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_function_target_identifier.rs index 43b5703..62155d2 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_function_target_identifier.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_function_target_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_info.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_info.rs index 8d5d432..3d49384 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_info.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_info.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_interface.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_interface.rs index 6be5ab3..5b771c4 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_interface.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_interface.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_method_royalty.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_method_royalty.rs index a11dd5c..f532054 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_method_royalty.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_method_royalty.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_payload_def.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_payload_def.rs index 29f307b..20e1f5c 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_payload_def.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_payload_def.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_payload_def_type.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_payload_def_type.rs index 6f68ec0..ead6943 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_payload_def_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_payload_def_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_royalty_config.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_royalty_config.rs index 25c7d36..579ef2d 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_royalty_config.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_royalty_config.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_schema_blueprint_type_reference.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_schema_blueprint_type_reference.rs index 92858f4..c7af549 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_schema_blueprint_type_reference.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_schema_blueprint_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_schema_collection_partition.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_schema_collection_partition.rs index 508e35e..5d88bc2 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_schema_collection_partition.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_schema_collection_partition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_schema_field_partition.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_schema_field_partition.rs index e40d039..dda3721 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_schema_field_partition.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_schema_field_partition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_type_identifier.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_type_identifier.rs index 665a89d..23458c0 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_type_identifier.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_type_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_type_reference.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_type_reference.rs index 4a3c188..6fe3838 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_type_reference.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_type_reference_kind.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_type_reference_kind.rs index d96dc35..fa78acf 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_type_reference_kind.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_type_reference_kind.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/blueprint_version_key.rs b/generated-clients/core-api-client/async-client/src/models/blueprint_version_key.rs index c0a69a6..d0d2baa 100644 --- a/generated-clients/core-api-client/async-client/src/models/blueprint_version_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/blueprint_version_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_kernel_boot_substate.rs b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_kernel_boot_substate.rs index eb16e5f..29cfd66 100644 --- a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_kernel_boot_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_kernel_boot_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_kernel_boot_value.rs b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_kernel_boot_value.rs index 647eb45..cb17b5d 100644 --- a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_kernel_boot_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_kernel_boot_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_system_boot_substate.rs b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_system_boot_substate.rs index 68f1d04..fb8edf1 100644 --- a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_system_boot_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_system_boot_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_system_boot_value.rs b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_system_boot_value.rs index c1ef37a..cef5474 100644 --- a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_system_boot_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_system_boot_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_transaction_validation_configuration_substate.rs b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_transaction_validation_configuration_substate.rs index a0d817f..2a25c75 100644 --- a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_transaction_validation_configuration_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_transaction_validation_configuration_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -13,13 +13,16 @@ use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] pub struct BootLoaderModuleFieldTransactionValidationConfigurationSubstate { + #[serde(rename = "config")] + pub config: models::TransactionValidationConfig, #[serde(rename = "is_locked")] pub is_locked: bool, } impl BootLoaderModuleFieldTransactionValidationConfigurationSubstate { - pub fn new(is_locked: bool) -> BootLoaderModuleFieldTransactionValidationConfigurationSubstate { + pub fn new(config: models::TransactionValidationConfig, is_locked: bool) -> BootLoaderModuleFieldTransactionValidationConfigurationSubstate { BootLoaderModuleFieldTransactionValidationConfigurationSubstate { + config, is_locked, } } diff --git a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_vm_boot_substate.rs b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_vm_boot_substate.rs index cde5c22..b19c523 100644 --- a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_vm_boot_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_vm_boot_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_vm_boot_value.rs b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_vm_boot_value.rs index 4a13f59..0970e17 100644 --- a/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_vm_boot_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/boot_loader_module_field_vm_boot_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/committed_intent_metadata.rs b/generated-clients/core-api-client/async-client/src/models/committed_intent_metadata.rs index 80c60e9..7c05823 100644 --- a/generated-clients/core-api-client/async-client/src/models/committed_intent_metadata.rs +++ b/generated-clients/core-api-client/async-client/src/models/committed_intent_metadata.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/committed_state_identifier.rs b/generated-clients/core-api-client/async-client/src/models/committed_state_identifier.rs index e5f9e91..6f8213f 100644 --- a/generated-clients/core-api-client/async-client/src/models/committed_state_identifier.rs +++ b/generated-clients/core-api-client/async-client/src/models/committed_state_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/committed_transaction.rs b/generated-clients/core-api-client/async-client/src/models/committed_transaction.rs index 6d497f0..416a100 100644 --- a/generated-clients/core-api-client/async-client/src/models/committed_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/committed_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/committed_transaction_balance_changes.rs b/generated-clients/core-api-client/async-client/src/models/committed_transaction_balance_changes.rs index 9f51914..a325b9c 100644 --- a/generated-clients/core-api-client/async-client/src/models/committed_transaction_balance_changes.rs +++ b/generated-clients/core-api-client/async-client/src/models/committed_transaction_balance_changes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/compiled_preview_transaction.rs b/generated-clients/core-api-client/async-client/src/models/compiled_preview_transaction.rs new file mode 100644 index 0000000..7a57d62 --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/compiled_preview_transaction.rs @@ -0,0 +1,28 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct CompiledPreviewTransaction { + /// A hex-encoded, compiled `RawPreviewTransaction`. As of Cuttlefish, only `PreviewTransactionV2` is supported. A `PreviewTransactionV2` can be created with a v2 transaction builder: * If using Rust, it can be created with a `TransactionV2Builder` using `build_preview_transaction()` and then converted to hex with `preview_transaction.to_raw().unwrap().to_hex()` * If using the toolkit, you can create this using the v2 transaction builder. Some subtleties: * Partial transactions can't be previewed. Instead, they must be wrapped inside a transaction wrapper, so that the engine knows how to yield to them appropriately. * Currently the builder assumes that the signed partial transactions have real signatures. This isn't strictly required, and we may create a builder in future which allows providing public keys when building partial transactions for use in preview. * If you don't have signatures to hand, you can simply not sign the partial transactions, and then use the `assume_all_signature_proofs` preview flag, although be advised that this may result in the fee estimate being slightly lower during preview. * We may create more ergonomic builders for PreviewTransactions which allow use of public keys to denote the signers of subintents. Let us know if this is important for your use case. + #[serde(rename = "preview_transaction_hex")] + pub preview_transaction_hex: String, +} + +impl CompiledPreviewTransaction { + pub fn new(preview_transaction_hex: String) -> CompiledPreviewTransaction { + CompiledPreviewTransaction { + preview_transaction_hex, + } + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/component_method_target_identifier.rs b/generated-clients/core-api-client/async-client/src/models/component_method_target_identifier.rs index a20ac81..1434bf4 100644 --- a/generated-clients/core-api-client/async-client/src/models/component_method_target_identifier.rs +++ b/generated-clients/core-api-client/async-client/src/models/component_method_target_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/access_rule_node.rs b/generated-clients/core-api-client/async-client/src/models/composite_requirement.rs similarity index 86% rename from generated-clients/core-api-client/async-client/src/models/access_rule_node.rs rename to generated-clients/core-api-client/async-client/src/models/composite_requirement.rs index 1fe6d75..204c475 100644 --- a/generated-clients/core-api-client/async-client/src/models/access_rule_node.rs +++ b/generated-clients/core-api-client/async-client/src/models/composite_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,18 +11,19 @@ use crate::models; use serde::{Deserialize, Serialize}; +/// CompositeRequirement : This type was historically called `AccessRuleNode`. #[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] #[serde(tag = "type")] -pub enum AccessRuleNode { +pub enum CompositeRequirement { #[serde(rename="ProofRule")] - ProofRule(models::ProofAccessRuleNode), + ProofRule(models::ProofRuleCompositeRequirement), #[serde(rename="AnyOf")] - AnyOf(models::AnyOfAccessRuleNode), + AnyOf(models::AnyOfCompositeRequirement), #[serde(rename="AllOf")] - AllOf(models::AllOfAccessRuleNode), + AllOf(models::AllOfCompositeRequirement), } -impl Default for AccessRuleNode { +impl Default for CompositeRequirement { fn default() -> Self { Self::ProofRule(Default::default()) } diff --git a/generated-clients/core-api-client/sync-client/src/models/access_rule_node_type.rs b/generated-clients/core-api-client/async-client/src/models/composite_requirement_type.rs similarity index 87% rename from generated-clients/core-api-client/sync-client/src/models/access_rule_node_type.rs rename to generated-clients/core-api-client/async-client/src/models/composite_requirement_type.rs index be711f2..92f2194 100644 --- a/generated-clients/core-api-client/sync-client/src/models/access_rule_node_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/composite_requirement_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,9 +11,10 @@ use crate::models; use serde::{Deserialize, Serialize}; -/// +/// CompositeRequirementType : `ProofRule` is now called `BasicRequirement`. +/// `ProofRule` is now called `BasicRequirement`. #[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] -pub enum AccessRuleNodeType { +pub enum CompositeRequirementType { #[serde(rename = "ProofRule")] ProofRule, #[serde(rename = "AnyOf")] @@ -23,7 +24,7 @@ pub enum AccessRuleNodeType { } -impl std::fmt::Display for AccessRuleNodeType { +impl std::fmt::Display for CompositeRequirementType { fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { match self { Self::ProofRule => write!(f, "ProofRule"), @@ -33,8 +34,8 @@ impl std::fmt::Display for AccessRuleNodeType { } } -impl Default for AccessRuleNodeType { - fn default() -> AccessRuleNodeType { +impl Default for CompositeRequirementType { + fn default() -> CompositeRequirementType { Self::ProofRule } } diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_ledger_proof_origin.rs b/generated-clients/core-api-client/async-client/src/models/consensus_ledger_proof_origin.rs index 24df61d..2e99e35 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_ledger_proof_origin.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_ledger_proof_origin.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_config_substate.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_config_substate.rs index 8bcca99..f0473aa 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_config_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_config_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_config_value.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_config_value.rs index ff85bde..3568ed2 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_config_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_config_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_proposal_statistic_substate.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_proposal_statistic_substate.rs index d3356fa..7dfa45a 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_proposal_statistic_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_proposal_statistic_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_proposal_statistic_value.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_proposal_statistic_value.rs index 442d508..21b2cdc 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_proposal_statistic_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_proposal_statistic_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs index 0d34f43..3c0a921 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs index 189c04b..93876b3 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_substate.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_substate.rs index 0682420..caf1c96 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_value.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_value.rs index 9091210..1b81e40 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_time_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_validator_set_substate.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_validator_set_substate.rs index 88a06c7..a745f43 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_validator_set_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_validator_set_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_validator_set_value.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_validator_set_value.rs index c41dca0..9c874a7 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_validator_set_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_current_validator_set_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_state_substate.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_state_substate.rs index 214a93c..743705c 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_state_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_state_value.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_state_value.rs index e35c34f..2e49345 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_state_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_validator_rewards_substate.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_validator_rewards_substate.rs index f51ee82..3a51bdc 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_validator_rewards_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_validator_rewards_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_validator_rewards_value.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_validator_rewards_value.rs index 39accad..ae08268 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_validator_rewards_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_field_validator_rewards_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs index 65deed9..ab600ae 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs index 82280c1..f1978a7 100644 --- a/generated-clients/core-api-client/async-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/costing_module_config.rs b/generated-clients/core-api-client/async-client/src/models/costing_module_config.rs index 058ac8e..d064a54 100644 --- a/generated-clients/core-api-client/async-client/src/models/costing_module_config.rs +++ b/generated-clients/core-api-client/async-client/src/models/costing_module_config.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/costing_parameters.rs b/generated-clients/core-api-client/async-client/src/models/costing_parameters.rs index 2b62252..7702b4a 100644 --- a/generated-clients/core-api-client/async-client/src/models/costing_parameters.rs +++ b/generated-clients/core-api-client/async-client/src/models/costing_parameters.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -28,9 +28,12 @@ pub struct CostingParameters { /// The string-encoded decimal representing the XRD price of a single cost unit of transaction finalization. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. #[serde(rename = "finalization_cost_unit_price")] pub finalization_cost_unit_price: String, - /// An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to 1% of the fee. + /// NOTE: V2 transactions specify the tip in basis points, which gets rounded down for this `tip_percentage` field. It is recommended to instead use the `tip_proportion` field to get a fully accurate value. An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to 1% of the fee. #[serde(rename = "tip_percentage")] pub tip_percentage: u32, + /// A string-encoded decimal, giving the validator tip as a proportional amount. A value of `\"0.01\"` corresponds to 1% of the fee being paid as a tip. NOTE: This field is not marked as required for Cuttlefish launch, to permit cuttlefish clients to talk to pre-cuttlefish nodes. This can be changed after Cuttlefish enactment once all nodes are on Cuttlefish. + #[serde(rename = "tip_proportion", skip_serializing_if = "Option::is_none")] + pub tip_proportion: Option, /// The string-encoded decimal representing the price of 1 byte of archive storage, expressed in XRD. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. #[serde(rename = "xrd_archive_storage_price")] pub xrd_archive_storage_price: String, @@ -51,6 +54,7 @@ impl CostingParameters { finalization_cost_unit_limit, finalization_cost_unit_price, tip_percentage, + tip_proportion: None, xrd_archive_storage_price, xrd_storage_price, xrd_usd_price, diff --git a/generated-clients/core-api-client/sync-client/src/models/count_of_proof_rule.rs b/generated-clients/core-api-client/async-client/src/models/count_of_basic_requirement.rs similarity index 92% rename from generated-clients/core-api-client/sync-client/src/models/count_of_proof_rule.rs rename to generated-clients/core-api-client/async-client/src/models/count_of_basic_requirement.rs index b240d16..eed045d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/count_of_proof_rule.rs +++ b/generated-clients/core-api-client/async-client/src/models/count_of_basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,16 +12,16 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct CountOfProofRule { +pub struct CountOfBasicRequirement { #[serde(rename = "count")] pub count: i32, #[serde(rename = "list")] pub list: Vec, } -impl CountOfProofRule { - pub fn new(count: i32, list: Vec) -> CountOfProofRule { - CountOfProofRule { +impl CountOfBasicRequirement { + pub fn new(count: i32, list: Vec) -> CountOfBasicRequirement { + CountOfBasicRequirement { count, list, } diff --git a/generated-clients/core-api-client/async-client/src/models/created_substate.rs b/generated-clients/core-api-client/async-client/src/models/created_substate.rs index 120eaab..b46eea8 100644 --- a/generated-clients/core-api-client/async-client/src/models/created_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/created_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/data_struct.rs b/generated-clients/core-api-client/async-client/src/models/data_struct.rs index 04bd2cf..d1d1f5f 100644 --- a/generated-clients/core-api-client/async-client/src/models/data_struct.rs +++ b/generated-clients/core-api-client/async-client/src/models/data_struct.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/default_deposit_rule.rs b/generated-clients/core-api-client/async-client/src/models/default_deposit_rule.rs index 9945329..f5e17b0 100644 --- a/generated-clients/core-api-client/async-client/src/models/default_deposit_rule.rs +++ b/generated-clients/core-api-client/async-client/src/models/default_deposit_rule.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/deleted_substate.rs b/generated-clients/core-api-client/async-client/src/models/deleted_substate.rs index d178195..9b2dd31 100644 --- a/generated-clients/core-api-client/async-client/src/models/deleted_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/deleted_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_public_key.rs b/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_public_key.rs index f1da63d..a85c909 100644 --- a/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_public_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_signature.rs b/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_signature.rs index 89a07fe..5783707 100644 --- a/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_signature.rs +++ b/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_signature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_signature_with_public_key.rs b/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_signature_with_public_key.rs index b219e23..4d1cc9a 100644 --- a/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_signature_with_public_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/ecdsa_secp256k1_signature_with_public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_public_key.rs b/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_public_key.rs index 0b1177e..81dee70 100644 --- a/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_public_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_signature.rs b/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_signature.rs index fe7172b..20e4de8 100644 --- a/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_signature.rs +++ b/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_signature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_signature_with_public_key.rs b/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_signature_with_public_key.rs index 8218fbd..b4a213d 100644 --- a/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_signature_with_public_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/eddsa_ed25519_signature_with_public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/encrypted_message_curve_decryptor_set.rs b/generated-clients/core-api-client/async-client/src/models/encrypted_message_curve_decryptor_set.rs index 6e3ce19..031719e 100644 --- a/generated-clients/core-api-client/async-client/src/models/encrypted_message_curve_decryptor_set.rs +++ b/generated-clients/core-api-client/async-client/src/models/encrypted_message_curve_decryptor_set.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/encrypted_message_decryptor.rs b/generated-clients/core-api-client/async-client/src/models/encrypted_message_decryptor.rs index 281632a..09253a2 100644 --- a/generated-clients/core-api-client/async-client/src/models/encrypted_message_decryptor.rs +++ b/generated-clients/core-api-client/async-client/src/models/encrypted_message_decryptor.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/encrypted_transaction_message.rs b/generated-clients/core-api-client/async-client/src/models/encrypted_transaction_message.rs index a91bb36..fda96f3 100644 --- a/generated-clients/core-api-client/async-client/src/models/encrypted_transaction_message.rs +++ b/generated-clients/core-api-client/async-client/src/models/encrypted_transaction_message.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/entity_module.rs b/generated-clients/core-api-client/async-client/src/models/entity_module.rs index 8e4810a..e0f61b6 100644 --- a/generated-clients/core-api-client/async-client/src/models/entity_module.rs +++ b/generated-clients/core-api-client/async-client/src/models/entity_module.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/entity_reference.rs b/generated-clients/core-api-client/async-client/src/models/entity_reference.rs index 2760914..e4fa353 100644 --- a/generated-clients/core-api-client/async-client/src/models/entity_reference.rs +++ b/generated-clients/core-api-client/async-client/src/models/entity_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/entity_type.rs b/generated-clients/core-api-client/async-client/src/models/entity_type.rs index 0a72a63..f3cc3cd 100644 --- a/generated-clients/core-api-client/async-client/src/models/entity_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/entity_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,7 +11,8 @@ use crate::models; use serde::{Deserialize, Serialize}; -/// +/// EntityType : To improve clarity, some `EntityType` names have been updated at Cuttlefish. But, due to backwards compatibility, the old names continue to be used here. Notably: * `GlobalVirtualSecp256k1Account` is now `GlobalPreallocatedSecp256k1Account` elsewhere * `GlobalVirtualSecp256k1Identity` is now `GlobalPreallocatedSecp256k1Identity` elsewhere * `GlobalVirtualEd25519Account` is now `GlobalPreallocatedEd25519Account` elsewhere * `GlobalVirtualEd25519Identity` is now `GlobalPreallocatedEd25519Identity` elsewhere +/// To improve clarity, some `EntityType` names have been updated at Cuttlefish. But, due to backwards compatibility, the old names continue to be used here. Notably: * `GlobalVirtualSecp256k1Account` is now `GlobalPreallocatedSecp256k1Account` elsewhere * `GlobalVirtualSecp256k1Identity` is now `GlobalPreallocatedSecp256k1Identity` elsewhere * `GlobalVirtualEd25519Account` is now `GlobalPreallocatedEd25519Account` elsewhere * `GlobalVirtualEd25519Identity` is now `GlobalPreallocatedEd25519Identity` elsewhere #[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] pub enum EntityType { #[serde(rename = "GlobalPackage")] diff --git a/generated-clients/core-api-client/async-client/src/models/epoch_change_condition.rs b/generated-clients/core-api-client/async-client/src/models/epoch_change_condition.rs index bd0174f..4b78c1a 100644 --- a/generated-clients/core-api-client/async-client/src/models/epoch_change_condition.rs +++ b/generated-clients/core-api-client/async-client/src/models/epoch_change_condition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/epoch_end_ledger_proof.rs b/generated-clients/core-api-client/async-client/src/models/epoch_end_ledger_proof.rs index 0daf347..59acf2f 100644 --- a/generated-clients/core-api-client/async-client/src/models/epoch_end_ledger_proof.rs +++ b/generated-clients/core-api-client/async-client/src/models/epoch_end_ledger_proof.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/epoch_round.rs b/generated-clients/core-api-client/async-client/src/models/epoch_round.rs index 960f41d..2465aa4 100644 --- a/generated-clients/core-api-client/async-client/src/models/epoch_round.rs +++ b/generated-clients/core-api-client/async-client/src/models/epoch_round.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/error_response.rs b/generated-clients/core-api-client/async-client/src/models/error_response.rs index e0e02d5..2e6690b 100644 --- a/generated-clients/core-api-client/async-client/src/models/error_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -20,6 +20,8 @@ pub enum ErrorResponse { TransactionSubmit(models::TransactionSubmitErrorResponse), #[serde(rename="LtsTransactionSubmit")] LtsTransactionSubmit(models::LtsTransactionSubmitErrorResponse), + #[serde(rename="TransactionPreviewV2")] + TransactionPreviewV2(models::TransactionPreviewV2ErrorResponse), #[serde(rename="StreamTransactions")] StreamTransactions(models::StreamTransactionsErrorResponse), #[serde(rename="StreamProofs")] diff --git a/generated-clients/core-api-client/async-client/src/models/error_response_type.rs b/generated-clients/core-api-client/async-client/src/models/error_response_type.rs index 2e81f5f..1d3e2ae 100644 --- a/generated-clients/core-api-client/async-client/src/models/error_response_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/error_response_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -20,6 +20,8 @@ pub enum ErrorResponseType { TransactionSubmit, #[serde(rename = "LtsTransactionSubmit")] LtsTransactionSubmit, + #[serde(rename = "TransactionPreviewV2")] + TransactionPreviewV2, #[serde(rename = "StreamTransactions")] StreamTransactions, #[serde(rename = "StreamProofs")] @@ -33,6 +35,7 @@ impl std::fmt::Display for ErrorResponseType { Self::Basic => write!(f, "Basic"), Self::TransactionSubmit => write!(f, "TransactionSubmit"), Self::LtsTransactionSubmit => write!(f, "LtsTransactionSubmit"), + Self::TransactionPreviewV2 => write!(f, "TransactionPreviewV2"), Self::StreamTransactions => write!(f, "StreamTransactions"), Self::StreamProofs => write!(f, "StreamProofs"), } diff --git a/generated-clients/core-api-client/async-client/src/models/event.rs b/generated-clients/core-api-client/async-client/src/models/event.rs index 94c93f1..7af7dfa 100644 --- a/generated-clients/core-api-client/async-client/src/models/event.rs +++ b/generated-clients/core-api-client/async-client/src/models/event.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/event_emitter_identifier.rs b/generated-clients/core-api-client/async-client/src/models/event_emitter_identifier.rs index f4601e9..ac48071 100644 --- a/generated-clients/core-api-client/async-client/src/models/event_emitter_identifier.rs +++ b/generated-clients/core-api-client/async-client/src/models/event_emitter_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/event_emitter_identifier_type.rs b/generated-clients/core-api-client/async-client/src/models/event_emitter_identifier_type.rs index baa5d71..d53fff0 100644 --- a/generated-clients/core-api-client/async-client/src/models/event_emitter_identifier_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/event_emitter_identifier_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/event_type_identifier.rs b/generated-clients/core-api-client/async-client/src/models/event_type_identifier.rs index 6c8b947..26bcad7 100644 --- a/generated-clients/core-api-client/async-client/src/models/event_type_identifier.rs +++ b/generated-clients/core-api-client/async-client/src/models/event_type_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/executed_scenario.rs b/generated-clients/core-api-client/async-client/src/models/executed_scenario.rs index ffe808f..417c19d 100644 --- a/generated-clients/core-api-client/async-client/src/models/executed_scenario.rs +++ b/generated-clients/core-api-client/async-client/src/models/executed_scenario.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/executed_scenario_transaction.rs b/generated-clients/core-api-client/async-client/src/models/executed_scenario_transaction.rs index bc07b44..b29a5bc 100644 --- a/generated-clients/core-api-client/async-client/src/models/executed_scenario_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/executed_scenario_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fee_destination.rs b/generated-clients/core-api-client/async-client/src/models/fee_destination.rs index 1b6199b..0f71049 100644 --- a/generated-clients/core-api-client/async-client/src/models/fee_destination.rs +++ b/generated-clients/core-api-client/async-client/src/models/fee_destination.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fee_source.rs b/generated-clients/core-api-client/async-client/src/models/fee_source.rs index 2d10612..9ceaab1 100644 --- a/generated-clients/core-api-client/async-client/src/models/fee_source.rs +++ b/generated-clients/core-api-client/async-client/src/models/fee_source.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fee_summary.rs b/generated-clients/core-api-client/async-client/src/models/fee_summary.rs index 9b62a63..0290bd6 100644 --- a/generated-clients/core-api-client/async-client/src/models/fee_summary.rs +++ b/generated-clients/core-api-client/async-client/src/models/fee_summary.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/field_schema.rs b/generated-clients/core-api-client/async-client/src/models/field_schema.rs index 0c4edc1..e7982e1 100644 --- a/generated-clients/core-api-client/async-client/src/models/field_schema.rs +++ b/generated-clients/core-api-client/async-client/src/models/field_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition.rs b/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition.rs index a015a56..6a9cbaa 100644 --- a/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition.rs +++ b/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_if_outer_object_feature.rs b/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_if_outer_object_feature.rs index 8a9df1e..e9e803f 100644 --- a/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_if_outer_object_feature.rs +++ b/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_if_outer_object_feature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_if_own_feature.rs b/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_if_own_feature.rs index a67f7cc..8e4f1fe 100644 --- a/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_if_own_feature.rs +++ b/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_if_own_feature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_type.rs b/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_type.rs index 472a9c2..c99b56e 100644 --- a/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/field_schema_feature_condition_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/field_substate_key.rs b/generated-clients/core-api-client/async-client/src/models/field_substate_key.rs index e4496f0..8e4c8d5 100644 --- a/generated-clients/core-api-client/async-client/src/models/field_substate_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/field_substate_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/flash_ledger_transaction.rs b/generated-clients/core-api-client/async-client/src/models/flash_ledger_transaction.rs index 9ef8615..76f20f4 100644 --- a/generated-clients/core-api-client/async-client/src/models/flash_ledger_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/flash_ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/flash_set_substate.rs b/generated-clients/core-api-client/async-client/src/models/flash_set_substate.rs index 8cd435c..aece4a9 100644 --- a/generated-clients/core-api-client/async-client/src/models/flash_set_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/flash_set_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/flashed_state_updates.rs b/generated-clients/core-api-client/async-client/src/models/flashed_state_updates.rs index 0a27677..8545a88 100644 --- a/generated-clients/core-api-client/async-client/src/models/flashed_state_updates.rs +++ b/generated-clients/core-api-client/async-client/src/models/flashed_state_updates.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/frozen_status.rs b/generated-clients/core-api-client/async-client/src/models/frozen_status.rs index 0db9af5..b455d79 100644 --- a/generated-clients/core-api-client/async-client/src/models/frozen_status.rs +++ b/generated-clients/core-api-client/async-client/src/models/frozen_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fully_scoped_type_id.rs b/generated-clients/core-api-client/async-client/src/models/fully_scoped_type_id.rs index d430e47..3137e3c 100644 --- a/generated-clients/core-api-client/async-client/src/models/fully_scoped_type_id.rs +++ b/generated-clients/core-api-client/async-client/src/models/fully_scoped_type_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/function_auth_type.rs b/generated-clients/core-api-client/async-client/src/models/function_auth_type.rs index a77a680..537120f 100644 --- a/generated-clients/core-api-client/async-client/src/models/function_auth_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/function_auth_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/function_event_emitter_identifier.rs b/generated-clients/core-api-client/async-client/src/models/function_event_emitter_identifier.rs index 84b6d1a..5f95c9f 100644 --- a/generated-clients/core-api-client/async-client/src/models/function_event_emitter_identifier.rs +++ b/generated-clients/core-api-client/async-client/src/models/function_event_emitter_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/function_schema.rs b/generated-clients/core-api-client/async-client/src/models/function_schema.rs index 891cfc1..3ba2214 100644 --- a/generated-clients/core-api-client/async-client/src/models/function_schema.rs +++ b/generated-clients/core-api-client/async-client/src/models/function_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fungible_resource_amount.rs b/generated-clients/core-api-client/async-client/src/models/fungible_resource_amount.rs index 906585c..a80ea3e 100644 --- a/generated-clients/core-api-client/async-client/src/models/fungible_resource_amount.rs +++ b/generated-clients/core-api-client/async-client/src/models/fungible_resource_amount.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_divisibility_substate.rs b/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_divisibility_substate.rs index c92ecbf..3711d46 100644 --- a/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_divisibility_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_divisibility_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_divisibility_value.rs b/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_divisibility_value.rs index 576ab40..e97b265 100644 --- a/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_divisibility_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_divisibility_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_total_supply_substate.rs b/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_total_supply_substate.rs index 181cad2..5fc29e2 100644 --- a/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_total_supply_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_total_supply_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_total_supply_value.rs b/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_total_supply_value.rs index 4d78f48..9ef468e 100644 --- a/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_total_supply_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/fungible_resource_manager_field_total_supply_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_balance_substate.rs b/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_balance_substate.rs index 96c8682..2572ad8 100644 --- a/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_balance_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_balance_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_balance_value.rs b/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_balance_value.rs index e7d82a1..daaa3ad 100644 --- a/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_balance_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_balance_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_frozen_status_substate.rs b/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_frozen_status_substate.rs index 3bd23d3..df3ab65 100644 --- a/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_frozen_status_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_frozen_status_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_frozen_status_value.rs b/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_frozen_status_value.rs index 56ce5ae..2ce63f6 100644 --- a/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_frozen_status_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/fungible_vault_field_frozen_status_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/generic_blueprint_payload_def.rs b/generated-clients/core-api-client/async-client/src/models/generic_blueprint_payload_def.rs index 54f7fa4..76023ff 100644 --- a/generated-clients/core-api-client/async-client/src/models/generic_blueprint_payload_def.rs +++ b/generated-clients/core-api-client/async-client/src/models/generic_blueprint_payload_def.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/generic_key.rs b/generated-clients/core-api-client/async-client/src/models/generic_key.rs index a9509ba..a2fd877 100644 --- a/generated-clients/core-api-client/async-client/src/models/generic_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/generic_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/generic_key_value_store_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/generic_key_value_store_entry_substate.rs index 3572ce1..58cddb6 100644 --- a/generated-clients/core-api-client/async-client/src/models/generic_key_value_store_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/generic_key_value_store_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/generic_key_value_store_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/generic_key_value_store_entry_value.rs index 816bf7e..4103de1 100644 --- a/generated-clients/core-api-client/async-client/src/models/generic_key_value_store_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/generic_key_value_store_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/generic_scrypto_component_field_state_substate.rs b/generated-clients/core-api-client/async-client/src/models/generic_scrypto_component_field_state_substate.rs index 0ed46aa..6ef3b0f 100644 --- a/generated-clients/core-api-client/async-client/src/models/generic_scrypto_component_field_state_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/generic_scrypto_component_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/generic_scrypto_component_field_state_value.rs b/generated-clients/core-api-client/async-client/src/models/generic_scrypto_component_field_state_value.rs index 4349aef..58fd287 100644 --- a/generated-clients/core-api-client/async-client/src/models/generic_scrypto_component_field_state_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/generic_scrypto_component_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/generic_substitution.rs b/generated-clients/core-api-client/async-client/src/models/generic_substitution.rs index 0ee1095..1bb1176 100644 --- a/generated-clients/core-api-client/async-client/src/models/generic_substitution.rs +++ b/generated-clients/core-api-client/async-client/src/models/generic_substitution.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/generic_substitution_type.rs b/generated-clients/core-api-client/async-client/src/models/generic_substitution_type.rs index 69f1ae5..7e4b08e 100644 --- a/generated-clients/core-api-client/async-client/src/models/generic_substitution_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/generic_substitution_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/generic_type_parameter.rs b/generated-clients/core-api-client/async-client/src/models/generic_type_parameter.rs index 7af9bd3..248a2d1 100644 --- a/generated-clients/core-api-client/async-client/src/models/generic_type_parameter.rs +++ b/generated-clients/core-api-client/async-client/src/models/generic_type_parameter.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/generic_type_parameter_constraints.rs b/generated-clients/core-api-client/async-client/src/models/generic_type_parameter_constraints.rs index 2fb33b9..a93e3e3 100644 --- a/generated-clients/core-api-client/async-client/src/models/generic_type_parameter_constraints.rs +++ b/generated-clients/core-api-client/async-client/src/models/generic_type_parameter_constraints.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/genesis_ledger_proof_origin.rs b/generated-clients/core-api-client/async-client/src/models/genesis_ledger_proof_origin.rs index 6482120..96f62a4 100644 --- a/generated-clients/core-api-client/async-client/src/models/genesis_ledger_proof_origin.rs +++ b/generated-clients/core-api-client/async-client/src/models/genesis_ledger_proof_origin.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/genesis_ledger_transaction.rs b/generated-clients/core-api-client/async-client/src/models/genesis_ledger_transaction.rs index be078da..b07c689 100644 --- a/generated-clients/core-api-client/async-client/src/models/genesis_ledger_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/genesis_ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/hook_export.rs b/generated-clients/core-api-client/async-client/src/models/hook_export.rs index 9ad12b2..50588a8 100644 --- a/generated-clients/core-api-client/async-client/src/models/hook_export.rs +++ b/generated-clients/core-api-client/async-client/src/models/hook_export.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/in_progress_protocol_update_status.rs b/generated-clients/core-api-client/async-client/src/models/in_progress_protocol_update_status.rs index 1923ff9..200dedf 100644 --- a/generated-clients/core-api-client/async-client/src/models/in_progress_protocol_update_status.rs +++ b/generated-clients/core-api-client/async-client/src/models/in_progress_protocol_update_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/index_blueprint_collection_schema.rs b/generated-clients/core-api-client/async-client/src/models/index_blueprint_collection_schema.rs index dfc1829..f2bae3e 100644 --- a/generated-clients/core-api-client/async-client/src/models/index_blueprint_collection_schema.rs +++ b/generated-clients/core-api-client/async-client/src/models/index_blueprint_collection_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/indexed_state_schema.rs b/generated-clients/core-api-client/async-client/src/models/indexed_state_schema.rs index e5c23b2..3fe90ee 100644 --- a/generated-clients/core-api-client/async-client/src/models/indexed_state_schema.rs +++ b/generated-clients/core-api-client/async-client/src/models/indexed_state_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/instance_schema_blueprint_type_reference.rs b/generated-clients/core-api-client/async-client/src/models/instance_schema_blueprint_type_reference.rs index cad0c6b..9c8d820 100644 --- a/generated-clients/core-api-client/async-client/src/models/instance_schema_blueprint_type_reference.rs +++ b/generated-clients/core-api-client/async-client/src/models/instance_schema_blueprint_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/instant_ms.rs b/generated-clients/core-api-client/async-client/src/models/instant_ms.rs index 5649adb..299fe12 100644 --- a/generated-clients/core-api-client/async-client/src/models/instant_ms.rs +++ b/generated-clients/core-api-client/async-client/src/models/instant_ms.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/instruction_resource_changes.rs b/generated-clients/core-api-client/async-client/src/models/instruction_resource_changes.rs index 287505e..8a9818e 100644 --- a/generated-clients/core-api-client/async-client/src/models/instruction_resource_changes.rs +++ b/generated-clients/core-api-client/async-client/src/models/instruction_resource_changes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/intent_core_v2.rs b/generated-clients/core-api-client/async-client/src/models/intent_core_v2.rs index e8d7020..30e09f5 100644 --- a/generated-clients/core-api-client/async-client/src/models/intent_core_v2.rs +++ b/generated-clients/core-api-client/async-client/src/models/intent_core_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/intent_header_v2.rs b/generated-clients/core-api-client/async-client/src/models/intent_header_v2.rs index e3d6873..9cbbf50 100644 --- a/generated-clients/core-api-client/async-client/src/models/intent_header_v2.rs +++ b/generated-clients/core-api-client/async-client/src/models/intent_header_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/intent_signatures.rs b/generated-clients/core-api-client/async-client/src/models/intent_signatures.rs index 49b8499..75f706f 100644 --- a/generated-clients/core-api-client/async-client/src/models/intent_signatures.rs +++ b/generated-clients/core-api-client/async-client/src/models/intent_signatures.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/invalid_transaction_preview_v2_error_details.rs b/generated-clients/core-api-client/async-client/src/models/invalid_transaction_preview_v2_error_details.rs new file mode 100644 index 0000000..fb14a34 --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/invalid_transaction_preview_v2_error_details.rs @@ -0,0 +1,27 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct InvalidTransactionPreviewV2ErrorDetails { + #[serde(rename = "validation_error")] + pub validation_error: String, +} + +impl InvalidTransactionPreviewV2ErrorDetails { + pub fn new(validation_error: String) -> InvalidTransactionPreviewV2ErrorDetails { + InvalidTransactionPreviewV2ErrorDetails { + validation_error, + } + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/key_value_based_structure.rs b/generated-clients/core-api-client/async-client/src/models/key_value_based_structure.rs index 80e0644..c099f93 100644 --- a/generated-clients/core-api-client/async-client/src/models/key_value_based_structure.rs +++ b/generated-clients/core-api-client/async-client/src/models/key_value_based_structure.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/key_value_blueprint_collection_schema.rs b/generated-clients/core-api-client/async-client/src/models/key_value_blueprint_collection_schema.rs index 523d1e2..f991765 100644 --- a/generated-clients/core-api-client/async-client/src/models/key_value_blueprint_collection_schema.rs +++ b/generated-clients/core-api-client/async-client/src/models/key_value_blueprint_collection_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/key_value_store_entry_structure.rs b/generated-clients/core-api-client/async-client/src/models/key_value_store_entry_structure.rs index 9a9851a..9d694a7 100644 --- a/generated-clients/core-api-client/async-client/src/models/key_value_store_entry_structure.rs +++ b/generated-clients/core-api-client/async-client/src/models/key_value_store_entry_structure.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/key_value_store_info.rs b/generated-clients/core-api-client/async-client/src/models/key_value_store_info.rs index 0d10fff..a1a1184 100644 --- a/generated-clients/core-api-client/async-client/src/models/key_value_store_info.rs +++ b/generated-clients/core-api-client/async-client/src/models/key_value_store_info.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/key_value_store_type_info_details.rs b/generated-clients/core-api-client/async-client/src/models/key_value_store_type_info_details.rs index acb72f2..0294134 100644 --- a/generated-clients/core-api-client/async-client/src/models/key_value_store_type_info_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/key_value_store_type_info_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/leader_proposal_history.rs b/generated-clients/core-api-client/async-client/src/models/leader_proposal_history.rs index 58986ec..58964b5 100644 --- a/generated-clients/core-api-client/async-client/src/models/leader_proposal_history.rs +++ b/generated-clients/core-api-client/async-client/src/models/leader_proposal_history.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ledger_hashes.rs b/generated-clients/core-api-client/async-client/src/models/ledger_hashes.rs index c9f4292..e8e4f84 100644 --- a/generated-clients/core-api-client/async-client/src/models/ledger_hashes.rs +++ b/generated-clients/core-api-client/async-client/src/models/ledger_hashes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ledger_header.rs b/generated-clients/core-api-client/async-client/src/models/ledger_header.rs index 98a12d9..5fc68dc 100644 --- a/generated-clients/core-api-client/async-client/src/models/ledger_header.rs +++ b/generated-clients/core-api-client/async-client/src/models/ledger_header.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ledger_header_summary.rs b/generated-clients/core-api-client/async-client/src/models/ledger_header_summary.rs index 0c54901..239a33f 100644 --- a/generated-clients/core-api-client/async-client/src/models/ledger_header_summary.rs +++ b/generated-clients/core-api-client/async-client/src/models/ledger_header_summary.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ledger_proof.rs b/generated-clients/core-api-client/async-client/src/models/ledger_proof.rs index 370c3d2..e7315c0 100644 --- a/generated-clients/core-api-client/async-client/src/models/ledger_proof.rs +++ b/generated-clients/core-api-client/async-client/src/models/ledger_proof.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ledger_proof_origin.rs b/generated-clients/core-api-client/async-client/src/models/ledger_proof_origin.rs index 1632619..43d217c 100644 --- a/generated-clients/core-api-client/async-client/src/models/ledger_proof_origin.rs +++ b/generated-clients/core-api-client/async-client/src/models/ledger_proof_origin.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ledger_proof_origin_type.rs b/generated-clients/core-api-client/async-client/src/models/ledger_proof_origin_type.rs index 20ef4dd..3907d62 100644 --- a/generated-clients/core-api-client/async-client/src/models/ledger_proof_origin_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/ledger_proof_origin_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ledger_state_selector.rs b/generated-clients/core-api-client/async-client/src/models/ledger_state_selector.rs index 2906f86..09d436f 100644 --- a/generated-clients/core-api-client/async-client/src/models/ledger_state_selector.rs +++ b/generated-clients/core-api-client/async-client/src/models/ledger_state_selector.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ledger_state_selector_type.rs b/generated-clients/core-api-client/async-client/src/models/ledger_state_selector_type.rs index 86e52d5..5b8dbf5 100644 --- a/generated-clients/core-api-client/async-client/src/models/ledger_state_selector_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/ledger_state_selector_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ledger_state_summary.rs b/generated-clients/core-api-client/async-client/src/models/ledger_state_summary.rs index 76e5a00..5250a45 100644 --- a/generated-clients/core-api-client/async-client/src/models/ledger_state_summary.rs +++ b/generated-clients/core-api-client/async-client/src/models/ledger_state_summary.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ledger_transaction.rs b/generated-clients/core-api-client/async-client/src/models/ledger_transaction.rs index de5d4ab..ae9e7d0 100644 --- a/generated-clients/core-api-client/async-client/src/models/ledger_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/ledger_transaction_type.rs b/generated-clients/core-api-client/async-client/src/models/ledger_transaction_type.rs index a80cd57..0433b8a 100644 --- a/generated-clients/core-api-client/async-client/src/models/ledger_transaction_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/ledger_transaction_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/limit_parameters.rs b/generated-clients/core-api-client/async-client/src/models/limit_parameters.rs index 1e30219..ad5e528 100644 --- a/generated-clients/core-api-client/async-client/src/models/limit_parameters.rs +++ b/generated-clients/core-api-client/async-client/src/models/limit_parameters.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/local_generic_substitution.rs b/generated-clients/core-api-client/async-client/src/models/local_generic_substitution.rs index fa35e17..fc1e03b 100644 --- a/generated-clients/core-api-client/async-client/src/models/local_generic_substitution.rs +++ b/generated-clients/core-api-client/async-client/src/models/local_generic_substitution.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/local_non_fungible_key.rs b/generated-clients/core-api-client/async-client/src/models/local_non_fungible_key.rs index ea4535e..e078775 100644 --- a/generated-clients/core-api-client/async-client/src/models/local_non_fungible_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/local_non_fungible_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/local_type_id.rs b/generated-clients/core-api-client/async-client/src/models/local_type_id.rs index 9ab3ce1..6f8dc1a 100644 --- a/generated-clients/core-api-client/async-client/src/models/local_type_id.rs +++ b/generated-clients/core-api-client/async-client/src/models/local_type_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_committed_transaction_outcome.rs b/generated-clients/core-api-client/async-client/src/models/lts_committed_transaction_outcome.rs index 795ec53..e052577 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_committed_transaction_outcome.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_committed_transaction_outcome.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_committed_transaction_status.rs b/generated-clients/core-api-client/async-client/src/models/lts_committed_transaction_status.rs index f8fde21..56d8e76 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_committed_transaction_status.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_committed_transaction_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_entity_fungible_balance_changes.rs b/generated-clients/core-api-client/async-client/src/models/lts_entity_fungible_balance_changes.rs index 2081fa7..e5e5e92 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_entity_fungible_balance_changes.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_entity_fungible_balance_changes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_entity_non_fungible_balance_changes.rs b/generated-clients/core-api-client/async-client/src/models/lts_entity_non_fungible_balance_changes.rs index 97911f8..c204a37 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_entity_non_fungible_balance_changes.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_entity_non_fungible_balance_changes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_fee_fungible_resource_balance_change.rs b/generated-clients/core-api-client/async-client/src/models/lts_fee_fungible_resource_balance_change.rs index 595f05d..15ed6ef 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_fee_fungible_resource_balance_change.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_fee_fungible_resource_balance_change.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_fee_fungible_resource_balance_change_type.rs b/generated-clients/core-api-client/async-client/src/models/lts_fee_fungible_resource_balance_change_type.rs index a66db06..266c849 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_fee_fungible_resource_balance_change_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_fee_fungible_resource_balance_change_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_fungible_resource_balance.rs b/generated-clients/core-api-client/async-client/src/models/lts_fungible_resource_balance.rs index 93c32ca..c185809 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_fungible_resource_balance.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_fungible_resource_balance.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_fungible_resource_balance_change.rs b/generated-clients/core-api-client/async-client/src/models/lts_fungible_resource_balance_change.rs index 999a44f..89f10c6 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_fungible_resource_balance_change.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_fungible_resource_balance_change.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_resultant_account_fungible_balances.rs b/generated-clients/core-api-client/async-client/src/models/lts_resultant_account_fungible_balances.rs index 23bbc0c..2fadd1f 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_resultant_account_fungible_balances.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_resultant_account_fungible_balances.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_resultant_fungible_balance.rs b/generated-clients/core-api-client/async-client/src/models/lts_resultant_fungible_balance.rs index f18621a..fa3203f 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_resultant_fungible_balance.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_resultant_fungible_balance.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_state_account_all_fungible_resource_balances_request.rs b/generated-clients/core-api-client/async-client/src/models/lts_state_account_all_fungible_resource_balances_request.rs index bdc8518..745b4d6 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_state_account_all_fungible_resource_balances_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_state_account_all_fungible_resource_balances_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_state_account_all_fungible_resource_balances_response.rs b/generated-clients/core-api-client/async-client/src/models/lts_state_account_all_fungible_resource_balances_response.rs index 240fa2e..6b48eec 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_state_account_all_fungible_resource_balances_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_state_account_all_fungible_resource_balances_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_state_account_deposit_behaviour_request.rs b/generated-clients/core-api-client/async-client/src/models/lts_state_account_deposit_behaviour_request.rs index e603a7c..ba60db7 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_state_account_deposit_behaviour_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_state_account_deposit_behaviour_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_state_account_deposit_behaviour_response.rs b/generated-clients/core-api-client/async-client/src/models/lts_state_account_deposit_behaviour_response.rs index d980fa3..4fe49c4 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_state_account_deposit_behaviour_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_state_account_deposit_behaviour_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_state_account_fungible_resource_balance_request.rs b/generated-clients/core-api-client/async-client/src/models/lts_state_account_fungible_resource_balance_request.rs index 82512a2..5640730 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_state_account_fungible_resource_balance_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_state_account_fungible_resource_balance_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_state_account_fungible_resource_balance_response.rs b/generated-clients/core-api-client/async-client/src/models/lts_state_account_fungible_resource_balance_response.rs index 6dc53c3..5a92c8c 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_state_account_fungible_resource_balance_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_state_account_fungible_resource_balance_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_stream_account_transaction_outcomes_request.rs b/generated-clients/core-api-client/async-client/src/models/lts_stream_account_transaction_outcomes_request.rs index 5f4a0ab..02379f3 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_stream_account_transaction_outcomes_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_stream_account_transaction_outcomes_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_stream_account_transaction_outcomes_response.rs b/generated-clients/core-api-client/async-client/src/models/lts_stream_account_transaction_outcomes_response.rs index ac7a713..98017fc 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_stream_account_transaction_outcomes_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_stream_account_transaction_outcomes_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_stream_transaction_outcomes_request.rs b/generated-clients/core-api-client/async-client/src/models/lts_stream_transaction_outcomes_request.rs index 16f8da8..0e24ec0 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_stream_transaction_outcomes_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_stream_transaction_outcomes_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_stream_transaction_outcomes_response.rs b/generated-clients/core-api-client/async-client/src/models/lts_stream_transaction_outcomes_response.rs index 384527a..eeac9d0 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_stream_transaction_outcomes_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_stream_transaction_outcomes_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_construction_request.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_construction_request.rs index f482e5d..36cb7db 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_construction_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_construction_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_construction_response.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_construction_response.rs index 9bb96bf..59c6ca5 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_construction_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_construction_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_intent_status.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_intent_status.rs index fcab6b5..7dceab9 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_intent_status.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_intent_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_payload_details.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_payload_details.rs index ca520d7..e3ea533 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_payload_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_payload_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_payload_status.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_payload_status.rs index af6a202..c34dc12 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_payload_status.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_payload_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_status_request.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_status_request.rs index ecf94bf..a81c5a1 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_status_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_status_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_status_response.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_status_response.rs index e38adbc..a252d9b 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_status_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_status_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_details.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_details.rs index bfc1c76..55dc3a9 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_details_type.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_details_type.rs index 94a554e..1aab9ba 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_details_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_details_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_response.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_response.rs index 3eaccda..b3a2060 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_intent_already_committed.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_intent_already_committed.rs index 393eb99..8c1ee2a 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_intent_already_committed.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_intent_already_committed.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs index 31794ed..3b55916 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -13,19 +13,27 @@ use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] pub struct LtsTransactionSubmitPriorityThresholdNotMetErrorDetails { - /// A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. + /// NOTE: This is kept for backwards compatibility, but we recommend using `min_tip_proportion_required` instead. A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. #[serde(rename = "min_tip_percentage_required", skip_serializing_if = "Option::is_none")] pub min_tip_percentage_required: Option, - /// Tip percentage of the submitted (and rejected) transaction. + /// A lower bound for tip proportion at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. + #[serde(rename = "min_tip_proportion_required", skip_serializing_if = "Option::is_none")] + pub min_tip_proportion_required: Option, + /// NOTE: This is kept for backwards compatibility, but we recommend using `tip_proportion` instead. Tip percentage of the submitted (and rejected) transaction. For V2 transactions specifying basis point tips, the amount is rounded down. #[serde(rename = "tip_percentage")] pub tip_percentage: u32, + /// The string-encoded decimal tip proportion of the submitted (and rejected) transaction. This field will always be present on Cuttlefish nodes, but is marked as not-required for Cuttlefish launch, to avoid a dependency on clients to update after the node is updated. + #[serde(rename = "tip_proportion", skip_serializing_if = "Option::is_none")] + pub tip_proportion: Option, } impl LtsTransactionSubmitPriorityThresholdNotMetErrorDetails { pub fn new(tip_percentage: u32) -> LtsTransactionSubmitPriorityThresholdNotMetErrorDetails { LtsTransactionSubmitPriorityThresholdNotMetErrorDetails { min_tip_percentage_required: None, + min_tip_proportion_required: None, tip_percentage, + tip_proportion: None, } } } diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_rejected_error_details.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_rejected_error_details.rs index 8ff6a5d..6ac067d 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_rejected_error_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_rejected_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_request.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_request.rs index 7cc864e..2951b8d 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_response.rs b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_response.rs index 80bead5..82fa6f0 100644 --- a/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/lts_transaction_submit_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/main_method_key.rs b/generated-clients/core-api-client/async-client/src/models/main_method_key.rs index 7f1959f..0b0b591 100644 --- a/generated-clients/core-api-client/async-client/src/models/main_method_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/main_method_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/manifest_validation_ruleset.rs b/generated-clients/core-api-client/async-client/src/models/manifest_validation_ruleset.rs new file mode 100644 index 0000000..96308e9 --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/manifest_validation_ruleset.rs @@ -0,0 +1,38 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +/// +#[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] +pub enum ManifestValidationRuleset { + #[serde(rename = "Basic")] + Basic, + #[serde(rename = "Cuttlefish")] + Cuttlefish, + +} + +impl std::fmt::Display for ManifestValidationRuleset { + fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { + match self { + Self::Basic => write!(f, "Basic"), + Self::Cuttlefish => write!(f, "Cuttlefish"), + } + } +} + +impl Default for ManifestValidationRuleset { + fn default() -> ManifestValidationRuleset { + Self::Basic + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/map_substate_key.rs b/generated-clients/core-api-client/async-client/src/models/map_substate_key.rs index 8ac2aa2..0473451 100644 --- a/generated-clients/core-api-client/async-client/src/models/map_substate_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/map_substate_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/mempool_list_request.rs b/generated-clients/core-api-client/async-client/src/models/mempool_list_request.rs index b6c81cb..4ffe6ca 100644 --- a/generated-clients/core-api-client/async-client/src/models/mempool_list_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/mempool_list_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/mempool_list_response.rs b/generated-clients/core-api-client/async-client/src/models/mempool_list_response.rs index 49f5d50..3102386 100644 --- a/generated-clients/core-api-client/async-client/src/models/mempool_list_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/mempool_list_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/mempool_transaction_hashes.rs b/generated-clients/core-api-client/async-client/src/models/mempool_transaction_hashes.rs index 2b22f3d..8110875 100644 --- a/generated-clients/core-api-client/async-client/src/models/mempool_transaction_hashes.rs +++ b/generated-clients/core-api-client/async-client/src/models/mempool_transaction_hashes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/mempool_transaction_request.rs b/generated-clients/core-api-client/async-client/src/models/mempool_transaction_request.rs index ea8e487..1d80e34 100644 --- a/generated-clients/core-api-client/async-client/src/models/mempool_transaction_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/mempool_transaction_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/mempool_transaction_response.rs b/generated-clients/core-api-client/async-client/src/models/mempool_transaction_response.rs index b9833fe..99c24ac 100644 --- a/generated-clients/core-api-client/async-client/src/models/mempool_transaction_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/mempool_transaction_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/mempool_transaction_response_payloads_inner.rs b/generated-clients/core-api-client/async-client/src/models/mempool_transaction_response_payloads_inner.rs index 328ae9b..c7caf1b 100644 --- a/generated-clients/core-api-client/async-client/src/models/mempool_transaction_response_payloads_inner.rs +++ b/generated-clients/core-api-client/async-client/src/models/mempool_transaction_response_payloads_inner.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/message_validation_config.rs b/generated-clients/core-api-client/async-client/src/models/message_validation_config.rs new file mode 100644 index 0000000..b1852f7 --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/message_validation_config.rs @@ -0,0 +1,36 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct MessageValidationConfig { + #[serde(rename = "max_decryptors")] + pub max_decryptors: String, + #[serde(rename = "max_encrypted_message_length")] + pub max_encrypted_message_length: String, + #[serde(rename = "max_mime_type_length")] + pub max_mime_type_length: String, + #[serde(rename = "max_plaintext_message_length")] + pub max_plaintext_message_length: String, +} + +impl MessageValidationConfig { + pub fn new(max_decryptors: String, max_encrypted_message_length: String, max_mime_type_length: String, max_plaintext_message_length: String) -> MessageValidationConfig { + MessageValidationConfig { + max_decryptors, + max_encrypted_message_length, + max_mime_type_length, + max_plaintext_message_length, + } + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/metadata_key.rs b/generated-clients/core-api-client/async-client/src/models/metadata_key.rs index a3b98eb..9d4f7e9 100644 --- a/generated-clients/core-api-client/async-client/src/models/metadata_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/metadata_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/metadata_module_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/metadata_module_entry_substate.rs index 2f5e51f..45d29a6 100644 --- a/generated-clients/core-api-client/async-client/src/models/metadata_module_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/metadata_module_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/metadata_module_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/metadata_module_entry_value.rs index 0c53333..fc85f3b 100644 --- a/generated-clients/core-api-client/async-client/src/models/metadata_module_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/metadata_module_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/method_accessibility.rs b/generated-clients/core-api-client/async-client/src/models/method_accessibility.rs index bb02a10..b3fc0da 100644 --- a/generated-clients/core-api-client/async-client/src/models/method_accessibility.rs +++ b/generated-clients/core-api-client/async-client/src/models/method_accessibility.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/method_accessibility_type.rs b/generated-clients/core-api-client/async-client/src/models/method_accessibility_type.rs index e74aac7..7f4b793 100644 --- a/generated-clients/core-api-client/async-client/src/models/method_accessibility_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/method_accessibility_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/method_auth_type.rs b/generated-clients/core-api-client/async-client/src/models/method_auth_type.rs index ba1e953..388414b 100644 --- a/generated-clients/core-api-client/async-client/src/models/method_auth_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/method_auth_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/method_event_emitter_identifier.rs b/generated-clients/core-api-client/async-client/src/models/method_event_emitter_identifier.rs index b2979a8..df5c603 100644 --- a/generated-clients/core-api-client/async-client/src/models/method_event_emitter_identifier.rs +++ b/generated-clients/core-api-client/async-client/src/models/method_event_emitter_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/mod.rs b/generated-clients/core-api-client/async-client/src/models/mod.rs index 6ae55d6..d0dfbbf 100644 --- a/generated-clients/core-api-client/async-client/src/models/mod.rs +++ b/generated-clients/core-api-client/async-client/src/models/mod.rs @@ -4,10 +4,6 @@ pub mod access_controller_field_state_value; pub use self::access_controller_field_state_value::AccessControllerFieldStateValue; pub mod access_rule; pub use self::access_rule::AccessRule; -pub mod access_rule_node; -pub use self::access_rule_node::AccessRuleNode; -pub mod access_rule_node_type; -pub use self::access_rule_node_type::AccessRuleNodeType; pub mod access_rule_type; pub use self::access_rule_type::AccessRuleType; pub mod account_address_key; @@ -40,18 +36,18 @@ pub mod active_validator_key; pub use self::active_validator_key::ActiveValidatorKey; pub mod address_type; pub use self::address_type::AddressType; -pub mod all_of_access_rule_node; -pub use self::all_of_access_rule_node::AllOfAccessRuleNode; -pub mod all_of_proof_rule; -pub use self::all_of_proof_rule::AllOfProofRule; +pub mod all_of_basic_requirement; +pub use self::all_of_basic_requirement::AllOfBasicRequirement; +pub mod all_of_composite_requirement; +pub use self::all_of_composite_requirement::AllOfCompositeRequirement; pub mod always_visible_global_nodes_version; pub use self::always_visible_global_nodes_version::AlwaysVisibleGlobalNodesVersion; -pub mod amount_of_proof_rule; -pub use self::amount_of_proof_rule::AmountOfProofRule; -pub mod any_of_access_rule_node; -pub use self::any_of_access_rule_node::AnyOfAccessRuleNode; -pub mod any_of_proof_rule; -pub use self::any_of_proof_rule::AnyOfProofRule; +pub mod amount_of_basic_requirement; +pub use self::amount_of_basic_requirement::AmountOfBasicRequirement; +pub mod any_of_basic_requirement; +pub use self::any_of_basic_requirement::AnyOfBasicRequirement; +pub mod any_of_composite_requirement; +pub use self::any_of_composite_requirement::AnyOfCompositeRequirement; pub mod attached_module_id; pub use self::attached_module_id::AttachedModuleId; pub mod auth_config; @@ -64,6 +60,10 @@ pub mod authorized_depositor_key; pub use self::authorized_depositor_key::AuthorizedDepositorKey; pub mod basic_error_response; pub use self::basic_error_response::BasicErrorResponse; +pub mod basic_requirement; +pub use self::basic_requirement::BasicRequirement; +pub mod basic_requirement_type; +pub use self::basic_requirement_type::BasicRequirementType; pub mod binary_plaintext_message_content; pub use self::binary_plaintext_message_content::BinaryPlaintextMessageContent; pub mod blueprint_collection_schema; @@ -124,8 +124,14 @@ pub mod committed_transaction; pub use self::committed_transaction::CommittedTransaction; pub mod committed_transaction_balance_changes; pub use self::committed_transaction_balance_changes::CommittedTransactionBalanceChanges; +pub mod compiled_preview_transaction; +pub use self::compiled_preview_transaction::CompiledPreviewTransaction; pub mod component_method_target_identifier; pub use self::component_method_target_identifier::ComponentMethodTargetIdentifier; +pub mod composite_requirement; +pub use self::composite_requirement::CompositeRequirement; +pub mod composite_requirement_type; +pub use self::composite_requirement_type::CompositeRequirementType; pub mod consensus_ledger_proof_origin; pub use self::consensus_ledger_proof_origin::ConsensusLedgerProofOrigin; pub mod consensus_manager_field_config_substate; @@ -164,8 +170,8 @@ pub mod costing_module_config; pub use self::costing_module_config::CostingModuleConfig; pub mod costing_parameters; pub use self::costing_parameters::CostingParameters; -pub mod count_of_proof_rule; -pub use self::count_of_proof_rule::CountOfProofRule; +pub mod count_of_basic_requirement; +pub use self::count_of_basic_requirement::CountOfBasicRequirement; pub mod created_substate; pub use self::created_substate::CreatedSubstate; pub mod data_struct; @@ -316,6 +322,8 @@ pub mod intent_header_v2; pub use self::intent_header_v2::IntentHeaderV2; pub mod intent_signatures; pub use self::intent_signatures::IntentSignatures; +pub mod invalid_transaction_preview_v2_error_details; +pub use self::invalid_transaction_preview_v2_error_details::InvalidTransactionPreviewV2ErrorDetails; pub mod key_value_based_structure; pub use self::key_value_based_structure::KeyValueBasedStructure; pub mod key_value_blueprint_collection_schema; @@ -430,6 +438,8 @@ pub mod lts_transaction_submit_response; pub use self::lts_transaction_submit_response::LtsTransactionSubmitResponse; pub mod main_method_key; pub use self::main_method_key::MainMethodKey; +pub mod manifest_validation_ruleset; +pub use self::manifest_validation_ruleset::ManifestValidationRuleset; pub mod map_substate_key; pub use self::map_substate_key::MapSubstateKey; pub mod mempool_list_request; @@ -444,6 +454,8 @@ pub mod mempool_transaction_response; pub use self::mempool_transaction_response::MempoolTransactionResponse; pub mod mempool_transaction_response_payloads_inner; pub use self::mempool_transaction_response_payloads_inner::MempoolTransactionResponsePayloadsInner; +pub mod message_validation_config; +pub use self::message_validation_config::MessageValidationConfig; pub mod metadata_key; pub use self::metadata_key::MetadataKey; pub mod metadata_module_entry_substate; @@ -634,18 +646,22 @@ pub mod plaintext_transaction_message; pub use self::plaintext_transaction_message::PlaintextTransactionMessage; pub mod pool_vault; pub use self::pool_vault::PoolVault; +pub mod preparation_settings; +pub use self::preparation_settings::PreparationSettings; pub mod presented_badge; pub use self::presented_badge::PresentedBadge; pub mod presented_badge_type; pub use self::presented_badge_type::PresentedBadgeType; +pub mod preview_flags; +pub use self::preview_flags::PreviewFlags; +pub mod preview_transaction; +pub use self::preview_transaction::PreviewTransaction; +pub mod preview_transaction_type; +pub use self::preview_transaction_type::PreviewTransactionType; pub mod primary_role_recovery_attempt; pub use self::primary_role_recovery_attempt::PrimaryRoleRecoveryAttempt; -pub mod proof_access_rule_node; -pub use self::proof_access_rule_node::ProofAccessRuleNode; -pub mod proof_rule; -pub use self::proof_rule::ProofRule; -pub mod proof_rule_type; -pub use self::proof_rule_type::ProofRuleType; +pub mod proof_rule_composite_requirement; +pub use self::proof_rule_composite_requirement::ProofRuleCompositeRequirement; pub mod proposer_reward; pub use self::proposer_reward::ProposerReward; pub mod protected_access_rule; @@ -678,8 +694,8 @@ pub mod remote_generic_substitution; pub use self::remote_generic_substitution::RemoteGenericSubstitution; pub mod requested_state_version_out_of_bounds_error_details; pub use self::requested_state_version_out_of_bounds_error_details::RequestedStateVersionOutOfBoundsErrorDetails; -pub mod require_proof_rule; -pub use self::require_proof_rule::RequireProofRule; +pub mod require_basic_requirement; +pub use self::require_basic_requirement::RequireBasicRequirement; pub mod requirement; pub use self::requirement::Requirement; pub mod requirement_type; @@ -922,14 +938,24 @@ pub mod transaction_payload_status; pub use self::transaction_payload_status::TransactionPayloadStatus; pub mod transaction_preview_request; pub use self::transaction_preview_request::TransactionPreviewRequest; -pub mod transaction_preview_request_flags; -pub use self::transaction_preview_request_flags::TransactionPreviewRequestFlags; pub mod transaction_preview_response; pub use self::transaction_preview_response::TransactionPreviewResponse; pub mod transaction_preview_response_logs_inner; pub use self::transaction_preview_response_logs_inner::TransactionPreviewResponseLogsInner; pub mod transaction_preview_response_options; pub use self::transaction_preview_response_options::TransactionPreviewResponseOptions; +pub mod transaction_preview_v2_error_details; +pub use self::transaction_preview_v2_error_details::TransactionPreviewV2ErrorDetails; +pub mod transaction_preview_v2_error_details_type; +pub use self::transaction_preview_v2_error_details_type::TransactionPreviewV2ErrorDetailsType; +pub mod transaction_preview_v2_error_response; +pub use self::transaction_preview_v2_error_response::TransactionPreviewV2ErrorResponse; +pub mod transaction_preview_v2_request; +pub use self::transaction_preview_v2_request::TransactionPreviewV2Request; +pub mod transaction_preview_v2_response; +pub use self::transaction_preview_v2_response::TransactionPreviewV2Response; +pub mod transaction_preview_v2_response_options; +pub use self::transaction_preview_v2_response_options::TransactionPreviewV2ResponseOptions; pub mod transaction_receipt; pub use self::transaction_receipt::TransactionReceipt; pub mod transaction_receipt_request; @@ -968,6 +994,8 @@ pub mod transaction_tracker_field_state_value; pub use self::transaction_tracker_field_state_value::TransactionTrackerFieldStateValue; pub mod transaction_tracker_transaction_status; pub use self::transaction_tracker_transaction_status::TransactionTrackerTransactionStatus; +pub mod transaction_validation_config; +pub use self::transaction_validation_config::TransactionValidationConfig; pub mod two_resource_pool_field_state_substate; pub use self::two_resource_pool_field_state_substate::TwoResourcePoolFieldStateSubstate; pub mod two_resource_pool_field_state_value; diff --git a/generated-clients/core-api-client/async-client/src/models/module_id.rs b/generated-clients/core-api-client/async-client/src/models/module_id.rs index 1af4a29..fb29526 100644 --- a/generated-clients/core-api-client/async-client/src/models/module_id.rs +++ b/generated-clients/core-api-client/async-client/src/models/module_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/module_version.rs b/generated-clients/core-api-client/async-client/src/models/module_version.rs index 04bc27b..f8a134e 100644 --- a/generated-clients/core-api-client/async-client/src/models/module_version.rs +++ b/generated-clients/core-api-client/async-client/src/models/module_version.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/multi_resource_pool_field_state_substate.rs b/generated-clients/core-api-client/async-client/src/models/multi_resource_pool_field_state_substate.rs index 601fe96..135c625 100644 --- a/generated-clients/core-api-client/async-client/src/models/multi_resource_pool_field_state_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/multi_resource_pool_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/multi_resource_pool_field_state_value.rs b/generated-clients/core-api-client/async-client/src/models/multi_resource_pool_field_state_value.rs index 3ec9f84..9cc1a19 100644 --- a/generated-clients/core-api-client/async-client/src/models/multi_resource_pool_field_state_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/multi_resource_pool_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/mutable_field.rs b/generated-clients/core-api-client/async-client/src/models/mutable_field.rs index 4b07389..a8d4334 100644 --- a/generated-clients/core-api-client/async-client/src/models/mutable_field.rs +++ b/generated-clients/core-api-client/async-client/src/models/mutable_field.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/network_configuration_response.rs b/generated-clients/core-api-client/async-client/src/models/network_configuration_response.rs index a38c7f6..fa2ecd8 100644 --- a/generated-clients/core-api-client/async-client/src/models/network_configuration_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/network_configuration_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/network_configuration_response_version.rs b/generated-clients/core-api-client/async-client/src/models/network_configuration_response_version.rs index b2d8bd4..6f00373 100644 --- a/generated-clients/core-api-client/async-client/src/models/network_configuration_response_version.rs +++ b/generated-clients/core-api-client/async-client/src/models/network_configuration_response_version.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/network_configuration_response_well_known_addresses.rs b/generated-clients/core-api-client/async-client/src/models/network_configuration_response_well_known_addresses.rs index f1e4367..cc32864 100644 --- a/generated-clients/core-api-client/async-client/src/models/network_configuration_response_well_known_addresses.rs +++ b/generated-clients/core-api-client/async-client/src/models/network_configuration_response_well_known_addresses.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,7 +11,7 @@ use crate::models; use serde::{Deserialize, Serialize}; -/// NetworkConfigurationResponseWellKnownAddresses : Key addresses for this network. +/// NetworkConfigurationResponseWellKnownAddresses : Key addresses for this network, as per https://docs.radixdlt.com/docs/well-known-addresses. Note that at Cuttlefish, some of these names have been updated elsewhere in the stack, but for backwards compatibility, we must use the old names here. Notably: - `secp256k1_signature_virtual_badge` is now `secp256k1_signature_resource` elsewhere - `ed25519_signature_virtual_badge` is now `ed25519_signature_resource` elsewhere - `package_of_direct_caller_virtual_badge` is now `package_of_direct_caller_resource` elsewhere - `global_caller_virtual_badge` is now `global_caller_resource` elsewhere - `system_transaction_badge` is now `system_transaction_resource` elsewhere #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] pub struct NetworkConfigurationResponseWellKnownAddresses { #[serde(rename = "access_controller_package")] @@ -62,10 +62,14 @@ pub struct NetworkConfigurationResponseWellKnownAddresses { pub secp256k1_signature_virtual_badge: String, #[serde(rename = "system_transaction_badge")] pub system_transaction_badge: String, + #[serde(rename = "test_utils_package", skip_serializing_if = "Option::is_none")] + pub test_utils_package: Option, #[serde(rename = "transaction_processor_package")] pub transaction_processor_package: String, #[serde(rename = "transaction_tracker")] pub transaction_tracker: String, + #[serde(rename = "transaction_tracker_package", skip_serializing_if = "Option::is_none")] + pub transaction_tracker_package: Option, #[serde(rename = "validator_owner_badge")] pub validator_owner_badge: String, #[serde(rename = "xrd")] @@ -73,7 +77,7 @@ pub struct NetworkConfigurationResponseWellKnownAddresses { } impl NetworkConfigurationResponseWellKnownAddresses { - /// Key addresses for this network. + /// Key addresses for this network, as per https://docs.radixdlt.com/docs/well-known-addresses. Note that at Cuttlefish, some of these names have been updated elsewhere in the stack, but for backwards compatibility, we must use the old names here. Notably: - `secp256k1_signature_virtual_badge` is now `secp256k1_signature_resource` elsewhere - `ed25519_signature_virtual_badge` is now `ed25519_signature_resource` elsewhere - `package_of_direct_caller_virtual_badge` is now `package_of_direct_caller_resource` elsewhere - `global_caller_virtual_badge` is now `global_caller_resource` elsewhere - `system_transaction_badge` is now `system_transaction_resource` elsewhere pub fn new(access_controller_package: String, account_owner_badge: String, account_package: String, consensus_manager: String, consensus_manager_package: String, ed25519_signature_virtual_badge: String, faucet: String, faucet_package: String, genesis_helper: String, genesis_helper_package: String, global_caller_virtual_badge: String, identity_owner_badge: String, identity_package: String, metadata_module_package: String, package_of_direct_caller_virtual_badge: String, package_owner_badge: String, package_package: String, pool_package: String, resource_package: String, role_assignment_module_package: String, royalty_module_package: String, secp256k1_signature_virtual_badge: String, system_transaction_badge: String, transaction_processor_package: String, transaction_tracker: String, validator_owner_badge: String, xrd: String) -> NetworkConfigurationResponseWellKnownAddresses { NetworkConfigurationResponseWellKnownAddresses { access_controller_package, @@ -100,8 +104,10 @@ impl NetworkConfigurationResponseWellKnownAddresses { royalty_module_package, secp256k1_signature_virtual_badge, system_transaction_badge, + test_utils_package: None, transaction_processor_package, transaction_tracker, + transaction_tracker_package: None, validator_owner_badge, xrd, } diff --git a/generated-clients/core-api-client/async-client/src/models/network_definition.rs b/generated-clients/core-api-client/async-client/src/models/network_definition.rs index 7623404..d599eae 100644 --- a/generated-clients/core-api-client/async-client/src/models/network_definition.rs +++ b/generated-clients/core-api-client/async-client/src/models/network_definition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/network_status_request.rs b/generated-clients/core-api-client/async-client/src/models/network_status_request.rs index 9342657..5f529ab 100644 --- a/generated-clients/core-api-client/async-client/src/models/network_status_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/network_status_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/network_status_response.rs b/generated-clients/core-api-client/async-client/src/models/network_status_response.rs index 8e4d355..0829ff2 100644 --- a/generated-clients/core-api-client/async-client/src/models/network_status_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/network_status_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -19,9 +19,9 @@ pub struct NetworkStatusResponse { /// A descriptor for the current protocol version that the node is running. #[serde(rename = "current_protocol_version")] pub current_protocol_version: String, - /// The current state identifier at the top of the node's copy of the ledger (ie as of the latest committed transaction). It is not present until genesis has been run. - #[serde(rename = "current_state_identifier", skip_serializing_if = "Option::is_none")] - pub current_state_identifier: Option, + /// The current state identifier at the top of the node's copy of the ledger (i.e. as of the latest committed transaction). + #[serde(rename = "current_state_identifier")] + pub current_state_identifier: models::CommittedStateIdentifier, /// The epoch details for the genesis epoch and round. The genesis epoch will be the last Olympia epoch + 1, and have a \"fake\" round-number 1 (because there is no round for the genesis transaction). In the Gateway, this can be used for the epoch and round number before the first RoundUpdate transaction. It is not present until genesis has been run. #[serde(rename = "genesis_epoch_round", skip_serializing_if = "Option::is_none")] pub genesis_epoch_round: Option, @@ -37,11 +37,11 @@ pub struct NetworkStatusResponse { } impl NetworkStatusResponse { - pub fn new(current_protocol_version: String, pre_genesis_state_identifier: models::CommittedStateIdentifier) -> NetworkStatusResponse { + pub fn new(current_protocol_version: String, current_state_identifier: models::CommittedStateIdentifier, pre_genesis_state_identifier: models::CommittedStateIdentifier) -> NetworkStatusResponse { NetworkStatusResponse { current_epoch_round: None, current_protocol_version, - current_state_identifier: None, + current_state_identifier, genesis_epoch_round: None, post_genesis_epoch_round: None, post_genesis_state_identifier: None, diff --git a/generated-clients/core-api-client/async-client/src/models/next_epoch.rs b/generated-clients/core-api-client/async-client/src/models/next_epoch.rs index d9784c7..c542588 100644 --- a/generated-clients/core-api-client/async-client/src/models/next_epoch.rs +++ b/generated-clients/core-api-client/async-client/src/models/next_epoch.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_authorized_depositor_badge.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_authorized_depositor_badge.rs index ebc89da..b2e8bf7 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_authorized_depositor_badge.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_authorized_depositor_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_global_id.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_global_id.rs index 01dbb85..26c812f 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_global_id.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_global_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_id_type.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_id_type.rs index 0916299..eaa0527 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_id_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_id_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_local_id.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_local_id.rs index d665923..e455e3c 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_local_id.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_local_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_presented_badge.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_presented_badge.rs index 4e4bc37..0ad8e32 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_presented_badge.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_presented_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_requirement.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_requirement.rs index bc0bd14..0360573 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_requirement.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_amount.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_amount.rs index a2f63e1..9b38f9d 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_amount.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_amount.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_data_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_data_entry_substate.rs index 85e3ad2..24c4cab 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_data_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_data_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_data_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_data_entry_value.rs index 14ca3c7..4d27b31 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_data_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_data_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_id_type_substate.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_id_type_substate.rs index cc92215..7d84c83 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_id_type_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_id_type_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_id_type_value.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_id_type_value.rs index ce65365..e81cd51 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_id_type_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_id_type_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_mutable_fields_substate.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_mutable_fields_substate.rs index 463866e..d8938e9 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_mutable_fields_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_mutable_fields_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_mutable_fields_value.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_mutable_fields_value.rs index c32f6a8..476dfd3 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_mutable_fields_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_mutable_fields_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_total_supply_substate.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_total_supply_substate.rs index 68a6fd3..fc04f5a 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_total_supply_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_total_supply_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_total_supply_value.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_total_supply_value.rs index f915a37..094baee 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_total_supply_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_resource_manager_field_total_supply_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_contents_index_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_contents_index_entry_substate.rs index c417aed..74b681f 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_contents_index_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_contents_index_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_contents_index_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_contents_index_entry_value.rs index e11cafc..f6fd686 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_contents_index_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_contents_index_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_balance_substate.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_balance_substate.rs index a119127..af28415 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_balance_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_balance_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_balance_value.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_balance_value.rs index ea45187..2a15c8b 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_balance_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_balance_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_frozen_status_substate.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_frozen_status_substate.rs index bc4b5f8..406d2ba 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_frozen_status_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_frozen_status_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_frozen_status_value.rs b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_frozen_status_value.rs index 12d0c0c..cd06772 100644 --- a/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_frozen_status_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/non_fungible_vault_field_frozen_status_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/notarized_transaction.rs b/generated-clients/core-api-client/async-client/src/models/notarized_transaction.rs index db6fc5a..a411101 100644 --- a/generated-clients/core-api-client/async-client/src/models/notarized_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/notarized_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/notarized_transaction_v2.rs b/generated-clients/core-api-client/async-client/src/models/notarized_transaction_v2.rs index 881249e..41f8a30 100644 --- a/generated-clients/core-api-client/async-client/src/models/notarized_transaction_v2.rs +++ b/generated-clients/core-api-client/async-client/src/models/notarized_transaction_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/object_field_structure.rs b/generated-clients/core-api-client/async-client/src/models/object_field_structure.rs index de51380..c74f14b 100644 --- a/generated-clients/core-api-client/async-client/src/models/object_field_structure.rs +++ b/generated-clients/core-api-client/async-client/src/models/object_field_structure.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/object_hook.rs b/generated-clients/core-api-client/async-client/src/models/object_hook.rs index e75abd3..e3a54b4 100644 --- a/generated-clients/core-api-client/async-client/src/models/object_hook.rs +++ b/generated-clients/core-api-client/async-client/src/models/object_hook.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/object_instance_type_reference.rs b/generated-clients/core-api-client/async-client/src/models/object_instance_type_reference.rs index 94b714f..7816a61 100644 --- a/generated-clients/core-api-client/async-client/src/models/object_instance_type_reference.rs +++ b/generated-clients/core-api-client/async-client/src/models/object_instance_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/object_role_key.rs b/generated-clients/core-api-client/async-client/src/models/object_role_key.rs index 10a6f24..7a6f5b4 100644 --- a/generated-clients/core-api-client/async-client/src/models/object_role_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/object_role_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/object_substate_type_reference.rs b/generated-clients/core-api-client/async-client/src/models/object_substate_type_reference.rs index d56112f..be6867d 100644 --- a/generated-clients/core-api-client/async-client/src/models/object_substate_type_reference.rs +++ b/generated-clients/core-api-client/async-client/src/models/object_substate_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/object_substate_type_reference_type.rs b/generated-clients/core-api-client/async-client/src/models/object_substate_type_reference_type.rs index 78b109c..d7d7c94 100644 --- a/generated-clients/core-api-client/async-client/src/models/object_substate_type_reference_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/object_substate_type_reference_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/object_type_info_details.rs b/generated-clients/core-api-client/async-client/src/models/object_type_info_details.rs index 0318d34..c55e40b 100644 --- a/generated-clients/core-api-client/async-client/src/models/object_type_info_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/object_type_info_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/one_resource_pool_field_state_substate.rs b/generated-clients/core-api-client/async-client/src/models/one_resource_pool_field_state_substate.rs index 8afe6af..7a8ff76 100644 --- a/generated-clients/core-api-client/async-client/src/models/one_resource_pool_field_state_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/one_resource_pool_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/one_resource_pool_field_state_value.rs b/generated-clients/core-api-client/async-client/src/models/one_resource_pool_field_state_value.rs index 6c0a1f7..a53bc31 100644 --- a/generated-clients/core-api-client/async-client/src/models/one_resource_pool_field_state_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/one_resource_pool_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/owner_role.rs b/generated-clients/core-api-client/async-client/src/models/owner_role.rs index 0360b3c..4e0a69b 100644 --- a/generated-clients/core-api-client/async-client/src/models/owner_role.rs +++ b/generated-clients/core-api-client/async-client/src/models/owner_role.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/owner_role_updater.rs b/generated-clients/core-api-client/async-client/src/models/owner_role_updater.rs index e23a53a..285226d 100644 --- a/generated-clients/core-api-client/async-client/src/models/owner_role_updater.rs +++ b/generated-clients/core-api-client/async-client/src/models/owner_role_updater.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_blueprint_auth_template_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/package_blueprint_auth_template_entry_substate.rs index 4faf06e..f51001f 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_blueprint_auth_template_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_blueprint_auth_template_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_blueprint_auth_template_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/package_blueprint_auth_template_entry_value.rs index ca5402f..ad49191 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_blueprint_auth_template_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_blueprint_auth_template_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_blueprint_definition_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/package_blueprint_definition_entry_substate.rs index 02a1eb8..84f9c76 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_blueprint_definition_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_blueprint_definition_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_blueprint_definition_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/package_blueprint_definition_entry_value.rs index 90fea75..9ac60c3 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_blueprint_definition_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_blueprint_definition_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_blueprint_dependencies_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/package_blueprint_dependencies_entry_substate.rs index 63cbd54..b0d13ac 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_blueprint_dependencies_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_blueprint_dependencies_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_blueprint_dependencies_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/package_blueprint_dependencies_entry_value.rs index 2bdc464..598f8e1 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_blueprint_dependencies_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_blueprint_dependencies_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_blueprint_royalty_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/package_blueprint_royalty_entry_substate.rs index d3bf6a4..ac7395a 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_blueprint_royalty_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_blueprint_royalty_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_blueprint_royalty_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/package_blueprint_royalty_entry_value.rs index 22870ca..fbb130e 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_blueprint_royalty_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_blueprint_royalty_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_code_instrumented_code_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/package_code_instrumented_code_entry_substate.rs index e4fc637..21b508e 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_code_instrumented_code_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_code_instrumented_code_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_code_instrumented_code_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/package_code_instrumented_code_entry_value.rs index 1bab95e..450a8f1 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_code_instrumented_code_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_code_instrumented_code_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_code_key.rs b/generated-clients/core-api-client/async-client/src/models/package_code_key.rs index a751490..12585ae 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_code_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_code_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_code_original_code_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/package_code_original_code_entry_substate.rs index 34afa90..afca2a6 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_code_original_code_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_code_original_code_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_code_original_code_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/package_code_original_code_entry_value.rs index 6ecae25..0ff89fb 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_code_original_code_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_code_original_code_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_code_vm_type_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/package_code_vm_type_entry_substate.rs index a33da4c..7dca79a 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_code_vm_type_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_code_vm_type_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_code_vm_type_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/package_code_vm_type_entry_value.rs index 1cf8c01..d595e6c 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_code_vm_type_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_code_vm_type_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_export.rs b/generated-clients/core-api-client/async-client/src/models/package_export.rs index 1999493..2da9dee 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_export.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_export.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_field_royalty_accumulator_substate.rs b/generated-clients/core-api-client/async-client/src/models/package_field_royalty_accumulator_substate.rs index e10eab9..6adfd73 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_field_royalty_accumulator_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_field_royalty_accumulator_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_field_royalty_accumulator_value.rs b/generated-clients/core-api-client/async-client/src/models/package_field_royalty_accumulator_value.rs index 726c98c..06232aa 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_field_royalty_accumulator_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_field_royalty_accumulator_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/package_type_reference.rs b/generated-clients/core-api-client/async-client/src/models/package_type_reference.rs index 8b31035..f3346c3 100644 --- a/generated-clients/core-api-client/async-client/src/models/package_type_reference.rs +++ b/generated-clients/core-api-client/async-client/src/models/package_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_ledger_transaction.rs b/generated-clients/core-api-client/async-client/src/models/parsed_ledger_transaction.rs index 5ad855f..4092931 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_ledger_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_ledger_transaction_identifiers.rs b/generated-clients/core-api-client/async-client/src/models/parsed_ledger_transaction_identifiers.rs index 3536e91..b39c745 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_ledger_transaction_identifiers.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_ledger_transaction_identifiers.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction.rs b/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction.rs index 5399b3b..ae27871 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_identifiers.rs b/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_identifiers.rs index 2d7cb25..3905066 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_identifiers.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_identifiers.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_v2.rs b/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_v2.rs index 39344b1..337137c 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_v2.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_validation_error.rs b/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_validation_error.rs index 4c30eba..4169d1d 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_validation_error.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_notarized_transaction_validation_error.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_signed_transaction_intent.rs b/generated-clients/core-api-client/async-client/src/models/parsed_signed_transaction_intent.rs index 27b709c..cdc5b6a 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_signed_transaction_intent.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_signed_transaction_intent.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_signed_transaction_intent_identifiers.rs b/generated-clients/core-api-client/async-client/src/models/parsed_signed_transaction_intent_identifiers.rs index 81f3443..04c78aa 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_signed_transaction_intent_identifiers.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_signed_transaction_intent_identifiers.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_transaction.rs b/generated-clients/core-api-client/async-client/src/models/parsed_transaction.rs index b5bd7dd..b435791 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_transaction_intent.rs b/generated-clients/core-api-client/async-client/src/models/parsed_transaction_intent.rs index 67e319e..54a1b68 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_transaction_intent.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_transaction_intent.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_transaction_intent_identifiers.rs b/generated-clients/core-api-client/async-client/src/models/parsed_transaction_intent_identifiers.rs index 45cb16e..368359b 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_transaction_intent_identifiers.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_transaction_intent_identifiers.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/parsed_transaction_type.rs b/generated-clients/core-api-client/async-client/src/models/parsed_transaction_type.rs index 51ca108..b6126bc 100644 --- a/generated-clients/core-api-client/async-client/src/models/parsed_transaction_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/parsed_transaction_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/partition_description.rs b/generated-clients/core-api-client/async-client/src/models/partition_description.rs index 02d11d6..9ada6c4 100644 --- a/generated-clients/core-api-client/async-client/src/models/partition_description.rs +++ b/generated-clients/core-api-client/async-client/src/models/partition_description.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/partition_description_type.rs b/generated-clients/core-api-client/async-client/src/models/partition_description_type.rs index d7c25e0..046e040 100644 --- a/generated-clients/core-api-client/async-client/src/models/partition_description_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/partition_description_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/partition_id.rs b/generated-clients/core-api-client/async-client/src/models/partition_id.rs index 3e90627..9adc9db 100644 --- a/generated-clients/core-api-client/async-client/src/models/partition_id.rs +++ b/generated-clients/core-api-client/async-client/src/models/partition_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/partition_kind.rs b/generated-clients/core-api-client/async-client/src/models/partition_kind.rs index 9d168da..8da4b73 100644 --- a/generated-clients/core-api-client/async-client/src/models/partition_kind.rs +++ b/generated-clients/core-api-client/async-client/src/models/partition_kind.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/payment_from_vault.rs b/generated-clients/core-api-client/async-client/src/models/payment_from_vault.rs index 9d102b2..5354aa9 100644 --- a/generated-clients/core-api-client/async-client/src/models/payment_from_vault.rs +++ b/generated-clients/core-api-client/async-client/src/models/payment_from_vault.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/payment_to_royalty_recipient.rs b/generated-clients/core-api-client/async-client/src/models/payment_to_royalty_recipient.rs index 8bc26c6..6617322 100644 --- a/generated-clients/core-api-client/async-client/src/models/payment_to_royalty_recipient.rs +++ b/generated-clients/core-api-client/async-client/src/models/payment_to_royalty_recipient.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/pending_owner_stake_withdrawal.rs b/generated-clients/core-api-client/async-client/src/models/pending_owner_stake_withdrawal.rs index a5fa459..9176120 100644 --- a/generated-clients/core-api-client/async-client/src/models/pending_owner_stake_withdrawal.rs +++ b/generated-clients/core-api-client/async-client/src/models/pending_owner_stake_withdrawal.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/plaintext_message_content.rs b/generated-clients/core-api-client/async-client/src/models/plaintext_message_content.rs index 016d2d2..29a0f84 100644 --- a/generated-clients/core-api-client/async-client/src/models/plaintext_message_content.rs +++ b/generated-clients/core-api-client/async-client/src/models/plaintext_message_content.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/plaintext_message_content_type.rs b/generated-clients/core-api-client/async-client/src/models/plaintext_message_content_type.rs index 848cc9b..0a1d1f0 100644 --- a/generated-clients/core-api-client/async-client/src/models/plaintext_message_content_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/plaintext_message_content_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/plaintext_transaction_message.rs b/generated-clients/core-api-client/async-client/src/models/plaintext_transaction_message.rs index b804be8..eaf6b51 100644 --- a/generated-clients/core-api-client/async-client/src/models/plaintext_transaction_message.rs +++ b/generated-clients/core-api-client/async-client/src/models/plaintext_transaction_message.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/pool_vault.rs b/generated-clients/core-api-client/async-client/src/models/pool_vault.rs index 683669d..c7299ad 100644 --- a/generated-clients/core-api-client/async-client/src/models/pool_vault.rs +++ b/generated-clients/core-api-client/async-client/src/models/pool_vault.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/preparation_settings.rs b/generated-clients/core-api-client/async-client/src/models/preparation_settings.rs new file mode 100644 index 0000000..360eea3 --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/preparation_settings.rs @@ -0,0 +1,42 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct PreparationSettings { + #[serde(rename = "max_blobs")] + pub max_blobs: String, + #[serde(rename = "max_child_subintents_per_intent")] + pub max_child_subintents_per_intent: String, + #[serde(rename = "max_ledger_payload_length")] + pub max_ledger_payload_length: String, + #[serde(rename = "max_subintents_per_transaction")] + pub max_subintents_per_transaction: String, + #[serde(rename = "max_user_payload_length")] + pub max_user_payload_length: String, + #[serde(rename = "v2_transactions_permitted")] + pub v2_transactions_permitted: bool, +} + +impl PreparationSettings { + pub fn new(max_blobs: String, max_child_subintents_per_intent: String, max_ledger_payload_length: String, max_subintents_per_transaction: String, max_user_payload_length: String, v2_transactions_permitted: bool) -> PreparationSettings { + PreparationSettings { + max_blobs, + max_child_subintents_per_intent, + max_ledger_payload_length, + max_subintents_per_transaction, + max_user_payload_length, + v2_transactions_permitted, + } + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/presented_badge.rs b/generated-clients/core-api-client/async-client/src/models/presented_badge.rs index 88ee0f0..0d3be76 100644 --- a/generated-clients/core-api-client/async-client/src/models/presented_badge.rs +++ b/generated-clients/core-api-client/async-client/src/models/presented_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/presented_badge_type.rs b/generated-clients/core-api-client/async-client/src/models/presented_badge_type.rs index a64ca64..0c74bfb 100644 --- a/generated-clients/core-api-client/async-client/src/models/presented_badge_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/presented_badge_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/preview_flags.rs b/generated-clients/core-api-client/async-client/src/models/preview_flags.rs new file mode 100644 index 0000000..2c0991e --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/preview_flags.rs @@ -0,0 +1,40 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct PreviewFlags { + /// If enabled, each manifest processor's auth zone will be given a simulated proof of every signature, which can be used to pass signature access rules. This can be used to preview transactions even if the required signatures are not known ahead of time. See the documentation on [advanced access rules](https://docs.radixdlt.com/docs/advanced-accessrules#signature-requirements) for more information. + #[serde(rename = "assume_all_signature_proofs", skip_serializing_if = "Option::is_none")] + pub assume_all_signature_proofs: Option, + /// If enabled, all authorization checks are skipped during execution. This could be used to e.g.: * Preview protocol update style transactions. * Mint resources for previewing trades with resources you don't own. If doing this, be warned: only resources which were potentially mintable/burnable at creation time will be mintable/burnable, due to feature flags on the resource. Warning: this mode of operation is quite a departure from normal operation: * Calculated fees will likely be lower than a standard execution. * This mode can subtly break invariants some dApp code might rely on, or result in unexpected behaviour, so the execution result might not be valid for your needs. For example, if this flag was used to mint pool units to preview a redemption (or some dApp interaction which behind the scenes redeemed them), they'd redeem for less than they're currently worth, because the blueprint code relies on the total supply of the pool units to calculate their redemption worth, and you've just inflated the total supply through the mint operation. + #[serde(rename = "disable_auth_checks", skip_serializing_if = "Option::is_none")] + pub disable_auth_checks: Option, + /// If enabled, the various runtime epoch-related verifications are skipped: - The `start_epoch_inclusive` and `end_epoch_exclusive` parameters, if specified, are ignored. - The duplicate intent checks (which rely on the expiry epoch) are also ignored. However, if the start and end epoch are provided, they must still be statically valid. We recommend using a value of `start_epoch_inclusive = 1` and `end_epoch_exclusive = 2` in this case. + #[serde(rename = "skip_epoch_check", skip_serializing_if = "Option::is_none")] + pub skip_epoch_check: Option, + /// If enabled, a large simulated pool of XRD is marked as locked. This mode can be used to estimate fees. To get a reliable estimate, we recommend that your transaction is as close as possible to the real transaction. For example: - You should still use a lock fee command, but you can set it to lock a fee of 0. - You should include the public keys that will sign the transaction, so the cost of signature verification and payload size can be accounted for. + #[serde(rename = "use_free_credit", skip_serializing_if = "Option::is_none")] + pub use_free_credit: Option, +} + +impl PreviewFlags { + pub fn new() -> PreviewFlags { + PreviewFlags { + assume_all_signature_proofs: None, + disable_auth_checks: None, + skip_epoch_check: None, + use_free_credit: None, + } + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/preview_transaction.rs b/generated-clients/core-api-client/async-client/src/models/preview_transaction.rs new file mode 100644 index 0000000..8cbe3ad --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/preview_transaction.rs @@ -0,0 +1,27 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] +#[serde(tag = "type")] +pub enum PreviewTransaction { + #[serde(rename="Compiled")] + Compiled(models::CompiledPreviewTransaction), +} + +impl Default for PreviewTransaction { + fn default() -> Self { + Self::Compiled(Default::default()) + } +} + + diff --git a/generated-clients/core-api-client/async-client/src/models/preview_transaction_type.rs b/generated-clients/core-api-client/async-client/src/models/preview_transaction_type.rs new file mode 100644 index 0000000..e738a00 --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/preview_transaction_type.rs @@ -0,0 +1,35 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +/// +#[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] +pub enum PreviewTransactionType { + #[serde(rename = "Compiled")] + Compiled, + +} + +impl std::fmt::Display for PreviewTransactionType { + fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { + match self { + Self::Compiled => write!(f, "Compiled"), + } + } +} + +impl Default for PreviewTransactionType { + fn default() -> PreviewTransactionType { + Self::Compiled + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/primary_role_recovery_attempt.rs b/generated-clients/core-api-client/async-client/src/models/primary_role_recovery_attempt.rs index cdc0df2..7a488a3 100644 --- a/generated-clients/core-api-client/async-client/src/models/primary_role_recovery_attempt.rs +++ b/generated-clients/core-api-client/async-client/src/models/primary_role_recovery_attempt.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/proof_access_rule_node.rs b/generated-clients/core-api-client/async-client/src/models/proof_rule_composite_requirement.rs similarity index 87% rename from generated-clients/core-api-client/async-client/src/models/proof_access_rule_node.rs rename to generated-clients/core-api-client/async-client/src/models/proof_rule_composite_requirement.rs index d323e22..6567bad 100644 --- a/generated-clients/core-api-client/async-client/src/models/proof_access_rule_node.rs +++ b/generated-clients/core-api-client/async-client/src/models/proof_rule_composite_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct ProofAccessRuleNode { +pub struct ProofRuleCompositeRequirement { #[serde(rename = "proof_rule")] - pub proof_rule: models::ProofRule, + pub proof_rule: models::BasicRequirement, } -impl ProofAccessRuleNode { - pub fn new(proof_rule: models::ProofRule) -> ProofAccessRuleNode { - ProofAccessRuleNode { +impl ProofRuleCompositeRequirement { + pub fn new(proof_rule: models::BasicRequirement) -> ProofRuleCompositeRequirement { + ProofRuleCompositeRequirement { proof_rule, } } diff --git a/generated-clients/core-api-client/async-client/src/models/proposer_reward.rs b/generated-clients/core-api-client/async-client/src/models/proposer_reward.rs index e3b9251..8dbbe7b 100644 --- a/generated-clients/core-api-client/async-client/src/models/proposer_reward.rs +++ b/generated-clients/core-api-client/async-client/src/models/proposer_reward.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/protected_access_rule.rs b/generated-clients/core-api-client/async-client/src/models/protected_access_rule.rs index d8ecdaa..1daebe7 100644 --- a/generated-clients/core-api-client/async-client/src/models/protected_access_rule.rs +++ b/generated-clients/core-api-client/async-client/src/models/protected_access_rule.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -14,11 +14,11 @@ use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] pub struct ProtectedAccessRule { #[serde(rename = "access_rule")] - pub access_rule: models::AccessRuleNode, + pub access_rule: models::CompositeRequirement, } impl ProtectedAccessRule { - pub fn new(access_rule: models::AccessRuleNode) -> ProtectedAccessRule { + pub fn new(access_rule: models::CompositeRequirement) -> ProtectedAccessRule { ProtectedAccessRule { access_rule, } diff --git a/generated-clients/core-api-client/async-client/src/models/protocol_update_ledger_proof_origin.rs b/generated-clients/core-api-client/async-client/src/models/protocol_update_ledger_proof_origin.rs index 7605cb1..7bed3b3 100644 --- a/generated-clients/core-api-client/async-client/src/models/protocol_update_ledger_proof_origin.rs +++ b/generated-clients/core-api-client/async-client/src/models/protocol_update_ledger_proof_origin.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/protocol_update_status.rs b/generated-clients/core-api-client/async-client/src/models/protocol_update_status.rs index 98d4614..5cdfe9d 100644 --- a/generated-clients/core-api-client/async-client/src/models/protocol_update_status.rs +++ b/generated-clients/core-api-client/async-client/src/models/protocol_update_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/protocol_update_status_latest_commit.rs b/generated-clients/core-api-client/async-client/src/models/protocol_update_status_latest_commit.rs index 0a88818..3b76182 100644 --- a/generated-clients/core-api-client/async-client/src/models/protocol_update_status_latest_commit.rs +++ b/generated-clients/core-api-client/async-client/src/models/protocol_update_status_latest_commit.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/protocol_update_status_module_field_summary_substate.rs b/generated-clients/core-api-client/async-client/src/models/protocol_update_status_module_field_summary_substate.rs index 48c867f..cd65885 100644 --- a/generated-clients/core-api-client/async-client/src/models/protocol_update_status_module_field_summary_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/protocol_update_status_module_field_summary_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/protocol_update_status_type.rs b/generated-clients/core-api-client/async-client/src/models/protocol_update_status_type.rs index ba2186a..f5e2475 100644 --- a/generated-clients/core-api-client/async-client/src/models/protocol_update_status_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/protocol_update_status_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/protocol_version_readiness.rs b/generated-clients/core-api-client/async-client/src/models/protocol_version_readiness.rs index 25b169d..04c2e60 100644 --- a/generated-clients/core-api-client/async-client/src/models/protocol_version_readiness.rs +++ b/generated-clients/core-api-client/async-client/src/models/protocol_version_readiness.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/public_key.rs b/generated-clients/core-api-client/async-client/src/models/public_key.rs index 6c05a66..fc78a05 100644 --- a/generated-clients/core-api-client/async-client/src/models/public_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/public_key_type.rs b/generated-clients/core-api-client/async-client/src/models/public_key_type.rs index fd1819c..1ff206a 100644 --- a/generated-clients/core-api-client/async-client/src/models/public_key_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/public_key_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/receiver_info.rs b/generated-clients/core-api-client/async-client/src/models/receiver_info.rs index f2812ce..f3a037a 100644 --- a/generated-clients/core-api-client/async-client/src/models/receiver_info.rs +++ b/generated-clients/core-api-client/async-client/src/models/receiver_info.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/recovery_proposal.rs b/generated-clients/core-api-client/async-client/src/models/recovery_proposal.rs index 1db54cb..3524322 100644 --- a/generated-clients/core-api-client/async-client/src/models/recovery_proposal.rs +++ b/generated-clients/core-api-client/async-client/src/models/recovery_proposal.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/recovery_role_recovery_attempt.rs b/generated-clients/core-api-client/async-client/src/models/recovery_role_recovery_attempt.rs index 97c13fb..a8daa27 100644 --- a/generated-clients/core-api-client/async-client/src/models/recovery_role_recovery_attempt.rs +++ b/generated-clients/core-api-client/async-client/src/models/recovery_role_recovery_attempt.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/reference_type.rs b/generated-clients/core-api-client/async-client/src/models/reference_type.rs index c83f817..9780e1a 100644 --- a/generated-clients/core-api-client/async-client/src/models/reference_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/reference_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/remote_generic_substitution.rs b/generated-clients/core-api-client/async-client/src/models/remote_generic_substitution.rs index 9a4cf95..ac8cbc1 100644 --- a/generated-clients/core-api-client/async-client/src/models/remote_generic_substitution.rs +++ b/generated-clients/core-api-client/async-client/src/models/remote_generic_substitution.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/requested_state_version_out_of_bounds_error_details.rs b/generated-clients/core-api-client/async-client/src/models/requested_state_version_out_of_bounds_error_details.rs index 3d0b89c..ec4e488 100644 --- a/generated-clients/core-api-client/async-client/src/models/requested_state_version_out_of_bounds_error_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/requested_state_version_out_of_bounds_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/require_proof_rule.rs b/generated-clients/core-api-client/async-client/src/models/require_basic_requirement.rs similarity index 90% rename from generated-clients/core-api-client/sync-client/src/models/require_proof_rule.rs rename to generated-clients/core-api-client/async-client/src/models/require_basic_requirement.rs index bfd7b7b..479e264 100644 --- a/generated-clients/core-api-client/sync-client/src/models/require_proof_rule.rs +++ b/generated-clients/core-api-client/async-client/src/models/require_basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct RequireProofRule { +pub struct RequireBasicRequirement { #[serde(rename = "requirement")] pub requirement: models::Requirement, } -impl RequireProofRule { - pub fn new(requirement: models::Requirement) -> RequireProofRule { - RequireProofRule { +impl RequireBasicRequirement { + pub fn new(requirement: models::Requirement) -> RequireBasicRequirement { + RequireBasicRequirement { requirement, } } diff --git a/generated-clients/core-api-client/async-client/src/models/requirement.rs b/generated-clients/core-api-client/async-client/src/models/requirement.rs index 190b98f..ff3e115 100644 --- a/generated-clients/core-api-client/async-client/src/models/requirement.rs +++ b/generated-clients/core-api-client/async-client/src/models/requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,6 +11,7 @@ use crate::models; use serde::{Deserialize, Serialize}; +/// Requirement : This is called `ResourceOrNonFungible` in the engine. #[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] #[serde(tag = "type")] pub enum Requirement { diff --git a/generated-clients/core-api-client/async-client/src/models/requirement_type.rs b/generated-clients/core-api-client/async-client/src/models/requirement_type.rs index 17282e0..d297144 100644 --- a/generated-clients/core-api-client/async-client/src/models/requirement_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/requirement_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/resource_amount.rs b/generated-clients/core-api-client/async-client/src/models/resource_amount.rs index a459219..8556d32 100644 --- a/generated-clients/core-api-client/async-client/src/models/resource_amount.rs +++ b/generated-clients/core-api-client/async-client/src/models/resource_amount.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/resource_authorized_depositor_badge.rs b/generated-clients/core-api-client/async-client/src/models/resource_authorized_depositor_badge.rs index 7750a37..62ace51 100644 --- a/generated-clients/core-api-client/async-client/src/models/resource_authorized_depositor_badge.rs +++ b/generated-clients/core-api-client/async-client/src/models/resource_authorized_depositor_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/resource_change.rs b/generated-clients/core-api-client/async-client/src/models/resource_change.rs index 1640576..510a4b3 100644 --- a/generated-clients/core-api-client/async-client/src/models/resource_change.rs +++ b/generated-clients/core-api-client/async-client/src/models/resource_change.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/resource_key.rs b/generated-clients/core-api-client/async-client/src/models/resource_key.rs index 3129999..fe90b30 100644 --- a/generated-clients/core-api-client/async-client/src/models/resource_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/resource_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/resource_preference.rs b/generated-clients/core-api-client/async-client/src/models/resource_preference.rs index 1ee79cb..eb5d485 100644 --- a/generated-clients/core-api-client/async-client/src/models/resource_preference.rs +++ b/generated-clients/core-api-client/async-client/src/models/resource_preference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/resource_presented_badge.rs b/generated-clients/core-api-client/async-client/src/models/resource_presented_badge.rs index ee6f3e9..f264fa1 100644 --- a/generated-clients/core-api-client/async-client/src/models/resource_presented_badge.rs +++ b/generated-clients/core-api-client/async-client/src/models/resource_presented_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/resource_requirement.rs b/generated-clients/core-api-client/async-client/src/models/resource_requirement.rs index 653bbdc..002cde3 100644 --- a/generated-clients/core-api-client/async-client/src/models/resource_requirement.rs +++ b/generated-clients/core-api-client/async-client/src/models/resource_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/resource_specific_deposit_behaviour.rs b/generated-clients/core-api-client/async-client/src/models/resource_specific_deposit_behaviour.rs index ba89d27..0d1e174 100644 --- a/generated-clients/core-api-client/async-client/src/models/resource_specific_deposit_behaviour.rs +++ b/generated-clients/core-api-client/async-client/src/models/resource_specific_deposit_behaviour.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/resource_type.rs b/generated-clients/core-api-client/async-client/src/models/resource_type.rs index a468e9e..a7e81aa 100644 --- a/generated-clients/core-api-client/async-client/src/models/resource_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/resource_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/role_assignment_module_field_owner_role_substate.rs b/generated-clients/core-api-client/async-client/src/models/role_assignment_module_field_owner_role_substate.rs index 1088c53..539ccb8 100644 --- a/generated-clients/core-api-client/async-client/src/models/role_assignment_module_field_owner_role_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/role_assignment_module_field_owner_role_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/role_assignment_module_field_owner_role_value.rs b/generated-clients/core-api-client/async-client/src/models/role_assignment_module_field_owner_role_value.rs index 01a85fc..5de94ed 100644 --- a/generated-clients/core-api-client/async-client/src/models/role_assignment_module_field_owner_role_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/role_assignment_module_field_owner_role_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/role_assignment_module_rule_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/role_assignment_module_rule_entry_substate.rs index bc498c0..cf636af 100644 --- a/generated-clients/core-api-client/async-client/src/models/role_assignment_module_rule_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/role_assignment_module_rule_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/role_assignment_module_rule_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/role_assignment_module_rule_entry_value.rs index 0a2fdc0..936f9d1 100644 --- a/generated-clients/core-api-client/async-client/src/models/role_assignment_module_rule_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/role_assignment_module_rule_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/role_details.rs b/generated-clients/core-api-client/async-client/src/models/role_details.rs index a499b49..2521cce 100644 --- a/generated-clients/core-api-client/async-client/src/models/role_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/role_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/role_protected_method_accessibility.rs b/generated-clients/core-api-client/async-client/src/models/role_protected_method_accessibility.rs index c630516..68f5324 100644 --- a/generated-clients/core-api-client/async-client/src/models/role_protected_method_accessibility.rs +++ b/generated-clients/core-api-client/async-client/src/models/role_protected_method_accessibility.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/role_specification.rs b/generated-clients/core-api-client/async-client/src/models/role_specification.rs index 9d8d900..ec55585 100644 --- a/generated-clients/core-api-client/async-client/src/models/role_specification.rs +++ b/generated-clients/core-api-client/async-client/src/models/role_specification.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/round_update_ledger_transaction.rs b/generated-clients/core-api-client/async-client/src/models/round_update_ledger_transaction.rs index 3e82935..640791f 100644 --- a/generated-clients/core-api-client/async-client/src/models/round_update_ledger_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/round_update_ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/round_update_transaction.rs b/generated-clients/core-api-client/async-client/src/models/round_update_transaction.rs index 00786e5..2dbc625 100644 --- a/generated-clients/core-api-client/async-client/src/models/round_update_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/round_update_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/royalty_amount.rs b/generated-clients/core-api-client/async-client/src/models/royalty_amount.rs index f3dcf7f..a97a3f7 100644 --- a/generated-clients/core-api-client/async-client/src/models/royalty_amount.rs +++ b/generated-clients/core-api-client/async-client/src/models/royalty_amount.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/royalty_module_field_state_substate.rs b/generated-clients/core-api-client/async-client/src/models/royalty_module_field_state_substate.rs index 094bfeb..03a8871 100644 --- a/generated-clients/core-api-client/async-client/src/models/royalty_module_field_state_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/royalty_module_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/royalty_module_field_state_value.rs b/generated-clients/core-api-client/async-client/src/models/royalty_module_field_state_value.rs index ead8f50..ff303bd 100644 --- a/generated-clients/core-api-client/async-client/src/models/royalty_module_field_state_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/royalty_module_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/royalty_module_method_royalty_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/royalty_module_method_royalty_entry_substate.rs index fe154b2..809f8cb 100644 --- a/generated-clients/core-api-client/async-client/src/models/royalty_module_method_royalty_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/royalty_module_method_royalty_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/royalty_module_method_royalty_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/royalty_module_method_royalty_entry_value.rs index bf114c8..4beb45e 100644 --- a/generated-clients/core-api-client/async-client/src/models/royalty_module_method_royalty_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/royalty_module_method_royalty_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/sbor_data.rs b/generated-clients/core-api-client/async-client/src/models/sbor_data.rs index 0bd33db..ce4d0d5 100644 --- a/generated-clients/core-api-client/async-client/src/models/sbor_data.rs +++ b/generated-clients/core-api-client/async-client/src/models/sbor_data.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/sbor_format_options.rs b/generated-clients/core-api-client/async-client/src/models/sbor_format_options.rs index 448048a..24ef8f7 100644 --- a/generated-clients/core-api-client/async-client/src/models/sbor_format_options.rs +++ b/generated-clients/core-api-client/async-client/src/models/sbor_format_options.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/scenarios_request.rs b/generated-clients/core-api-client/async-client/src/models/scenarios_request.rs index 8d42423..763c22d 100644 --- a/generated-clients/core-api-client/async-client/src/models/scenarios_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/scenarios_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/scenarios_response.rs b/generated-clients/core-api-client/async-client/src/models/scenarios_response.rs index dbba31b..7c903a3 100644 --- a/generated-clients/core-api-client/async-client/src/models/scenarios_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/scenarios_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/schema_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/schema_entry_substate.rs index 28a4582..d8fe4fc 100644 --- a/generated-clients/core-api-client/async-client/src/models/schema_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/schema_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/schema_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/schema_entry_value.rs index 3d1d42a..937591c 100644 --- a/generated-clients/core-api-client/async-client/src/models/schema_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/schema_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/schema_key.rs b/generated-clients/core-api-client/async-client/src/models/schema_key.rs index 6b61f27..2d5453f 100644 --- a/generated-clients/core-api-client/async-client/src/models/schema_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/schema_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/scoped_type_id.rs b/generated-clients/core-api-client/async-client/src/models/scoped_type_id.rs index 246ccce..d3c732c 100644 --- a/generated-clients/core-api-client/async-client/src/models/scoped_type_id.rs +++ b/generated-clients/core-api-client/async-client/src/models/scoped_type_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/scrypto_instant.rs b/generated-clients/core-api-client/async-client/src/models/scrypto_instant.rs index 58b90e9..cd9dfa4 100644 --- a/generated-clients/core-api-client/async-client/src/models/scrypto_instant.rs +++ b/generated-clients/core-api-client/async-client/src/models/scrypto_instant.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/scrypto_schema.rs b/generated-clients/core-api-client/async-client/src/models/scrypto_schema.rs index a19d8dc..8becd78 100644 --- a/generated-clients/core-api-client/async-client/src/models/scrypto_schema.rs +++ b/generated-clients/core-api-client/async-client/src/models/scrypto_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/signalling_validator.rs b/generated-clients/core-api-client/async-client/src/models/signalling_validator.rs index 977c260..28b4c72 100644 --- a/generated-clients/core-api-client/async-client/src/models/signalling_validator.rs +++ b/generated-clients/core-api-client/async-client/src/models/signalling_validator.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/signature.rs b/generated-clients/core-api-client/async-client/src/models/signature.rs index fb3d211..ab8713b 100644 --- a/generated-clients/core-api-client/async-client/src/models/signature.rs +++ b/generated-clients/core-api-client/async-client/src/models/signature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/signature_with_public_key.rs b/generated-clients/core-api-client/async-client/src/models/signature_with_public_key.rs index c6d8061..630e4c8 100644 --- a/generated-clients/core-api-client/async-client/src/models/signature_with_public_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/signature_with_public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/signed_transaction_intent.rs b/generated-clients/core-api-client/async-client/src/models/signed_transaction_intent.rs index 62b8bba..aa8f2f3 100644 --- a/generated-clients/core-api-client/async-client/src/models/signed_transaction_intent.rs +++ b/generated-clients/core-api-client/async-client/src/models/signed_transaction_intent.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/signed_transaction_intent_v2.rs b/generated-clients/core-api-client/async-client/src/models/signed_transaction_intent_v2.rs index 01ed4b1..d0d6885 100644 --- a/generated-clients/core-api-client/async-client/src/models/signed_transaction_intent_v2.rs +++ b/generated-clients/core-api-client/async-client/src/models/signed_transaction_intent_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/significant_protocol_update_readiness_entry.rs b/generated-clients/core-api-client/async-client/src/models/significant_protocol_update_readiness_entry.rs index 56c0c2c..1f55336 100644 --- a/generated-clients/core-api-client/async-client/src/models/significant_protocol_update_readiness_entry.rs +++ b/generated-clients/core-api-client/async-client/src/models/significant_protocol_update_readiness_entry.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/sorted_index_blueprint_collection_schema.rs b/generated-clients/core-api-client/async-client/src/models/sorted_index_blueprint_collection_schema.rs index 7e00f71..77a4b4a 100644 --- a/generated-clients/core-api-client/async-client/src/models/sorted_index_blueprint_collection_schema.rs +++ b/generated-clients/core-api-client/async-client/src/models/sorted_index_blueprint_collection_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/sorted_substate_key.rs b/generated-clients/core-api-client/async-client/src/models/sorted_substate_key.rs index 72be277..78213f7 100644 --- a/generated-clients/core-api-client/async-client/src/models/sorted_substate_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/sorted_substate_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_access_controller_request.rs b/generated-clients/core-api-client/async-client/src/models/state_access_controller_request.rs index aa6f280..55b8d15 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_access_controller_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_access_controller_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_access_controller_response.rs b/generated-clients/core-api-client/async-client/src/models/state_access_controller_response.rs index 29f591a..5dbde3f 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_access_controller_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_access_controller_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_account_request.rs b/generated-clients/core-api-client/async-client/src/models/state_account_request.rs index ad9cd32..c2b8943 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_account_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_account_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_account_response.rs b/generated-clients/core-api-client/async-client/src/models/state_account_response.rs index 58b9d8a..65be49a 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_account_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_account_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_component_descendent_node.rs b/generated-clients/core-api-client/async-client/src/models/state_component_descendent_node.rs index 7fd76b5..3f7f616 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_component_descendent_node.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_component_descendent_node.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_component_request.rs b/generated-clients/core-api-client/async-client/src/models/state_component_request.rs index c5a7be6..b7ba98b 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_component_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_component_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_component_response.rs b/generated-clients/core-api-client/async-client/src/models/state_component_response.rs index 43ea2d8..4783f91 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_component_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_component_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_consensus_manager_request.rs b/generated-clients/core-api-client/async-client/src/models/state_consensus_manager_request.rs index 73feb56..48b0c41 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_consensus_manager_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_consensus_manager_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_consensus_manager_response.rs b/generated-clients/core-api-client/async-client/src/models/state_consensus_manager_response.rs index 21e5f60..f0e9b79 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_consensus_manager_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_consensus_manager_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_fungible_resource_manager.rs b/generated-clients/core-api-client/async-client/src/models/state_fungible_resource_manager.rs index 50547a9..1bba010 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_fungible_resource_manager.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_fungible_resource_manager.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_non_fungible_request.rs b/generated-clients/core-api-client/async-client/src/models/state_non_fungible_request.rs index 0280144..3a39bf9 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_non_fungible_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_non_fungible_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_non_fungible_resource_manager.rs b/generated-clients/core-api-client/async-client/src/models/state_non_fungible_resource_manager.rs index dd63c43..b535a8d 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_non_fungible_resource_manager.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_non_fungible_resource_manager.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_non_fungible_response.rs b/generated-clients/core-api-client/async-client/src/models/state_non_fungible_response.rs index 6fe607e..08c2470 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_non_fungible_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_non_fungible_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_package_request.rs b/generated-clients/core-api-client/async-client/src/models/state_package_request.rs index 10b46e5..921c2b0 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_package_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_package_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_package_response.rs b/generated-clients/core-api-client/async-client/src/models/state_package_response.rs index 43369f7..557d887 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_package_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_package_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_resource_manager.rs b/generated-clients/core-api-client/async-client/src/models/state_resource_manager.rs index 8febfbe..d9600c4 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_resource_manager.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_resource_manager.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_resource_request.rs b/generated-clients/core-api-client/async-client/src/models/state_resource_request.rs index 63895a2..f04b514 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_resource_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_resource_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_resource_response.rs b/generated-clients/core-api-client/async-client/src/models/state_resource_response.rs index 26b9a2b..36f62df 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_resource_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_resource_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_updates.rs b/generated-clients/core-api-client/async-client/src/models/state_updates.rs index 90f45fb..1ed3ec9 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_updates.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_updates.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_validator_request.rs b/generated-clients/core-api-client/async-client/src/models/state_validator_request.rs index 4d54cf0..0e4d3a2 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_validator_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_validator_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/state_validator_response.rs b/generated-clients/core-api-client/async-client/src/models/state_validator_response.rs index 4f827f2..e95c183 100644 --- a/generated-clients/core-api-client/async-client/src/models/state_validator_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/state_validator_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/static_blueprint_payload_def.rs b/generated-clients/core-api-client/async-client/src/models/static_blueprint_payload_def.rs index 7dd684e..cea4e22 100644 --- a/generated-clients/core-api-client/async-client/src/models/static_blueprint_payload_def.rs +++ b/generated-clients/core-api-client/async-client/src/models/static_blueprint_payload_def.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/static_role_definition_auth_template.rs b/generated-clients/core-api-client/async-client/src/models/static_role_definition_auth_template.rs index ad4534c..8c04257 100644 --- a/generated-clients/core-api-client/async-client/src/models/static_role_definition_auth_template.rs +++ b/generated-clients/core-api-client/async-client/src/models/static_role_definition_auth_template.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details.rs index ae71b43..1bf3f53 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs index cf1c328..e1145d6 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs index ba2ed82..014a80b 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_type.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_type.rs index b9c1f20..9cbc18b 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_details_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_response.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_response.rs index a9fa665..9952ffa 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter.rs index 507c2a4..4ca608b 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_any.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_any.rs index 56e0752..50d2725 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_any.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_any.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_new_epochs.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_new_epochs.rs index 2d8eeb6..b469912 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_new_epochs.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_new_epochs.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_protocol_update_execution.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_protocol_update_execution.rs index ff3a5c8..3447dfb 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_protocol_update_execution.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_protocol_update_execution.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_protocol_update_initializations.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_protocol_update_initializations.rs index 4bd1d3c..7bb0190 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_protocol_update_initializations.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_protocol_update_initializations.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_type.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_type.rs index 549bc0d..a7420b5 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_filter_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_request.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_request.rs index 482342b..cef4d67 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_proofs_response.rs b/generated-clients/core-api-client/async-client/src/models/stream_proofs_response.rs index dd968f4..8db4a72 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_proofs_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_proofs_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_details.rs b/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_details.rs index e0d76a0..0791f1e 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_details_type.rs b/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_details_type.rs index a5c69fc..e079806 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_details_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_details_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_response.rs b/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_response.rs index 483d68e..a0458eb 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_transactions_error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_transactions_request.rs b/generated-clients/core-api-client/async-client/src/models/stream_transactions_request.rs index c6ef403..d3993ae 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_transactions_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_transactions_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/stream_transactions_response.rs b/generated-clients/core-api-client/async-client/src/models/stream_transactions_response.rs index 583b522..9c56f24 100644 --- a/generated-clients/core-api-client/async-client/src/models/stream_transactions_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/stream_transactions_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/string_plaintext_message_content.rs b/generated-clients/core-api-client/async-client/src/models/string_plaintext_message_content.rs index b3bfa57..78f4bba 100644 --- a/generated-clients/core-api-client/async-client/src/models/string_plaintext_message_content.rs +++ b/generated-clients/core-api-client/async-client/src/models/string_plaintext_message_content.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/subintent_v2.rs b/generated-clients/core-api-client/async-client/src/models/subintent_v2.rs index b2cfb4e..d7959e8 100644 --- a/generated-clients/core-api-client/async-client/src/models/subintent_v2.rs +++ b/generated-clients/core-api-client/async-client/src/models/subintent_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/substate.rs b/generated-clients/core-api-client/async-client/src/models/substate.rs index 7bd3f8d..d530bc3 100644 --- a/generated-clients/core-api-client/async-client/src/models/substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/substate_format_options.rs b/generated-clients/core-api-client/async-client/src/models/substate_format_options.rs index c3604d1..f6091e6 100644 --- a/generated-clients/core-api-client/async-client/src/models/substate_format_options.rs +++ b/generated-clients/core-api-client/async-client/src/models/substate_format_options.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/substate_id.rs b/generated-clients/core-api-client/async-client/src/models/substate_id.rs index 0fb8f0a..58ded5d 100644 --- a/generated-clients/core-api-client/async-client/src/models/substate_id.rs +++ b/generated-clients/core-api-client/async-client/src/models/substate_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/substate_key.rs b/generated-clients/core-api-client/async-client/src/models/substate_key.rs index 75de8a0..12b051b 100644 --- a/generated-clients/core-api-client/async-client/src/models/substate_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/substate_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/substate_key_type.rs b/generated-clients/core-api-client/async-client/src/models/substate_key_type.rs index 44c6a64..f04e5c1 100644 --- a/generated-clients/core-api-client/async-client/src/models/substate_key_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/substate_key_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/substate_system_structure.rs b/generated-clients/core-api-client/async-client/src/models/substate_system_structure.rs index 8d57602..5852a98 100644 --- a/generated-clients/core-api-client/async-client/src/models/substate_system_structure.rs +++ b/generated-clients/core-api-client/async-client/src/models/substate_system_structure.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/substate_system_structure_type.rs b/generated-clients/core-api-client/async-client/src/models/substate_system_structure_type.rs index cdf96a4..aed1e3e 100644 --- a/generated-clients/core-api-client/async-client/src/models/substate_system_structure_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/substate_system_structure_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/substate_type.rs b/generated-clients/core-api-client/async-client/src/models/substate_type.rs index bc33935..343f47a 100644 --- a/generated-clients/core-api-client/async-client/src/models/substate_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/substate_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/substate_value.rs b/generated-clients/core-api-client/async-client/src/models/substate_value.rs index a09a5fb..940e48a 100644 --- a/generated-clients/core-api-client/async-client/src/models/substate_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/substate_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/system_costing_parameters.rs b/generated-clients/core-api-client/async-client/src/models/system_costing_parameters.rs index 1afd056..4640ed4 100644 --- a/generated-clients/core-api-client/async-client/src/models/system_costing_parameters.rs +++ b/generated-clients/core-api-client/async-client/src/models/system_costing_parameters.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/system_field_kind.rs b/generated-clients/core-api-client/async-client/src/models/system_field_kind.rs index a759cfc..126bb5e 100644 --- a/generated-clients/core-api-client/async-client/src/models/system_field_kind.rs +++ b/generated-clients/core-api-client/async-client/src/models/system_field_kind.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/system_field_structure.rs b/generated-clients/core-api-client/async-client/src/models/system_field_structure.rs index 1fdb903..1360ba9 100644 --- a/generated-clients/core-api-client/async-client/src/models/system_field_structure.rs +++ b/generated-clients/core-api-client/async-client/src/models/system_field_structure.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/system_parameters.rs b/generated-clients/core-api-client/async-client/src/models/system_parameters.rs index 3487647..2a1b2c6 100644 --- a/generated-clients/core-api-client/async-client/src/models/system_parameters.rs +++ b/generated-clients/core-api-client/async-client/src/models/system_parameters.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/system_transaction.rs b/generated-clients/core-api-client/async-client/src/models/system_transaction.rs index 788f949..56df887 100644 --- a/generated-clients/core-api-client/async-client/src/models/system_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/system_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/system_version.rs b/generated-clients/core-api-client/async-client/src/models/system_version.rs index 28319d9..8c9c81f 100644 --- a/generated-clients/core-api-client/async-client/src/models/system_version.rs +++ b/generated-clients/core-api-client/async-client/src/models/system_version.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -19,6 +19,8 @@ pub enum SystemVersion { V1, #[serde(rename = "V2")] V2, + #[serde(rename = "V3")] + V3, } @@ -27,6 +29,7 @@ impl std::fmt::Display for SystemVersion { match self { Self::V1 => write!(f, "V1"), Self::V2 => write!(f, "V2"), + Self::V3 => write!(f, "V3"), } } } diff --git a/generated-clients/core-api-client/async-client/src/models/target_identifier.rs b/generated-clients/core-api-client/async-client/src/models/target_identifier.rs index 05e89eb..a76eba4 100644 --- a/generated-clients/core-api-client/async-client/src/models/target_identifier.rs +++ b/generated-clients/core-api-client/async-client/src/models/target_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/target_identifier_type.rs b/generated-clients/core-api-client/async-client/src/models/target_identifier_type.rs index 0af46a5..ad7023e 100644 --- a/generated-clients/core-api-client/async-client/src/models/target_identifier_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/target_identifier_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/timestamped_validator_signature.rs b/generated-clients/core-api-client/async-client/src/models/timestamped_validator_signature.rs index e580c98..46d514d 100644 --- a/generated-clients/core-api-client/async-client/src/models/timestamped_validator_signature.rs +++ b/generated-clients/core-api-client/async-client/src/models/timestamped_validator_signature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_call_preview_request.rs b/generated-clients/core-api-client/async-client/src/models/transaction_call_preview_request.rs index f355b83..823a457 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_call_preview_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_call_preview_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_call_preview_response.rs b/generated-clients/core-api-client/async-client/src/models/transaction_call_preview_response.rs index 7165cf1..25dbd3f 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_call_preview_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_call_preview_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_format_options.rs b/generated-clients/core-api-client/async-client/src/models/transaction_format_options.rs index cbb4cb6..ee07ee8 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_format_options.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_format_options.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_header.rs b/generated-clients/core-api-client/async-client/src/models/transaction_header.rs index 9fc7151..0e004be 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_header.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_header.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_header_v2.rs b/generated-clients/core-api-client/async-client/src/models/transaction_header_v2.rs index 5948d8a..553a054 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_header_v2.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_header_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_id_key.rs b/generated-clients/core-api-client/async-client/src/models/transaction_id_key.rs index 2e9c339..1291ec6 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_id_key.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_id_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_identifiers.rs b/generated-clients/core-api-client/async-client/src/models/transaction_identifiers.rs index 68fbf63..4f16afa 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_identifiers.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_identifiers.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_intent.rs b/generated-clients/core-api-client/async-client/src/models/transaction_intent.rs index 1933e3b..809ac27 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_intent.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_intent.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_intent_status.rs b/generated-clients/core-api-client/async-client/src/models/transaction_intent_status.rs index 4192b81..6f4ceb4 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_intent_status.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_intent_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_intent_v2.rs b/generated-clients/core-api-client/async-client/src/models/transaction_intent_v2.rs index a99cb41..fb4d8d1 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_intent_v2.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_intent_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_message.rs b/generated-clients/core-api-client/async-client/src/models/transaction_message.rs index 3866a3c..f8db327 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_message.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_message.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_message_type.rs b/generated-clients/core-api-client/async-client/src/models/transaction_message_type.rs index bbdc10c..51af06f 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_message_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_message_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_parse_request.rs b/generated-clients/core-api-client/async-client/src/models/transaction_parse_request.rs index 12379af..44164bd 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_parse_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_parse_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_parse_response.rs b/generated-clients/core-api-client/async-client/src/models/transaction_parse_response.rs index 8e6b3e2..689ef31 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_parse_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_parse_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_payload_details.rs b/generated-clients/core-api-client/async-client/src/models/transaction_payload_details.rs index e638443..5832905 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_payload_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_payload_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_payload_status.rs b/generated-clients/core-api-client/async-client/src/models/transaction_payload_status.rs index 0c43e69..ab24f93 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_payload_status.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_payload_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_preview_request.rs b/generated-clients/core-api-client/async-client/src/models/transaction_preview_request.rs index 7509985..e6f56be 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_preview_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_preview_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -18,11 +18,11 @@ pub struct TransactionPreviewRequest { /// An array of hex-encoded blob data, if referenced by the manifest. #[serde(rename = "blobs_hex", skip_serializing_if = "Option::is_none")] pub blobs_hex: Option>, - /// An integer between `0` and `10^10`, marking the epoch at which the transaction is no longer valid. If omitted, a maximum epoch (relative to the `start_epoch_inclusive`) will be used. + /// An integer between `0` and `10^10`, marking the epoch at which the transaction is no longer valid. If not provided, a maximum epoch (relative to the `start_epoch_inclusive`) will be used. #[serde(rename = "end_epoch_exclusive", skip_serializing_if = "Option::is_none")] pub end_epoch_exclusive: Option, - #[serde(rename = "flags")] - pub flags: models::TransactionPreviewRequestFlags, + #[serde(rename = "flags", skip_serializing_if = "Option::is_none")] + pub flags: Option, /// A text representation of a transaction manifest. #[serde(rename = "manifest")] pub manifest: String, @@ -32,46 +32,45 @@ pub struct TransactionPreviewRequest { /// The logical name of the network #[serde(rename = "network")] pub network: String, - /// An integer between `0` and `2^32 - 1`, chosen to allow a unique intent to be created (to enable submitting an otherwise identical/duplicate intent). - #[serde(rename = "nonce")] - pub nonce: u64, - /// Whether the notary should count as a signatory (defaults to `false`). + /// An integer between `0` and `2^32 - 1`, chosen to allow a unique intent to be created (to enable submitting an otherwise identical/duplicate intent). If not provided, this defaults to 0. + #[serde(rename = "nonce", skip_serializing_if = "Option::is_none")] + pub nonce: Option, + /// Whether the notary should be used as a signer (optional). If not provided, this defaults to false. #[serde(rename = "notary_is_signatory", skip_serializing_if = "Option::is_none")] pub notary_is_signatory: Option, - /// The notary public key to use (optional). + /// The notary public key to use. If not provided, this defaults to a fixed public key. #[serde(rename = "notary_public_key", skip_serializing_if = "Option::is_none")] pub notary_public_key: Option, - /// A set of flags to configure the response of the transaction preview. #[serde(rename = "options", skip_serializing_if = "Option::is_none")] pub options: Option, - /// A list of public keys to be used as transaction signers - #[serde(rename = "signer_public_keys")] - pub signer_public_keys: Vec, - /// An integer between `0` and `10^10`, marking the epoch at which the transaction starts being valid. If omitted, the current epoch will be used (taking into account the `at_ledger_state`, if specified). + /// A list of public keys to be used as transaction signers. If not provided, this defaults to an empty array. + #[serde(rename = "signer_public_keys", skip_serializing_if = "Option::is_none")] + pub signer_public_keys: Option>, + /// An integer between `0` and `10^10`, marking the epoch at which the transaction starts being valid. If not provided, the current epoch will be used (taking into account the `at_ledger_state`, if specified). #[serde(rename = "start_epoch_inclusive", skip_serializing_if = "Option::is_none")] pub start_epoch_inclusive: Option, - /// An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to a 1% fee. - #[serde(rename = "tip_percentage")] - pub tip_percentage: u32, + /// An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to a 1% fee. If not provided, this defaults to 0. + #[serde(rename = "tip_percentage", skip_serializing_if = "Option::is_none")] + pub tip_percentage: Option, } impl TransactionPreviewRequest { - pub fn new(flags: models::TransactionPreviewRequestFlags, manifest: String, network: String, nonce: u64, signer_public_keys: Vec, tip_percentage: u32) -> TransactionPreviewRequest { + pub fn new(manifest: String, network: String) -> TransactionPreviewRequest { TransactionPreviewRequest { at_ledger_state: None, blobs_hex: None, end_epoch_exclusive: None, - flags, + flags: None, manifest, message: None, network, - nonce, + nonce: None, notary_is_signatory: None, notary_public_key: None, options: None, - signer_public_keys, + signer_public_keys: None, start_epoch_inclusive: None, - tip_percentage, + tip_percentage: None, } } } diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_preview_request_flags.rs b/generated-clients/core-api-client/async-client/src/models/transaction_preview_request_flags.rs deleted file mode 100644 index 2833697..0000000 --- a/generated-clients/core-api-client/async-client/src/models/transaction_preview_request_flags.rs +++ /dev/null @@ -1,40 +0,0 @@ -/* - * Radix Core API - * - * 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.2.3 - * - * Generated by: https://openapi-generator.tech - */ - -use crate::models; -use serde::{Deserialize, Serialize}; - -#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct TransactionPreviewRequestFlags { - /// Whether the virtual signature proofs should be automatically placed in the auth zone. - #[serde(rename = "assume_all_signature_proofs")] - pub assume_all_signature_proofs: bool, - /// Whether to skip the auth checks during execution. This could be used to e.g.: * Preview protocol update style transactions. * Mint resources for previewing trades with resources you don't own. If doing this, be warned: * Only resources which were potentially mintable/burnable at creation time will be mintable/burnable, due to feature flags on the resource. * Please see the below warning about unexpected results if using this approach. Warning: this mode of operation is quite a departure from normal operation: * Calculated fees will likely be lower than a standard execution. * This mode can subtly break invariants some dApp code might rely on, or result in unexpected behaviour, so the resulting execution result might not be valid for your needs. For example, if I used this flag to mint pool units to preview a redemption (or some dApp interaction which behind the scenes redeemed them), they'd redeem for less than they're currently worth, because the blueprint code relies on the total supply of the pool units to calculate their redemption worth, and you've just inflated the total supply through the mint operation. - #[serde(rename = "disable_auth_checks", skip_serializing_if = "Option::is_none")] - pub disable_auth_checks: Option, - /// Whether to skip the epoch range check (i.e. ignoring the `start_epoch_inclusive` and `end_epoch_exclusive` parameters, if specified). Note: effectively, without an epoch range, the Radix Engine cannot perform the *intent hash duplicate* detection, which means that this check will be skipped as well. - #[serde(rename = "skip_epoch_check")] - pub skip_epoch_check: bool, - /// Whether to use a virtual, preview-only pool of XRD to pay for all execution fees. - #[serde(rename = "use_free_credit")] - pub use_free_credit: bool, -} - -impl TransactionPreviewRequestFlags { - pub fn new(assume_all_signature_proofs: bool, skip_epoch_check: bool, use_free_credit: bool) -> TransactionPreviewRequestFlags { - TransactionPreviewRequestFlags { - assume_all_signature_proofs, - disable_auth_checks: None, - skip_epoch_check, - use_free_credit, - } - } -} - diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_preview_response.rs b/generated-clients/core-api-client/async-client/src/models/transaction_preview_response.rs index 4e7c244..90dc550 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_preview_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_preview_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -23,7 +23,7 @@ pub struct TransactionPreviewResponse { pub instruction_resource_changes: Vec, #[serde(rename = "logs")] pub logs: Vec, - /// An optional field which is only provided if the `request_radix_engine_toolkit_receipt` flag is set to true when requesting a transaction preview from the API. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. + /// An optional field which is only provided if the `radix_engine_toolkit_receipt` flag is set to true when requesting a transaction preview from the API. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. #[serde(rename = "radix_engine_toolkit_receipt", skip_serializing_if = "Option::is_none")] pub radix_engine_toolkit_receipt: Option, #[serde(rename = "receipt")] diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_preview_response_logs_inner.rs b/generated-clients/core-api-client/async-client/src/models/transaction_preview_response_logs_inner.rs index f8f8738..8a0248a 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_preview_response_logs_inner.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_preview_response_logs_inner.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_preview_response_options.rs b/generated-clients/core-api-client/async-client/src/models/transaction_preview_response_options.rs index 7624c1b..97d4624 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_preview_response_options.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_preview_response_options.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_error_details.rs b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_error_details.rs new file mode 100644 index 0000000..b76d084 --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_error_details.rs @@ -0,0 +1,27 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] +#[serde(tag = "type")] +pub enum TransactionPreviewV2ErrorDetails { + #[serde(rename="Invalid")] + Invalid(models::InvalidTransactionPreviewV2ErrorDetails), +} + +impl Default for TransactionPreviewV2ErrorDetails { + fn default() -> Self { + Self::Invalid(Default::default()) + } +} + + diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_error_details_type.rs b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_error_details_type.rs new file mode 100644 index 0000000..5c4cc7d --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_error_details_type.rs @@ -0,0 +1,35 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +/// +#[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] +pub enum TransactionPreviewV2ErrorDetailsType { + #[serde(rename = "Invalid")] + Invalid, + +} + +impl std::fmt::Display for TransactionPreviewV2ErrorDetailsType { + fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { + match self { + Self::Invalid => write!(f, "Invalid"), + } + } +} + +impl Default for TransactionPreviewV2ErrorDetailsType { + fn default() -> TransactionPreviewV2ErrorDetailsType { + Self::Invalid + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_error_response.rs b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_error_response.rs new file mode 100644 index 0000000..366ed5a --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_error_response.rs @@ -0,0 +1,39 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct TransactionPreviewV2ErrorResponse { + /// A numeric code corresponding to the given HTTP error code. + #[serde(rename = "code")] + pub code: i32, + #[serde(rename = "details", skip_serializing_if = "Option::is_none")] + pub details: Option, + /// A human-readable error message. + #[serde(rename = "message")] + pub message: String, + /// A GUID to be used when reporting errors, to allow correlation with the Core API's error logs, in the case where the Core API details are hidden. + #[serde(rename = "trace_id", skip_serializing_if = "Option::is_none")] + pub trace_id: Option, +} + +impl TransactionPreviewV2ErrorResponse { + pub fn new(code: i32, message: String) -> TransactionPreviewV2ErrorResponse { + TransactionPreviewV2ErrorResponse { + code, + details: None, + message, + trace_id: None, + } + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_request.rs b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_request.rs new file mode 100644 index 0000000..fe0d9ae --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_request.rs @@ -0,0 +1,40 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct TransactionPreviewV2Request { + #[serde(rename = "at_ledger_state", skip_serializing_if = "Option::is_none")] + pub at_ledger_state: Option, + #[serde(rename = "flags", skip_serializing_if = "Option::is_none")] + pub flags: Option, + /// The logical name of the network + #[serde(rename = "network")] + pub network: String, + #[serde(rename = "options", skip_serializing_if = "Option::is_none")] + pub options: Option, + #[serde(rename = "preview_transaction")] + pub preview_transaction: models::PreviewTransaction, +} + +impl TransactionPreviewV2Request { + pub fn new(network: String, preview_transaction: models::PreviewTransaction) -> TransactionPreviewV2Request { + TransactionPreviewV2Request { + at_ledger_state: None, + flags: None, + network, + options: None, + preview_transaction, + } + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_response.rs b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_response.rs new file mode 100644 index 0000000..5d548e4 --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_response.rs @@ -0,0 +1,40 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct TransactionPreviewV2Response { + /// A summarized state of the ledger on top of which the preview was performed. + #[serde(rename = "at_ledger_state")] + pub at_ledger_state: models::LedgerStateSummary, + /// An optional field which is only provided if the `logs` flag is set to true in the `options` property of the request. If present, it gives the emitted logs from the transaction execution. + #[serde(rename = "logs", skip_serializing_if = "Option::is_none")] + pub logs: Option>, + /// An optional field which is only provided if the `radix_engine_toolkit_receipt` flag is set to true in the `options` property of the request. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. + #[serde(rename = "radix_engine_toolkit_receipt", skip_serializing_if = "Option::is_none")] + pub radix_engine_toolkit_receipt: Option, + /// This is provided unless the `core_api_receipt` flag is set to false in the `options` property of the request. + #[serde(rename = "receipt", skip_serializing_if = "Option::is_none")] + pub receipt: Option, +} + +impl TransactionPreviewV2Response { + pub fn new(at_ledger_state: models::LedgerStateSummary) -> TransactionPreviewV2Response { + TransactionPreviewV2Response { + at_ledger_state, + logs: None, + radix_engine_toolkit_receipt: None, + receipt: None, + } + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_response_options.rs b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_response_options.rs new file mode 100644 index 0000000..a35c9f7 --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/transaction_preview_v2_response_options.rs @@ -0,0 +1,38 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +/// TransactionPreviewV2ResponseOptions : A set of flags to configure the response of the transaction preview. +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct TransactionPreviewV2ResponseOptions { + /// This flag controls whether the preview response will include a Core API receipt or not. If not provided, this defaults to `false` and no core api receipt is provided in the response. + #[serde(rename = "core_api_receipt", skip_serializing_if = "Option::is_none")] + pub core_api_receipt: Option, + /// This flag controls whether the preview response will include execution logs. If not provided, this defaults to `false` and no logs will be provided in the response. + #[serde(rename = "logs", skip_serializing_if = "Option::is_none")] + pub logs: Option, + /// This flag controls whether the preview response will include a Radix Engine Toolkit serializable receipt or not. If not provided, this defaults to `false` and no toolkit receipt is provided in the response. + #[serde(rename = "radix_engine_toolkit_receipt", skip_serializing_if = "Option::is_none")] + pub radix_engine_toolkit_receipt: Option, +} + +impl TransactionPreviewV2ResponseOptions { + /// A set of flags to configure the response of the transaction preview. + pub fn new() -> TransactionPreviewV2ResponseOptions { + TransactionPreviewV2ResponseOptions { + core_api_receipt: None, + logs: None, + radix_engine_toolkit_receipt: None, + } + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_receipt.rs b/generated-clients/core-api-client/async-client/src/models/transaction_receipt.rs index b85ec55..f8a69e7 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_receipt.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_receipt.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -16,7 +16,7 @@ use serde::{Deserialize, Serialize}; pub struct TransactionReceipt { #[serde(rename = "costing_parameters")] pub costing_parameters: models::CostingParameters, - /// Error message (only present if status is `Failed` or `Rejected`) + /// The error message. This property is only present if the status is `Failed` or `Rejected`. #[serde(rename = "error_message", skip_serializing_if = "Option::is_none")] pub error_message: Option, #[serde(rename = "events", skip_serializing_if = "Option::is_none")] @@ -31,7 +31,7 @@ pub struct TransactionReceipt { pub fee_summary: models::FeeSummary, #[serde(rename = "next_epoch", skip_serializing_if = "Option::is_none")] pub next_epoch: Option, - /// The manifest line-by-line engine return data (only present if `status` is `Succeeded`) + /// The return data for each line of the transaction intent's manifest. This property is only present if the `status` is `Succeeded`. #[serde(rename = "output", skip_serializing_if = "Option::is_none")] pub output: Option>, #[serde(rename = "state_updates")] diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_receipt_request.rs b/generated-clients/core-api-client/async-client/src/models/transaction_receipt_request.rs index 465ebfd..3a7dd0c 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_receipt_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_receipt_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_receipt_response.rs b/generated-clients/core-api-client/async-client/src/models/transaction_receipt_response.rs index daf4dae..8039b7c 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_receipt_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_receipt_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_status.rs b/generated-clients/core-api-client/async-client/src/models/transaction_status.rs index 2189dcf..ebe24a8 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_status.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_status_request.rs b/generated-clients/core-api-client/async-client/src/models/transaction_status_request.rs index 7af58c2..8ca668d 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_status_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_status_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_status_response.rs b/generated-clients/core-api-client/async-client/src/models/transaction_status_response.rs index cd8152b..c8aed2e 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_status_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_status_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_details.rs b/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_details.rs index 62b9dfc..0ddf569 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_details_type.rs b/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_details_type.rs index ba8e22f..1dceff2 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_details_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_details_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_response.rs b/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_response.rs index b146719..6ae2444 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_submit_error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_submit_intent_already_committed.rs b/generated-clients/core-api-client/async-client/src/models/transaction_submit_intent_already_committed.rs index e704d04..9ecbfc5 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_submit_intent_already_committed.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_submit_intent_already_committed.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_submit_priority_threshold_not_met_error_details.rs b/generated-clients/core-api-client/async-client/src/models/transaction_submit_priority_threshold_not_met_error_details.rs index 55f1f2b..19974e4 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_submit_priority_threshold_not_met_error_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_submit_priority_threshold_not_met_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -13,19 +13,27 @@ use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] pub struct TransactionSubmitPriorityThresholdNotMetErrorDetails { - /// A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. + /// NOTE: This is kept for backwards compatibility, but we recommend using `min_tip_proportion_required` instead. A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. #[serde(rename = "min_tip_percentage_required", skip_serializing_if = "Option::is_none")] pub min_tip_percentage_required: Option, - /// Tip percentage of the submitted (and rejected) transaction. + /// A lower bound for tip proportion at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. + #[serde(rename = "min_tip_proportion_required", skip_serializing_if = "Option::is_none")] + pub min_tip_proportion_required: Option, + /// NOTE: This is kept for backwards compatibility, but we recommend using `tip_proportion` instead. Tip percentage of the submitted (and rejected) transaction. For V2 transactions specifying basis point tips, the amount is rounded down. #[serde(rename = "tip_percentage")] pub tip_percentage: u32, + /// The string-encoded decimal tip proportion of the submitted (and rejected) transaction. This field will always be present on Cuttlefish nodes, but is marked as not-required for Cuttlefish launch, to avoid a dependency on clients to update after the node is updated. + #[serde(rename = "tip_proportion", skip_serializing_if = "Option::is_none")] + pub tip_proportion: Option, } impl TransactionSubmitPriorityThresholdNotMetErrorDetails { pub fn new(tip_percentage: u32) -> TransactionSubmitPriorityThresholdNotMetErrorDetails { TransactionSubmitPriorityThresholdNotMetErrorDetails { min_tip_percentage_required: None, + min_tip_proportion_required: None, tip_percentage, + tip_proportion: None, } } } diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_submit_rejected_error_details.rs b/generated-clients/core-api-client/async-client/src/models/transaction_submit_rejected_error_details.rs index c9d35c7..8eb2fc7 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_submit_rejected_error_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_submit_rejected_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_submit_request.rs b/generated-clients/core-api-client/async-client/src/models/transaction_submit_request.rs index ad121ab..63de72a 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_submit_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_submit_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_submit_response.rs b/generated-clients/core-api-client/async-client/src/models/transaction_submit_response.rs index bdc85c7..6da7a1c 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_submit_response.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_submit_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_tracker_collection_entry_substate.rs b/generated-clients/core-api-client/async-client/src/models/transaction_tracker_collection_entry_substate.rs index 9d88cb8..fedbecf 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_tracker_collection_entry_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_tracker_collection_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_tracker_collection_entry_value.rs b/generated-clients/core-api-client/async-client/src/models/transaction_tracker_collection_entry_value.rs index c9764c6..351d318 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_tracker_collection_entry_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_tracker_collection_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_tracker_field_state_substate.rs b/generated-clients/core-api-client/async-client/src/models/transaction_tracker_field_state_substate.rs index aeac5ec..a11637a 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_tracker_field_state_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_tracker_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_tracker_field_state_value.rs b/generated-clients/core-api-client/async-client/src/models/transaction_tracker_field_state_value.rs index bcef329..0f5c76c 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_tracker_field_state_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_tracker_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_tracker_transaction_status.rs b/generated-clients/core-api-client/async-client/src/models/transaction_tracker_transaction_status.rs index 96c8761..9f57969 100644 --- a/generated-clients/core-api-client/async-client/src/models/transaction_tracker_transaction_status.rs +++ b/generated-clients/core-api-client/async-client/src/models/transaction_tracker_transaction_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/transaction_validation_config.rs b/generated-clients/core-api-client/async-client/src/models/transaction_validation_config.rs new file mode 100644 index 0000000..185edbc --- /dev/null +++ b/generated-clients/core-api-client/async-client/src/models/transaction_validation_config.rs @@ -0,0 +1,74 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct TransactionValidationConfig { + #[serde(rename = "manifest_validation")] + pub manifest_validation: models::ManifestValidationRuleset, + #[serde(rename = "max_epoch_range")] + pub max_epoch_range: String, + #[serde(rename = "max_instructions")] + pub max_instructions: String, + #[serde(rename = "max_references_per_intent")] + pub max_references_per_intent: String, + #[serde(rename = "max_signer_signatures_per_intent")] + pub max_signer_signatures_per_intent: String, + #[serde(rename = "max_subintent_depth")] + pub max_subintent_depth: String, + #[serde(rename = "max_tip_basis_points")] + pub max_tip_basis_points: u64, + /// Only applies to V1 transactions + #[serde(rename = "max_tip_percentage")] + pub max_tip_percentage: u32, + #[serde(rename = "max_total_references")] + pub max_total_references: String, + #[serde(rename = "max_total_signature_validations")] + pub max_total_signature_validations: String, + #[serde(rename = "message_validation")] + pub message_validation: models::MessageValidationConfig, + #[serde(rename = "min_tip_basis_points")] + pub min_tip_basis_points: u64, + /// Only applies to V1 transactions + #[serde(rename = "min_tip_percentage")] + pub min_tip_percentage: u32, + #[serde(rename = "preparation_settings")] + pub preparation_settings: models::PreparationSettings, + #[serde(rename = "v1_transactions_allow_notary_to_duplicate_signer")] + pub v1_transactions_allow_notary_to_duplicate_signer: bool, + #[serde(rename = "v2_transactions_allowed")] + pub v2_transactions_allowed: bool, +} + +impl TransactionValidationConfig { + pub fn new(manifest_validation: models::ManifestValidationRuleset, max_epoch_range: String, max_instructions: String, max_references_per_intent: String, max_signer_signatures_per_intent: String, max_subintent_depth: String, max_tip_basis_points: u64, max_tip_percentage: u32, max_total_references: String, max_total_signature_validations: String, message_validation: models::MessageValidationConfig, min_tip_basis_points: u64, min_tip_percentage: u32, preparation_settings: models::PreparationSettings, v1_transactions_allow_notary_to_duplicate_signer: bool, v2_transactions_allowed: bool) -> TransactionValidationConfig { + TransactionValidationConfig { + manifest_validation, + max_epoch_range, + max_instructions, + max_references_per_intent, + max_signer_signatures_per_intent, + max_subintent_depth, + max_tip_basis_points, + max_tip_percentage, + max_total_references, + max_total_signature_validations, + message_validation, + min_tip_basis_points, + min_tip_percentage, + preparation_settings, + v1_transactions_allow_notary_to_duplicate_signer, + v2_transactions_allowed, + } + } +} + diff --git a/generated-clients/core-api-client/async-client/src/models/two_resource_pool_field_state_substate.rs b/generated-clients/core-api-client/async-client/src/models/two_resource_pool_field_state_substate.rs index 22b5f51..b27c627 100644 --- a/generated-clients/core-api-client/async-client/src/models/two_resource_pool_field_state_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/two_resource_pool_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/two_resource_pool_field_state_value.rs b/generated-clients/core-api-client/async-client/src/models/two_resource_pool_field_state_value.rs index a80e139..6a687ad 100644 --- a/generated-clients/core-api-client/async-client/src/models/two_resource_pool_field_state_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/two_resource_pool_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/type_info_details.rs b/generated-clients/core-api-client/async-client/src/models/type_info_details.rs index a49f6d7..95f61a6 100644 --- a/generated-clients/core-api-client/async-client/src/models/type_info_details.rs +++ b/generated-clients/core-api-client/async-client/src/models/type_info_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/type_info_module_field_type_info_substate.rs b/generated-clients/core-api-client/async-client/src/models/type_info_module_field_type_info_substate.rs index 13d54e7..1148ba0 100644 --- a/generated-clients/core-api-client/async-client/src/models/type_info_module_field_type_info_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/type_info_module_field_type_info_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/type_info_module_field_type_info_value.rs b/generated-clients/core-api-client/async-client/src/models/type_info_module_field_type_info_value.rs index 137056f..f2c63bd 100644 --- a/generated-clients/core-api-client/async-client/src/models/type_info_module_field_type_info_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/type_info_module_field_type_info_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/type_info_type.rs b/generated-clients/core-api-client/async-client/src/models/type_info_type.rs index 6327fed..c3d01f5 100644 --- a/generated-clients/core-api-client/async-client/src/models/type_info_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/type_info_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/updated_substate.rs b/generated-clients/core-api-client/async-client/src/models/updated_substate.rs index 2c89603..3e87729 100644 --- a/generated-clients/core-api-client/async-client/src/models/updated_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/updated_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/user_ledger_transaction.rs b/generated-clients/core-api-client/async-client/src/models/user_ledger_transaction.rs index 8bbac4e..a841d25 100644 --- a/generated-clients/core-api-client/async-client/src/models/user_ledger_transaction.rs +++ b/generated-clients/core-api-client/async-client/src/models/user_ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/user_ledger_transaction_v2.rs b/generated-clients/core-api-client/async-client/src/models/user_ledger_transaction_v2.rs index a9171f4..b871255 100644 --- a/generated-clients/core-api-client/async-client/src/models/user_ledger_transaction_v2.rs +++ b/generated-clients/core-api-client/async-client/src/models/user_ledger_transaction_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/validator_fee_change_request.rs b/generated-clients/core-api-client/async-client/src/models/validator_fee_change_request.rs index 6312ccf..042ca04 100644 --- a/generated-clients/core-api-client/async-client/src/models/validator_fee_change_request.rs +++ b/generated-clients/core-api-client/async-client/src/models/validator_fee_change_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/validator_field_protocol_update_readiness_signal_substate.rs b/generated-clients/core-api-client/async-client/src/models/validator_field_protocol_update_readiness_signal_substate.rs index 89a0bcc..9642c4b 100644 --- a/generated-clients/core-api-client/async-client/src/models/validator_field_protocol_update_readiness_signal_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/validator_field_protocol_update_readiness_signal_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/validator_field_protocol_update_readiness_signal_value.rs b/generated-clients/core-api-client/async-client/src/models/validator_field_protocol_update_readiness_signal_value.rs index 68415ef..3c97e20 100644 --- a/generated-clients/core-api-client/async-client/src/models/validator_field_protocol_update_readiness_signal_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/validator_field_protocol_update_readiness_signal_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/validator_field_state_substate.rs b/generated-clients/core-api-client/async-client/src/models/validator_field_state_substate.rs index c58c94d..c7d85d3 100644 --- a/generated-clients/core-api-client/async-client/src/models/validator_field_state_substate.rs +++ b/generated-clients/core-api-client/async-client/src/models/validator_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/validator_field_state_value.rs b/generated-clients/core-api-client/async-client/src/models/validator_field_state_value.rs index c09d08e..bc6f228 100644 --- a/generated-clients/core-api-client/async-client/src/models/validator_field_state_value.rs +++ b/generated-clients/core-api-client/async-client/src/models/validator_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/vault_balance.rs b/generated-clients/core-api-client/async-client/src/models/vault_balance.rs index 33ccb7a..bd83b15 100644 --- a/generated-clients/core-api-client/async-client/src/models/vault_balance.rs +++ b/generated-clients/core-api-client/async-client/src/models/vault_balance.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/version_ledger_state_selector.rs b/generated-clients/core-api-client/async-client/src/models/version_ledger_state_selector.rs index 035e128..6b58e74 100644 --- a/generated-clients/core-api-client/async-client/src/models/version_ledger_state_selector.rs +++ b/generated-clients/core-api-client/async-client/src/models/version_ledger_state_selector.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/virtual_lazy_load_schema.rs b/generated-clients/core-api-client/async-client/src/models/virtual_lazy_load_schema.rs index 7473a9c..1de4f72 100644 --- a/generated-clients/core-api-client/async-client/src/models/virtual_lazy_load_schema.rs +++ b/generated-clients/core-api-client/async-client/src/models/virtual_lazy_load_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/vm_type.rs b/generated-clients/core-api-client/async-client/src/models/vm_type.rs index 5f16ca8..77371a0 100644 --- a/generated-clients/core-api-client/async-client/src/models/vm_type.rs +++ b/generated-clients/core-api-client/async-client/src/models/vm_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/.openapi-generator/FILES b/generated-clients/core-api-client/sync-client/.openapi-generator/FILES index 4879b76..d1c2f7c 100644 --- a/generated-clients/core-api-client/sync-client/.openapi-generator/FILES +++ b/generated-clients/core-api-client/sync-client/.openapi-generator/FILES @@ -6,8 +6,6 @@ README.md docs/AccessControllerFieldStateSubstate.md docs/AccessControllerFieldStateValue.md docs/AccessRule.md -docs/AccessRuleNode.md -docs/AccessRuleNodeType.md docs/AccessRuleType.md docs/AccountAddressKey.md docs/AccountAuthorizedDepositorEntrySubstate.md @@ -24,18 +22,20 @@ docs/ActiveValidator.md docs/ActiveValidatorIndex.md docs/ActiveValidatorKey.md docs/AddressType.md -docs/AllOfAccessRuleNode.md -docs/AllOfProofRule.md +docs/AllOfBasicRequirement.md +docs/AllOfCompositeRequirement.md docs/AlwaysVisibleGlobalNodesVersion.md -docs/AmountOfProofRule.md -docs/AnyOfAccessRuleNode.md -docs/AnyOfProofRule.md +docs/AmountOfBasicRequirement.md +docs/AnyOfBasicRequirement.md +docs/AnyOfCompositeRequirement.md docs/AttachedModuleId.md docs/AuthConfig.md docs/AuthorizedDepositorBadge.md docs/AuthorizedDepositorBadgeType.md docs/AuthorizedDepositorKey.md docs/BasicErrorResponse.md +docs/BasicRequirement.md +docs/BasicRequirementType.md docs/BinaryPlaintextMessageContent.md docs/BlueprintCollectionSchema.md docs/BlueprintCollectionSchemaType.md @@ -66,7 +66,10 @@ docs/CommittedIntentMetadata.md docs/CommittedStateIdentifier.md docs/CommittedTransaction.md docs/CommittedTransactionBalanceChanges.md +docs/CompiledPreviewTransaction.md docs/ComponentMethodTargetIdentifier.md +docs/CompositeRequirement.md +docs/CompositeRequirementType.md docs/ConsensusLedgerProofOrigin.md docs/ConsensusManagerFieldConfigSubstate.md docs/ConsensusManagerFieldConfigValue.md @@ -86,7 +89,7 @@ docs/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstate.md docs/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.md docs/CostingModuleConfig.md docs/CostingParameters.md -docs/CountOfProofRule.md +docs/CountOfBasicRequirement.md docs/CreatedSubstate.md docs/DataStruct.md docs/DefaultDepositRule.md @@ -162,6 +165,7 @@ docs/InstructionResourceChanges.md docs/IntentCoreV2.md docs/IntentHeaderV2.md docs/IntentSignatures.md +docs/InvalidTransactionPreviewV2ErrorDetails.md docs/KeyValueBasedStructure.md docs/KeyValueBlueprintCollectionSchema.md docs/KeyValueStoreEntryStructure.md @@ -220,6 +224,7 @@ docs/LtsTransactionSubmitRejectedErrorDetails.md docs/LtsTransactionSubmitRequest.md docs/LtsTransactionSubmitResponse.md docs/MainMethodKey.md +docs/ManifestValidationRuleset.md docs/MapSubstateKey.md docs/MempoolApi.md docs/MempoolListRequest.md @@ -228,6 +233,7 @@ docs/MempoolTransactionHashes.md docs/MempoolTransactionRequest.md docs/MempoolTransactionResponse.md docs/MempoolTransactionResponsePayloadsInner.md +docs/MessageValidationConfig.md docs/MetadataKey.md docs/MetadataModuleEntrySubstate.md docs/MetadataModuleEntryValue.md @@ -323,12 +329,14 @@ docs/PlaintextMessageContent.md docs/PlaintextMessageContentType.md docs/PlaintextTransactionMessage.md docs/PoolVault.md +docs/PreparationSettings.md docs/PresentedBadge.md docs/PresentedBadgeType.md +docs/PreviewFlags.md +docs/PreviewTransaction.md +docs/PreviewTransactionType.md docs/PrimaryRoleRecoveryAttempt.md -docs/ProofAccessRuleNode.md -docs/ProofRule.md -docs/ProofRuleType.md +docs/ProofRuleCompositeRequirement.md docs/ProposerReward.md docs/ProtectedAccessRule.md docs/ProtocolUpdateLedgerProofOrigin.md @@ -345,7 +353,7 @@ docs/RecoveryRoleRecoveryAttempt.md docs/ReferenceType.md docs/RemoteGenericSubstitution.md docs/RequestedStateVersionOutOfBoundsErrorDetails.md -docs/RequireProofRule.md +docs/RequireBasicRequirement.md docs/Requirement.md docs/RequirementType.md docs/ResourceAmount.md @@ -471,10 +479,15 @@ docs/TransactionParseResponse.md docs/TransactionPayloadDetails.md docs/TransactionPayloadStatus.md docs/TransactionPreviewRequest.md -docs/TransactionPreviewRequestFlags.md docs/TransactionPreviewResponse.md docs/TransactionPreviewResponseLogsInner.md docs/TransactionPreviewResponseOptions.md +docs/TransactionPreviewV2ErrorDetails.md +docs/TransactionPreviewV2ErrorDetailsType.md +docs/TransactionPreviewV2ErrorResponse.md +docs/TransactionPreviewV2Request.md +docs/TransactionPreviewV2Response.md +docs/TransactionPreviewV2ResponseOptions.md docs/TransactionReceipt.md docs/TransactionReceiptRequest.md docs/TransactionReceiptResponse.md @@ -494,6 +507,7 @@ docs/TransactionTrackerCollectionEntryValue.md docs/TransactionTrackerFieldStateSubstate.md docs/TransactionTrackerFieldStateValue.md docs/TransactionTrackerTransactionStatus.md +docs/TransactionValidationConfig.md docs/TwoResourcePoolFieldStateSubstate.md docs/TwoResourcePoolFieldStateValue.md docs/TypeInfoDetails.md @@ -525,8 +539,6 @@ src/lib.rs src/models/access_controller_field_state_substate.rs src/models/access_controller_field_state_value.rs src/models/access_rule.rs -src/models/access_rule_node.rs -src/models/access_rule_node_type.rs src/models/access_rule_type.rs src/models/account_address_key.rs src/models/account_authorized_depositor_entry_substate.rs @@ -543,18 +555,20 @@ src/models/active_validator.rs src/models/active_validator_index.rs src/models/active_validator_key.rs src/models/address_type.rs -src/models/all_of_access_rule_node.rs -src/models/all_of_proof_rule.rs +src/models/all_of_basic_requirement.rs +src/models/all_of_composite_requirement.rs src/models/always_visible_global_nodes_version.rs -src/models/amount_of_proof_rule.rs -src/models/any_of_access_rule_node.rs -src/models/any_of_proof_rule.rs +src/models/amount_of_basic_requirement.rs +src/models/any_of_basic_requirement.rs +src/models/any_of_composite_requirement.rs src/models/attached_module_id.rs src/models/auth_config.rs src/models/authorized_depositor_badge.rs src/models/authorized_depositor_badge_type.rs src/models/authorized_depositor_key.rs src/models/basic_error_response.rs +src/models/basic_requirement.rs +src/models/basic_requirement_type.rs src/models/binary_plaintext_message_content.rs src/models/blueprint_collection_schema.rs src/models/blueprint_collection_schema_type.rs @@ -585,7 +599,10 @@ src/models/committed_intent_metadata.rs src/models/committed_state_identifier.rs src/models/committed_transaction.rs src/models/committed_transaction_balance_changes.rs +src/models/compiled_preview_transaction.rs src/models/component_method_target_identifier.rs +src/models/composite_requirement.rs +src/models/composite_requirement_type.rs src/models/consensus_ledger_proof_origin.rs src/models/consensus_manager_field_config_substate.rs src/models/consensus_manager_field_config_value.rs @@ -605,7 +622,7 @@ src/models/consensus_manager_registered_validators_by_stake_index_entry_substate src/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs src/models/costing_module_config.rs src/models/costing_parameters.rs -src/models/count_of_proof_rule.rs +src/models/count_of_basic_requirement.rs src/models/created_substate.rs src/models/data_struct.rs src/models/default_deposit_rule.rs @@ -681,6 +698,7 @@ src/models/instruction_resource_changes.rs src/models/intent_core_v2.rs src/models/intent_header_v2.rs src/models/intent_signatures.rs +src/models/invalid_transaction_preview_v2_error_details.rs src/models/key_value_based_structure.rs src/models/key_value_blueprint_collection_schema.rs src/models/key_value_store_entry_structure.rs @@ -738,6 +756,7 @@ src/models/lts_transaction_submit_rejected_error_details.rs src/models/lts_transaction_submit_request.rs src/models/lts_transaction_submit_response.rs src/models/main_method_key.rs +src/models/manifest_validation_ruleset.rs src/models/map_substate_key.rs src/models/mempool_list_request.rs src/models/mempool_list_response.rs @@ -745,6 +764,7 @@ src/models/mempool_transaction_hashes.rs src/models/mempool_transaction_request.rs src/models/mempool_transaction_response.rs src/models/mempool_transaction_response_payloads_inner.rs +src/models/message_validation_config.rs src/models/metadata_key.rs src/models/metadata_module_entry_substate.rs src/models/metadata_module_entry_value.rs @@ -841,12 +861,14 @@ src/models/plaintext_message_content.rs src/models/plaintext_message_content_type.rs src/models/plaintext_transaction_message.rs src/models/pool_vault.rs +src/models/preparation_settings.rs src/models/presented_badge.rs src/models/presented_badge_type.rs +src/models/preview_flags.rs +src/models/preview_transaction.rs +src/models/preview_transaction_type.rs src/models/primary_role_recovery_attempt.rs -src/models/proof_access_rule_node.rs -src/models/proof_rule.rs -src/models/proof_rule_type.rs +src/models/proof_rule_composite_requirement.rs src/models/proposer_reward.rs src/models/protected_access_rule.rs src/models/protocol_update_ledger_proof_origin.rs @@ -863,7 +885,7 @@ src/models/recovery_role_recovery_attempt.rs src/models/reference_type.rs src/models/remote_generic_substitution.rs src/models/requested_state_version_out_of_bounds_error_details.rs -src/models/require_proof_rule.rs +src/models/require_basic_requirement.rs src/models/requirement.rs src/models/requirement_type.rs src/models/resource_amount.rs @@ -985,10 +1007,15 @@ src/models/transaction_parse_response.rs src/models/transaction_payload_details.rs src/models/transaction_payload_status.rs src/models/transaction_preview_request.rs -src/models/transaction_preview_request_flags.rs src/models/transaction_preview_response.rs src/models/transaction_preview_response_logs_inner.rs src/models/transaction_preview_response_options.rs +src/models/transaction_preview_v2_error_details.rs +src/models/transaction_preview_v2_error_details_type.rs +src/models/transaction_preview_v2_error_response.rs +src/models/transaction_preview_v2_request.rs +src/models/transaction_preview_v2_response.rs +src/models/transaction_preview_v2_response_options.rs src/models/transaction_receipt.rs src/models/transaction_receipt_request.rs src/models/transaction_receipt_response.rs @@ -1008,6 +1035,7 @@ src/models/transaction_tracker_collection_entry_value.rs src/models/transaction_tracker_field_state_substate.rs src/models/transaction_tracker_field_state_value.rs src/models/transaction_tracker_transaction_status.rs +src/models/transaction_validation_config.rs src/models/two_resource_pool_field_state_substate.rs src/models/two_resource_pool_field_state_value.rs src/models/type_info_details.rs diff --git a/generated-clients/core-api-client/sync-client/README.md b/generated-clients/core-api-client/sync-client/README.md index b2b714d..d9aad56 100644 --- a/generated-clients/core-api-client/sync-client/README.md +++ b/generated-clients/core-api-client/sync-client/README.md @@ -34,7 +34,7 @@ fields on JSON objects. This API client was generated by the [OpenAPI Generator](https://openapi-generator.tech) project. By using the [openapi-spec](https://openapis.org) from a remote server, you can easily generate an API client. -- API version: v1.2.3 +- API version: v1.3.0 - Package version: 1.0.0 - Generator version: 7.6.0 - Build package: `org.openapitools.codegen.languages.RustClientCodegen` @@ -78,7 +78,8 @@ Class | Method | HTTP request | Description *StreamApi* | [**stream_transactions_post**](docs/StreamApi.md#stream_transactions_post) | **POST** /stream/transactions | Get Committed Transactions *TransactionApi* | [**transaction_call_preview_post**](docs/TransactionApi.md#transaction_call_preview_post) | **POST** /transaction/call-preview | Scrypto Call Preview *TransactionApi* | [**transaction_parse_post**](docs/TransactionApi.md#transaction_parse_post) | **POST** /transaction/parse | Parse Transaction Payload -*TransactionApi* | [**transaction_preview_post**](docs/TransactionApi.md#transaction_preview_post) | **POST** /transaction/preview | Transaction Preview +*TransactionApi* | [**transaction_preview_post**](docs/TransactionApi.md#transaction_preview_post) | **POST** /transaction/preview | Transaction Preview V1 +*TransactionApi* | [**transaction_preview_v2_post**](docs/TransactionApi.md#transaction_preview_v2_post) | **POST** /transaction/preview-v2 | Transaction Preview V2 *TransactionApi* | [**transaction_receipt_post**](docs/TransactionApi.md#transaction_receipt_post) | **POST** /transaction/receipt | Get Transaction Receipt *TransactionApi* | [**transaction_status_post**](docs/TransactionApi.md#transaction_status_post) | **POST** /transaction/status | Get Transaction Status *TransactionApi* | [**transaction_submit_post**](docs/TransactionApi.md#transaction_submit_post) | **POST** /transaction/submit | Transaction Submit @@ -89,8 +90,6 @@ Class | Method | HTTP request | Description - [AccessControllerFieldStateSubstate](docs/AccessControllerFieldStateSubstate.md) - [AccessControllerFieldStateValue](docs/AccessControllerFieldStateValue.md) - [AccessRule](docs/AccessRule.md) - - [AccessRuleNode](docs/AccessRuleNode.md) - - [AccessRuleNodeType](docs/AccessRuleNodeType.md) - [AccessRuleType](docs/AccessRuleType.md) - [AccountAddressKey](docs/AccountAddressKey.md) - [AccountAuthorizedDepositorEntrySubstate](docs/AccountAuthorizedDepositorEntrySubstate.md) @@ -107,18 +106,20 @@ Class | Method | HTTP request | Description - [ActiveValidatorIndex](docs/ActiveValidatorIndex.md) - [ActiveValidatorKey](docs/ActiveValidatorKey.md) - [AddressType](docs/AddressType.md) - - [AllOfAccessRuleNode](docs/AllOfAccessRuleNode.md) - - [AllOfProofRule](docs/AllOfProofRule.md) + - [AllOfBasicRequirement](docs/AllOfBasicRequirement.md) + - [AllOfCompositeRequirement](docs/AllOfCompositeRequirement.md) - [AlwaysVisibleGlobalNodesVersion](docs/AlwaysVisibleGlobalNodesVersion.md) - - [AmountOfProofRule](docs/AmountOfProofRule.md) - - [AnyOfAccessRuleNode](docs/AnyOfAccessRuleNode.md) - - [AnyOfProofRule](docs/AnyOfProofRule.md) + - [AmountOfBasicRequirement](docs/AmountOfBasicRequirement.md) + - [AnyOfBasicRequirement](docs/AnyOfBasicRequirement.md) + - [AnyOfCompositeRequirement](docs/AnyOfCompositeRequirement.md) - [AttachedModuleId](docs/AttachedModuleId.md) - [AuthConfig](docs/AuthConfig.md) - [AuthorizedDepositorBadge](docs/AuthorizedDepositorBadge.md) - [AuthorizedDepositorBadgeType](docs/AuthorizedDepositorBadgeType.md) - [AuthorizedDepositorKey](docs/AuthorizedDepositorKey.md) - [BasicErrorResponse](docs/BasicErrorResponse.md) + - [BasicRequirement](docs/BasicRequirement.md) + - [BasicRequirementType](docs/BasicRequirementType.md) - [BinaryPlaintextMessageContent](docs/BinaryPlaintextMessageContent.md) - [BlueprintCollectionSchema](docs/BlueprintCollectionSchema.md) - [BlueprintCollectionSchemaType](docs/BlueprintCollectionSchemaType.md) @@ -149,7 +150,10 @@ Class | Method | HTTP request | Description - [CommittedStateIdentifier](docs/CommittedStateIdentifier.md) - [CommittedTransaction](docs/CommittedTransaction.md) - [CommittedTransactionBalanceChanges](docs/CommittedTransactionBalanceChanges.md) + - [CompiledPreviewTransaction](docs/CompiledPreviewTransaction.md) - [ComponentMethodTargetIdentifier](docs/ComponentMethodTargetIdentifier.md) + - [CompositeRequirement](docs/CompositeRequirement.md) + - [CompositeRequirementType](docs/CompositeRequirementType.md) - [ConsensusLedgerProofOrigin](docs/ConsensusLedgerProofOrigin.md) - [ConsensusManagerFieldConfigSubstate](docs/ConsensusManagerFieldConfigSubstate.md) - [ConsensusManagerFieldConfigValue](docs/ConsensusManagerFieldConfigValue.md) @@ -169,7 +173,7 @@ Class | Method | HTTP request | Description - [ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue](docs/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.md) - [CostingModuleConfig](docs/CostingModuleConfig.md) - [CostingParameters](docs/CostingParameters.md) - - [CountOfProofRule](docs/CountOfProofRule.md) + - [CountOfBasicRequirement](docs/CountOfBasicRequirement.md) - [CreatedSubstate](docs/CreatedSubstate.md) - [DataStruct](docs/DataStruct.md) - [DefaultDepositRule](docs/DefaultDepositRule.md) @@ -245,6 +249,7 @@ Class | Method | HTTP request | Description - [IntentCoreV2](docs/IntentCoreV2.md) - [IntentHeaderV2](docs/IntentHeaderV2.md) - [IntentSignatures](docs/IntentSignatures.md) + - [InvalidTransactionPreviewV2ErrorDetails](docs/InvalidTransactionPreviewV2ErrorDetails.md) - [KeyValueBasedStructure](docs/KeyValueBasedStructure.md) - [KeyValueBlueprintCollectionSchema](docs/KeyValueBlueprintCollectionSchema.md) - [KeyValueStoreEntryStructure](docs/KeyValueStoreEntryStructure.md) @@ -302,6 +307,7 @@ Class | Method | HTTP request | Description - [LtsTransactionSubmitRequest](docs/LtsTransactionSubmitRequest.md) - [LtsTransactionSubmitResponse](docs/LtsTransactionSubmitResponse.md) - [MainMethodKey](docs/MainMethodKey.md) + - [ManifestValidationRuleset](docs/ManifestValidationRuleset.md) - [MapSubstateKey](docs/MapSubstateKey.md) - [MempoolListRequest](docs/MempoolListRequest.md) - [MempoolListResponse](docs/MempoolListResponse.md) @@ -309,6 +315,7 @@ Class | Method | HTTP request | Description - [MempoolTransactionRequest](docs/MempoolTransactionRequest.md) - [MempoolTransactionResponse](docs/MempoolTransactionResponse.md) - [MempoolTransactionResponsePayloadsInner](docs/MempoolTransactionResponsePayloadsInner.md) + - [MessageValidationConfig](docs/MessageValidationConfig.md) - [MetadataKey](docs/MetadataKey.md) - [MetadataModuleEntrySubstate](docs/MetadataModuleEntrySubstate.md) - [MetadataModuleEntryValue](docs/MetadataModuleEntryValue.md) @@ -404,12 +411,14 @@ Class | Method | HTTP request | Description - [PlaintextMessageContentType](docs/PlaintextMessageContentType.md) - [PlaintextTransactionMessage](docs/PlaintextTransactionMessage.md) - [PoolVault](docs/PoolVault.md) + - [PreparationSettings](docs/PreparationSettings.md) - [PresentedBadge](docs/PresentedBadge.md) - [PresentedBadgeType](docs/PresentedBadgeType.md) + - [PreviewFlags](docs/PreviewFlags.md) + - [PreviewTransaction](docs/PreviewTransaction.md) + - [PreviewTransactionType](docs/PreviewTransactionType.md) - [PrimaryRoleRecoveryAttempt](docs/PrimaryRoleRecoveryAttempt.md) - - [ProofAccessRuleNode](docs/ProofAccessRuleNode.md) - - [ProofRule](docs/ProofRule.md) - - [ProofRuleType](docs/ProofRuleType.md) + - [ProofRuleCompositeRequirement](docs/ProofRuleCompositeRequirement.md) - [ProposerReward](docs/ProposerReward.md) - [ProtectedAccessRule](docs/ProtectedAccessRule.md) - [ProtocolUpdateLedgerProofOrigin](docs/ProtocolUpdateLedgerProofOrigin.md) @@ -426,7 +435,7 @@ Class | Method | HTTP request | Description - [ReferenceType](docs/ReferenceType.md) - [RemoteGenericSubstitution](docs/RemoteGenericSubstitution.md) - [RequestedStateVersionOutOfBoundsErrorDetails](docs/RequestedStateVersionOutOfBoundsErrorDetails.md) - - [RequireProofRule](docs/RequireProofRule.md) + - [RequireBasicRequirement](docs/RequireBasicRequirement.md) - [Requirement](docs/Requirement.md) - [RequirementType](docs/RequirementType.md) - [ResourceAmount](docs/ResourceAmount.md) @@ -548,10 +557,15 @@ Class | Method | HTTP request | Description - [TransactionPayloadDetails](docs/TransactionPayloadDetails.md) - [TransactionPayloadStatus](docs/TransactionPayloadStatus.md) - [TransactionPreviewRequest](docs/TransactionPreviewRequest.md) - - [TransactionPreviewRequestFlags](docs/TransactionPreviewRequestFlags.md) - [TransactionPreviewResponse](docs/TransactionPreviewResponse.md) - [TransactionPreviewResponseLogsInner](docs/TransactionPreviewResponseLogsInner.md) - [TransactionPreviewResponseOptions](docs/TransactionPreviewResponseOptions.md) + - [TransactionPreviewV2ErrorDetails](docs/TransactionPreviewV2ErrorDetails.md) + - [TransactionPreviewV2ErrorDetailsType](docs/TransactionPreviewV2ErrorDetailsType.md) + - [TransactionPreviewV2ErrorResponse](docs/TransactionPreviewV2ErrorResponse.md) + - [TransactionPreviewV2Request](docs/TransactionPreviewV2Request.md) + - [TransactionPreviewV2Response](docs/TransactionPreviewV2Response.md) + - [TransactionPreviewV2ResponseOptions](docs/TransactionPreviewV2ResponseOptions.md) - [TransactionReceipt](docs/TransactionReceipt.md) - [TransactionReceiptRequest](docs/TransactionReceiptRequest.md) - [TransactionReceiptResponse](docs/TransactionReceiptResponse.md) @@ -571,6 +585,7 @@ Class | Method | HTTP request | Description - [TransactionTrackerFieldStateSubstate](docs/TransactionTrackerFieldStateSubstate.md) - [TransactionTrackerFieldStateValue](docs/TransactionTrackerFieldStateValue.md) - [TransactionTrackerTransactionStatus](docs/TransactionTrackerTransactionStatus.md) + - [TransactionValidationConfig](docs/TransactionValidationConfig.md) - [TwoResourcePoolFieldStateSubstate](docs/TwoResourcePoolFieldStateSubstate.md) - [TwoResourcePoolFieldStateValue](docs/TwoResourcePoolFieldStateValue.md) - [TypeInfoDetails](docs/TypeInfoDetails.md) diff --git a/generated-clients/core-api-client/sync-client/docs/AllOfAccessRuleNode.md b/generated-clients/core-api-client/sync-client/docs/AllOfAccessRuleNode.md deleted file mode 100644 index 5955d2c..0000000 --- a/generated-clients/core-api-client/sync-client/docs/AllOfAccessRuleNode.md +++ /dev/null @@ -1,11 +0,0 @@ -# AllOfAccessRuleNode - -## Properties - -Name | Type | Description | Notes ------------- | ------------- | ------------- | ------------- -**access_rules** | [**Vec**](AccessRuleNode.md) | | - -[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) - - diff --git a/generated-clients/core-api-client/sync-client/docs/AllOfProofRule.md b/generated-clients/core-api-client/sync-client/docs/AllOfBasicRequirement.md similarity index 93% rename from generated-clients/core-api-client/sync-client/docs/AllOfProofRule.md rename to generated-clients/core-api-client/sync-client/docs/AllOfBasicRequirement.md index 6163263..46ee379 100644 --- a/generated-clients/core-api-client/sync-client/docs/AllOfProofRule.md +++ b/generated-clients/core-api-client/sync-client/docs/AllOfBasicRequirement.md @@ -1,4 +1,4 @@ -# AllOfProofRule +# AllOfBasicRequirement ## Properties diff --git a/generated-clients/core-api-client/sync-client/docs/AllOfCompositeRequirement.md b/generated-clients/core-api-client/sync-client/docs/AllOfCompositeRequirement.md new file mode 100644 index 0000000..2fafd2f --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/AllOfCompositeRequirement.md @@ -0,0 +1,11 @@ +# AllOfCompositeRequirement + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**access_rules** | [**Vec**](CompositeRequirement.md) | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/AmountOfProofRule.md b/generated-clients/core-api-client/sync-client/docs/AmountOfBasicRequirement.md similarity index 93% rename from generated-clients/core-api-client/sync-client/docs/AmountOfProofRule.md rename to generated-clients/core-api-client/sync-client/docs/AmountOfBasicRequirement.md index ab7ccf8..87a5039 100644 --- a/generated-clients/core-api-client/sync-client/docs/AmountOfProofRule.md +++ b/generated-clients/core-api-client/sync-client/docs/AmountOfBasicRequirement.md @@ -1,4 +1,4 @@ -# AmountOfProofRule +# AmountOfBasicRequirement ## Properties diff --git a/generated-clients/core-api-client/sync-client/docs/AnyOfAccessRuleNode.md b/generated-clients/core-api-client/sync-client/docs/AnyOfAccessRuleNode.md deleted file mode 100644 index 3ad23c0..0000000 --- a/generated-clients/core-api-client/sync-client/docs/AnyOfAccessRuleNode.md +++ /dev/null @@ -1,11 +0,0 @@ -# AnyOfAccessRuleNode - -## Properties - -Name | Type | Description | Notes ------------- | ------------- | ------------- | ------------- -**access_rules** | [**Vec**](AccessRuleNode.md) | | - -[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) - - diff --git a/generated-clients/core-api-client/async-client/docs/AllOfProofRule.md b/generated-clients/core-api-client/sync-client/docs/AnyOfBasicRequirement.md similarity index 93% rename from generated-clients/core-api-client/async-client/docs/AllOfProofRule.md rename to generated-clients/core-api-client/sync-client/docs/AnyOfBasicRequirement.md index 6163263..a3df737 100644 --- a/generated-clients/core-api-client/async-client/docs/AllOfProofRule.md +++ b/generated-clients/core-api-client/sync-client/docs/AnyOfBasicRequirement.md @@ -1,4 +1,4 @@ -# AllOfProofRule +# AnyOfBasicRequirement ## Properties diff --git a/generated-clients/core-api-client/sync-client/docs/AnyOfCompositeRequirement.md b/generated-clients/core-api-client/sync-client/docs/AnyOfCompositeRequirement.md new file mode 100644 index 0000000..4e0c336 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/AnyOfCompositeRequirement.md @@ -0,0 +1,11 @@ +# AnyOfCompositeRequirement + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**access_rules** | [**Vec**](CompositeRequirement.md) | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/ProofRule.md b/generated-clients/core-api-client/sync-client/docs/BasicRequirement.md similarity index 91% rename from generated-clients/core-api-client/sync-client/docs/ProofRule.md rename to generated-clients/core-api-client/sync-client/docs/BasicRequirement.md index 69d81e0..7a31d59 100644 --- a/generated-clients/core-api-client/sync-client/docs/ProofRule.md +++ b/generated-clients/core-api-client/sync-client/docs/BasicRequirement.md @@ -1,4 +1,4 @@ -# ProofRule +# BasicRequirement ## Enum Variants diff --git a/generated-clients/core-api-client/async-client/docs/ProofRuleType.md b/generated-clients/core-api-client/sync-client/docs/BasicRequirementType.md similarity index 93% rename from generated-clients/core-api-client/async-client/docs/ProofRuleType.md rename to generated-clients/core-api-client/sync-client/docs/BasicRequirementType.md index 5599976..82d05f9 100644 --- a/generated-clients/core-api-client/async-client/docs/ProofRuleType.md +++ b/generated-clients/core-api-client/sync-client/docs/BasicRequirementType.md @@ -1,4 +1,4 @@ -# ProofRuleType +# BasicRequirementType ## Enum Variants diff --git a/generated-clients/core-api-client/sync-client/docs/BootLoaderModuleFieldTransactionValidationConfigurationSubstate.md b/generated-clients/core-api-client/sync-client/docs/BootLoaderModuleFieldTransactionValidationConfigurationSubstate.md index 30e151e..780ecce 100644 --- a/generated-clients/core-api-client/sync-client/docs/BootLoaderModuleFieldTransactionValidationConfigurationSubstate.md +++ b/generated-clients/core-api-client/sync-client/docs/BootLoaderModuleFieldTransactionValidationConfigurationSubstate.md @@ -4,6 +4,7 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- +**config** | [**models::TransactionValidationConfig**](TransactionValidationConfig.md) | | **is_locked** | **bool** | | [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/sync-client/docs/CompiledPreviewTransaction.md b/generated-clients/core-api-client/sync-client/docs/CompiledPreviewTransaction.md new file mode 100644 index 0000000..dd1218f --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/CompiledPreviewTransaction.md @@ -0,0 +1,11 @@ +# CompiledPreviewTransaction + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**preview_transaction_hex** | **String** | A hex-encoded, compiled `RawPreviewTransaction`. As of Cuttlefish, only `PreviewTransactionV2` is supported. A `PreviewTransactionV2` can be created with a v2 transaction builder: * If using Rust, it can be created with a `TransactionV2Builder` using `build_preview_transaction()` and then converted to hex with `preview_transaction.to_raw().unwrap().to_hex()` * If using the toolkit, you can create this using the v2 transaction builder. Some subtleties: * Partial transactions can't be previewed. Instead, they must be wrapped inside a transaction wrapper, so that the engine knows how to yield to them appropriately. * Currently the builder assumes that the signed partial transactions have real signatures. This isn't strictly required, and we may create a builder in future which allows providing public keys when building partial transactions for use in preview. * If you don't have signatures to hand, you can simply not sign the partial transactions, and then use the `assume_all_signature_proofs` preview flag, although be advised that this may result in the fee estimate being slightly lower during preview. * We may create more ergonomic builders for PreviewTransactions which allow use of public keys to denote the signers of subintents. Let us know if this is important for your use case. | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/CompositeRequirement.md b/generated-clients/core-api-client/sync-client/docs/CompositeRequirement.md new file mode 100644 index 0000000..67d649d --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/CompositeRequirement.md @@ -0,0 +1,10 @@ +# CompositeRequirement + +## Enum Variants + +| Name | Value | +|---- | -----| + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/async-client/docs/AccessRuleNodeType.md b/generated-clients/core-api-client/sync-client/docs/CompositeRequirementType.md similarity index 91% rename from generated-clients/core-api-client/async-client/docs/AccessRuleNodeType.md rename to generated-clients/core-api-client/sync-client/docs/CompositeRequirementType.md index ee21c81..557b5fb 100644 --- a/generated-clients/core-api-client/async-client/docs/AccessRuleNodeType.md +++ b/generated-clients/core-api-client/sync-client/docs/CompositeRequirementType.md @@ -1,4 +1,4 @@ -# AccessRuleNodeType +# CompositeRequirementType ## Enum Variants diff --git a/generated-clients/core-api-client/sync-client/docs/CostingParameters.md b/generated-clients/core-api-client/sync-client/docs/CostingParameters.md index 8f7c149..035c650 100644 --- a/generated-clients/core-api-client/sync-client/docs/CostingParameters.md +++ b/generated-clients/core-api-client/sync-client/docs/CostingParameters.md @@ -9,7 +9,8 @@ Name | Type | Description | Notes **execution_cost_unit_price** | **String** | The string-encoded decimal representing the XRD price of a single cost unit of transaction execution. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. | **finalization_cost_unit_limit** | **u64** | An integer between `0` and `2^32 - 1`, representing the maximum amount of cost units available for the transaction finalization. | **finalization_cost_unit_price** | **String** | The string-encoded decimal representing the XRD price of a single cost unit of transaction finalization. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. | -**tip_percentage** | **u32** | An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to 1% of the fee. | +**tip_percentage** | **u32** | NOTE: V2 transactions specify the tip in basis points, which gets rounded down for this `tip_percentage` field. It is recommended to instead use the `tip_proportion` field to get a fully accurate value. An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to 1% of the fee. | +**tip_proportion** | Option<**String**> | A string-encoded decimal, giving the validator tip as a proportional amount. A value of `\"0.01\"` corresponds to 1% of the fee being paid as a tip. NOTE: This field is not marked as required for Cuttlefish launch, to permit cuttlefish clients to talk to pre-cuttlefish nodes. This can be changed after Cuttlefish enactment once all nodes are on Cuttlefish. | [optional] **xrd_archive_storage_price** | **String** | The string-encoded decimal representing the price of 1 byte of archive storage, expressed in XRD. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. | **xrd_storage_price** | **String** | The string-encoded decimal representing the price of 1 byte of state storage, expressed in XRD. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. | **xrd_usd_price** | **String** | The string-encoded decimal representing what amount of XRD is consumed by a Royalty of 1 USD. This is fixed for a given protocol version, so is not an accurate representation of the XRD price. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. | diff --git a/generated-clients/core-api-client/async-client/docs/CountOfProofRule.md b/generated-clients/core-api-client/sync-client/docs/CountOfBasicRequirement.md similarity index 93% rename from generated-clients/core-api-client/async-client/docs/CountOfProofRule.md rename to generated-clients/core-api-client/sync-client/docs/CountOfBasicRequirement.md index 33e8018..499ae6d 100644 --- a/generated-clients/core-api-client/async-client/docs/CountOfProofRule.md +++ b/generated-clients/core-api-client/sync-client/docs/CountOfBasicRequirement.md @@ -1,4 +1,4 @@ -# CountOfProofRule +# CountOfBasicRequirement ## Properties diff --git a/generated-clients/core-api-client/sync-client/docs/ErrorResponseType.md b/generated-clients/core-api-client/sync-client/docs/ErrorResponseType.md index 8972e62..00508c4 100644 --- a/generated-clients/core-api-client/sync-client/docs/ErrorResponseType.md +++ b/generated-clients/core-api-client/sync-client/docs/ErrorResponseType.md @@ -7,6 +7,7 @@ | Basic | Basic | | TransactionSubmit | TransactionSubmit | | LtsTransactionSubmit | LtsTransactionSubmit | +| TransactionPreviewV2 | TransactionPreviewV2 | | StreamTransactions | StreamTransactions | | StreamProofs | StreamProofs | diff --git a/generated-clients/core-api-client/sync-client/docs/InvalidTransactionPreviewV2ErrorDetails.md b/generated-clients/core-api-client/sync-client/docs/InvalidTransactionPreviewV2ErrorDetails.md new file mode 100644 index 0000000..c55e383 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/InvalidTransactionPreviewV2ErrorDetails.md @@ -0,0 +1,11 @@ +# InvalidTransactionPreviewV2ErrorDetails + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**validation_error** | **String** | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.md b/generated-clients/core-api-client/sync-client/docs/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.md index 29b3ebf..1b0f399 100644 --- a/generated-clients/core-api-client/sync-client/docs/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.md +++ b/generated-clients/core-api-client/sync-client/docs/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.md @@ -4,8 +4,10 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- -**min_tip_percentage_required** | Option<**u32**> | A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] -**tip_percentage** | **u32** | Tip percentage of the submitted (and rejected) transaction. | +**min_tip_percentage_required** | Option<**u32**> | NOTE: This is kept for backwards compatibility, but we recommend using `min_tip_proportion_required` instead. A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] +**min_tip_proportion_required** | Option<**String**> | A lower bound for tip proportion at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] +**tip_percentage** | **u32** | NOTE: This is kept for backwards compatibility, but we recommend using `tip_proportion` instead. Tip percentage of the submitted (and rejected) transaction. For V2 transactions specifying basis point tips, the amount is rounded down. | +**tip_proportion** | Option<**String**> | The string-encoded decimal tip proportion of the submitted (and rejected) transaction. This field will always be present on Cuttlefish nodes, but is marked as not-required for Cuttlefish launch, to avoid a dependency on clients to update after the node is updated. | [optional] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/sync-client/docs/ManifestValidationRuleset.md b/generated-clients/core-api-client/sync-client/docs/ManifestValidationRuleset.md new file mode 100644 index 0000000..ae51f3e --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/ManifestValidationRuleset.md @@ -0,0 +1,13 @@ +# ManifestValidationRuleset + +## Enum Variants + +| Name | Value | +|---- | -----| +| Basic | Basic | +| Cuttlefish | Cuttlefish | + + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/MessageValidationConfig.md b/generated-clients/core-api-client/sync-client/docs/MessageValidationConfig.md new file mode 100644 index 0000000..a14efcc --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/MessageValidationConfig.md @@ -0,0 +1,14 @@ +# MessageValidationConfig + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**max_decryptors** | **String** | | +**max_encrypted_message_length** | **String** | | +**max_mime_type_length** | **String** | | +**max_plaintext_message_length** | **String** | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/NetworkConfigurationResponseWellKnownAddresses.md b/generated-clients/core-api-client/sync-client/docs/NetworkConfigurationResponseWellKnownAddresses.md index 84226e3..ebf3eaf 100644 --- a/generated-clients/core-api-client/sync-client/docs/NetworkConfigurationResponseWellKnownAddresses.md +++ b/generated-clients/core-api-client/sync-client/docs/NetworkConfigurationResponseWellKnownAddresses.md @@ -28,8 +28,10 @@ Name | Type | Description | Notes **royalty_module_package** | **String** | | **secp256k1_signature_virtual_badge** | **String** | | **system_transaction_badge** | **String** | | +**test_utils_package** | Option<**String**> | | [optional] **transaction_processor_package** | **String** | | **transaction_tracker** | **String** | | +**transaction_tracker_package** | Option<**String**> | | [optional] **validator_owner_badge** | **String** | | **xrd** | **String** | | diff --git a/generated-clients/core-api-client/sync-client/docs/NetworkStatusResponse.md b/generated-clients/core-api-client/sync-client/docs/NetworkStatusResponse.md index 20d557c..4a758c1 100644 --- a/generated-clients/core-api-client/sync-client/docs/NetworkStatusResponse.md +++ b/generated-clients/core-api-client/sync-client/docs/NetworkStatusResponse.md @@ -6,7 +6,7 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **current_epoch_round** | Option<[**models::EpochRound**](EpochRound.md)> | The current epoch and round of the ledger. It is not present until genesis has been run. | [optional] **current_protocol_version** | **String** | A descriptor for the current protocol version that the node is running. | -**current_state_identifier** | Option<[**models::CommittedStateIdentifier**](CommittedStateIdentifier.md)> | The current state identifier at the top of the node's copy of the ledger (ie as of the latest committed transaction). It is not present until genesis has been run. | [optional] +**current_state_identifier** | [**models::CommittedStateIdentifier**](CommittedStateIdentifier.md) | The current state identifier at the top of the node's copy of the ledger (i.e. as of the latest committed transaction). | **genesis_epoch_round** | Option<[**models::EpochRound**](EpochRound.md)> | The epoch details for the genesis epoch and round. The genesis epoch will be the last Olympia epoch + 1, and have a \"fake\" round-number 1 (because there is no round for the genesis transaction). In the Gateway, this can be used for the epoch and round number before the first RoundUpdate transaction. It is not present until genesis has been run. | [optional] **post_genesis_epoch_round** | Option<[**models::EpochRound**](EpochRound.md)> | The post-genesis epoch and round. | [optional] **post_genesis_state_identifier** | Option<[**models::CommittedStateIdentifier**](CommittedStateIdentifier.md)> | The ledger state after the genesis transactions have been executed. It is not present until genesis has been run. | [optional] diff --git a/generated-clients/core-api-client/sync-client/docs/PreparationSettings.md b/generated-clients/core-api-client/sync-client/docs/PreparationSettings.md new file mode 100644 index 0000000..73653f6 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/PreparationSettings.md @@ -0,0 +1,16 @@ +# PreparationSettings + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**max_blobs** | **String** | | +**max_child_subintents_per_intent** | **String** | | +**max_ledger_payload_length** | **String** | | +**max_subintents_per_transaction** | **String** | | +**max_user_payload_length** | **String** | | +**v2_transactions_permitted** | **bool** | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/PreviewFlags.md b/generated-clients/core-api-client/sync-client/docs/PreviewFlags.md new file mode 100644 index 0000000..0757dd5 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/PreviewFlags.md @@ -0,0 +1,14 @@ +# PreviewFlags + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**assume_all_signature_proofs** | Option<**bool**> | If enabled, each manifest processor's auth zone will be given a simulated proof of every signature, which can be used to pass signature access rules. This can be used to preview transactions even if the required signatures are not known ahead of time. See the documentation on [advanced access rules](https://docs.radixdlt.com/docs/advanced-accessrules#signature-requirements) for more information. | [optional] +**disable_auth_checks** | Option<**bool**> | If enabled, all authorization checks are skipped during execution. This could be used to e.g.: * Preview protocol update style transactions. * Mint resources for previewing trades with resources you don't own. If doing this, be warned: only resources which were potentially mintable/burnable at creation time will be mintable/burnable, due to feature flags on the resource. Warning: this mode of operation is quite a departure from normal operation: * Calculated fees will likely be lower than a standard execution. * This mode can subtly break invariants some dApp code might rely on, or result in unexpected behaviour, so the execution result might not be valid for your needs. For example, if this flag was used to mint pool units to preview a redemption (or some dApp interaction which behind the scenes redeemed them), they'd redeem for less than they're currently worth, because the blueprint code relies on the total supply of the pool units to calculate their redemption worth, and you've just inflated the total supply through the mint operation. | [optional] +**skip_epoch_check** | Option<**bool**> | If enabled, the various runtime epoch-related verifications are skipped: - The `start_epoch_inclusive` and `end_epoch_exclusive` parameters, if specified, are ignored. - The duplicate intent checks (which rely on the expiry epoch) are also ignored. However, if the start and end epoch are provided, they must still be statically valid. We recommend using a value of `start_epoch_inclusive = 1` and `end_epoch_exclusive = 2` in this case. | [optional] +**use_free_credit** | Option<**bool**> | If enabled, a large simulated pool of XRD is marked as locked. This mode can be used to estimate fees. To get a reliable estimate, we recommend that your transaction is as close as possible to the real transaction. For example: - You should still use a lock fee command, but you can set it to lock a fee of 0. - You should include the public keys that will sign the transaction, so the cost of signature verification and payload size can be accounted for. | [optional] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/AccessRuleNode.md b/generated-clients/core-api-client/sync-client/docs/PreviewTransaction.md similarity index 91% rename from generated-clients/core-api-client/sync-client/docs/AccessRuleNode.md rename to generated-clients/core-api-client/sync-client/docs/PreviewTransaction.md index 1def3a2..e26eb83 100644 --- a/generated-clients/core-api-client/sync-client/docs/AccessRuleNode.md +++ b/generated-clients/core-api-client/sync-client/docs/PreviewTransaction.md @@ -1,4 +1,4 @@ -# AccessRuleNode +# PreviewTransaction ## Enum Variants diff --git a/generated-clients/core-api-client/sync-client/docs/PreviewTransactionType.md b/generated-clients/core-api-client/sync-client/docs/PreviewTransactionType.md new file mode 100644 index 0000000..1eb0a0b --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/PreviewTransactionType.md @@ -0,0 +1,12 @@ +# PreviewTransactionType + +## Enum Variants + +| Name | Value | +|---- | -----| +| Compiled | Compiled | + + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/ProofAccessRuleNode.md b/generated-clients/core-api-client/sync-client/docs/ProofAccessRuleNode.md deleted file mode 100644 index 8c97498..0000000 --- a/generated-clients/core-api-client/sync-client/docs/ProofAccessRuleNode.md +++ /dev/null @@ -1,11 +0,0 @@ -# ProofAccessRuleNode - -## Properties - -Name | Type | Description | Notes ------------- | ------------- | ------------- | ------------- -**proof_rule** | [**models::ProofRule**](ProofRule.md) | | - -[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) - - diff --git a/generated-clients/core-api-client/async-client/docs/AllOfAccessRuleNode.md b/generated-clients/core-api-client/sync-client/docs/ProofRuleCompositeRequirement.md similarity index 72% rename from generated-clients/core-api-client/async-client/docs/AllOfAccessRuleNode.md rename to generated-clients/core-api-client/sync-client/docs/ProofRuleCompositeRequirement.md index 5955d2c..4797af8 100644 --- a/generated-clients/core-api-client/async-client/docs/AllOfAccessRuleNode.md +++ b/generated-clients/core-api-client/sync-client/docs/ProofRuleCompositeRequirement.md @@ -1,10 +1,10 @@ -# AllOfAccessRuleNode +# ProofRuleCompositeRequirement ## Properties Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- -**access_rules** | [**Vec**](AccessRuleNode.md) | | +**proof_rule** | [**models::BasicRequirement**](BasicRequirement.md) | | [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/sync-client/docs/ProtectedAccessRule.md b/generated-clients/core-api-client/sync-client/docs/ProtectedAccessRule.md index 9bd76fc..1a6ea16 100644 --- a/generated-clients/core-api-client/sync-client/docs/ProtectedAccessRule.md +++ b/generated-clients/core-api-client/sync-client/docs/ProtectedAccessRule.md @@ -4,7 +4,7 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- -**access_rule** | [**models::AccessRuleNode**](AccessRuleNode.md) | | +**access_rule** | [**models::CompositeRequirement**](CompositeRequirement.md) | | [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/async-client/docs/RequireProofRule.md b/generated-clients/core-api-client/sync-client/docs/RequireBasicRequirement.md similarity index 92% rename from generated-clients/core-api-client/async-client/docs/RequireProofRule.md rename to generated-clients/core-api-client/sync-client/docs/RequireBasicRequirement.md index 6ca08d7..d1ab006 100644 --- a/generated-clients/core-api-client/async-client/docs/RequireProofRule.md +++ b/generated-clients/core-api-client/sync-client/docs/RequireBasicRequirement.md @@ -1,4 +1,4 @@ -# RequireProofRule +# RequireBasicRequirement ## Properties diff --git a/generated-clients/core-api-client/sync-client/docs/SystemVersion.md b/generated-clients/core-api-client/sync-client/docs/SystemVersion.md index 7a4daf2..7b51a7d 100644 --- a/generated-clients/core-api-client/sync-client/docs/SystemVersion.md +++ b/generated-clients/core-api-client/sync-client/docs/SystemVersion.md @@ -6,6 +6,7 @@ |---- | -----| | V1 | V1 | | V2 | V2 | +| V3 | V3 | [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionApi.md b/generated-clients/core-api-client/sync-client/docs/TransactionApi.md index 3b367cc..70b7e26 100644 --- a/generated-clients/core-api-client/sync-client/docs/TransactionApi.md +++ b/generated-clients/core-api-client/sync-client/docs/TransactionApi.md @@ -6,7 +6,8 @@ Method | HTTP request | Description ------------- | ------------- | ------------- [**transaction_call_preview_post**](TransactionApi.md#transaction_call_preview_post) | **POST** /transaction/call-preview | Scrypto Call Preview [**transaction_parse_post**](TransactionApi.md#transaction_parse_post) | **POST** /transaction/parse | Parse Transaction Payload -[**transaction_preview_post**](TransactionApi.md#transaction_preview_post) | **POST** /transaction/preview | Transaction Preview +[**transaction_preview_post**](TransactionApi.md#transaction_preview_post) | **POST** /transaction/preview | Transaction Preview V1 +[**transaction_preview_v2_post**](TransactionApi.md#transaction_preview_v2_post) | **POST** /transaction/preview-v2 | Transaction Preview V2 [**transaction_receipt_post**](TransactionApi.md#transaction_receipt_post) | **POST** /transaction/receipt | Get Transaction Receipt [**transaction_status_post**](TransactionApi.md#transaction_status_post) | **POST** /transaction/status | Get Transaction Status [**transaction_submit_post**](TransactionApi.md#transaction_submit_post) | **POST** /transaction/submit | Transaction Submit @@ -76,9 +77,9 @@ No authorization required ## transaction_preview_post > models::TransactionPreviewResponse transaction_preview_post(transaction_preview_request) -Transaction Preview +Transaction Preview V1 -Preview a transaction against the latest network state, and returns the preview receipt. +Preview a transaction against the latest network state, and returns the preview receipt. If the node has enabled it, you may be able to also preview against recent network state. For V2 transactions (and beyond) the `/preview-v2` endpoint should be used instead. ### Parameters @@ -103,6 +104,36 @@ No authorization required [[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) +## transaction_preview_v2_post + +> models::TransactionPreviewV2Response transaction_preview_v2_post(transaction_preview_v2_request) +Transaction Preview V2 + +Previews a transaction against the latest network state, and returns the preview receipt. If the node has enabled it, you may be able to also preview against recent network state. This endpoint supports V2 transactions (and beyond). If you still need to preview V1 transactions, you should use the `/preview` endpoint instead. + +### Parameters + + +Name | Type | Description | Required | Notes +------------- | ------------- | ------------- | ------------- | ------------- +**transaction_preview_v2_request** | [**TransactionPreviewV2Request**](TransactionPreviewV2Request.md) | | [required] | + +### Return type + +[**models::TransactionPreviewV2Response**](TransactionPreviewV2Response.md) + +### Authorization + +No authorization required + +### HTTP request headers + +- **Content-Type**: application/json +- **Accept**: application/json + +[[Back to top]](#) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to Model list]](../README.md#documentation-for-models) [[Back to README]](../README.md) + + ## transaction_receipt_post > models::TransactionReceiptResponse transaction_receipt_post(transaction_receipt_request) diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewRequest.md b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewRequest.md index 27e8406..25a66bf 100644 --- a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewRequest.md +++ b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewRequest.md @@ -6,18 +6,18 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **at_ledger_state** | Option<[**models::LedgerStateSelector**](LedgerStateSelector.md)> | | [optional] **blobs_hex** | Option<**Vec**> | An array of hex-encoded blob data, if referenced by the manifest. | [optional] -**end_epoch_exclusive** | Option<**u64**> | An integer between `0` and `10^10`, marking the epoch at which the transaction is no longer valid. If omitted, a maximum epoch (relative to the `start_epoch_inclusive`) will be used. | [optional] -**flags** | [**models::TransactionPreviewRequestFlags**](TransactionPreviewRequest_flags.md) | | +**end_epoch_exclusive** | Option<**u64**> | An integer between `0` and `10^10`, marking the epoch at which the transaction is no longer valid. If not provided, a maximum epoch (relative to the `start_epoch_inclusive`) will be used. | [optional] +**flags** | Option<[**models::PreviewFlags**](PreviewFlags.md)> | | [optional] **manifest** | **String** | A text representation of a transaction manifest. | **message** | Option<[**models::TransactionMessage**](TransactionMessage.md)> | An optional transaction message. Only affects the costing. | [optional] **network** | **String** | The logical name of the network | -**nonce** | **u64** | An integer between `0` and `2^32 - 1`, chosen to allow a unique intent to be created (to enable submitting an otherwise identical/duplicate intent). | -**notary_is_signatory** | Option<**bool**> | Whether the notary should count as a signatory (defaults to `false`). | [optional] -**notary_public_key** | Option<[**models::PublicKey**](PublicKey.md)> | The notary public key to use (optional). | [optional] -**options** | Option<[**models::TransactionPreviewResponseOptions**](TransactionPreviewResponseOptions.md)> | A set of flags to configure the response of the transaction preview. | [optional] -**signer_public_keys** | [**Vec**](PublicKey.md) | A list of public keys to be used as transaction signers | -**start_epoch_inclusive** | Option<**u64**> | An integer between `0` and `10^10`, marking the epoch at which the transaction starts being valid. If omitted, the current epoch will be used (taking into account the `at_ledger_state`, if specified). | [optional] -**tip_percentage** | **u32** | An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to a 1% fee. | +**nonce** | Option<**u64**> | An integer between `0` and `2^32 - 1`, chosen to allow a unique intent to be created (to enable submitting an otherwise identical/duplicate intent). If not provided, this defaults to 0. | [optional] +**notary_is_signatory** | Option<**bool**> | Whether the notary should be used as a signer (optional). If not provided, this defaults to false. | [optional] +**notary_public_key** | Option<[**models::PublicKey**](PublicKey.md)> | The notary public key to use. If not provided, this defaults to a fixed public key. | [optional] +**options** | Option<[**models::TransactionPreviewResponseOptions**](TransactionPreviewResponseOptions.md)> | | [optional] +**signer_public_keys** | Option<[**Vec**](PublicKey.md)> | A list of public keys to be used as transaction signers. If not provided, this defaults to an empty array. | [optional] +**start_epoch_inclusive** | Option<**u64**> | An integer between `0` and `10^10`, marking the epoch at which the transaction starts being valid. If not provided, the current epoch will be used (taking into account the `at_ledger_state`, if specified). | [optional] +**tip_percentage** | Option<**u32**> | An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to a 1% fee. If not provided, this defaults to 0. | [optional] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewRequestFlags.md b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewRequestFlags.md deleted file mode 100644 index 942a720..0000000 --- a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewRequestFlags.md +++ /dev/null @@ -1,14 +0,0 @@ -# TransactionPreviewRequestFlags - -## Properties - -Name | Type | Description | Notes ------------- | ------------- | ------------- | ------------- -**assume_all_signature_proofs** | **bool** | Whether the virtual signature proofs should be automatically placed in the auth zone. | -**disable_auth_checks** | Option<**bool**> | Whether to skip the auth checks during execution. This could be used to e.g.: * Preview protocol update style transactions. * Mint resources for previewing trades with resources you don't own. If doing this, be warned: * Only resources which were potentially mintable/burnable at creation time will be mintable/burnable, due to feature flags on the resource. * Please see the below warning about unexpected results if using this approach. Warning: this mode of operation is quite a departure from normal operation: * Calculated fees will likely be lower than a standard execution. * This mode can subtly break invariants some dApp code might rely on, or result in unexpected behaviour, so the resulting execution result might not be valid for your needs. For example, if I used this flag to mint pool units to preview a redemption (or some dApp interaction which behind the scenes redeemed them), they'd redeem for less than they're currently worth, because the blueprint code relies on the total supply of the pool units to calculate their redemption worth, and you've just inflated the total supply through the mint operation. | [optional] -**skip_epoch_check** | **bool** | Whether to skip the epoch range check (i.e. ignoring the `start_epoch_inclusive` and `end_epoch_exclusive` parameters, if specified). Note: effectively, without an epoch range, the Radix Engine cannot perform the *intent hash duplicate* detection, which means that this check will be skipped as well. | -**use_free_credit** | **bool** | Whether to use a virtual, preview-only pool of XRD to pay for all execution fees. | - -[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) - - diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewResponse.md b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewResponse.md index 9d13f79..e69fe39 100644 --- a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewResponse.md +++ b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewResponse.md @@ -8,7 +8,7 @@ Name | Type | Description | Notes **encoded_receipt** | **String** | The hex-sbor-encoded receipt. This field is deprecated and will be removed from the API with the release of the next protocol update, cuttlefish. This field was provided primarily for use with the Radix Engine Toolkit and its execution summary functionality. If you still wish to use this functionality update your Radix Engine Toolkit and use the receipt provided in the `radix_engine_toolkit_receipt` field of this response. | **instruction_resource_changes** | [**Vec**](InstructionResourceChanges.md) | | **logs** | [**Vec**](TransactionPreviewResponse_logs_inner.md) | | -**radix_engine_toolkit_receipt** | Option<[**serde_json::Value**](.md)> | An optional field which is only provided if the `request_radix_engine_toolkit_receipt` flag is set to true when requesting a transaction preview from the API. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. | [optional] +**radix_engine_toolkit_receipt** | Option<[**serde_json::Value**](.md)> | An optional field which is only provided if the `radix_engine_toolkit_receipt` flag is set to true when requesting a transaction preview from the API. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. | [optional] **receipt** | [**models::TransactionReceipt**](TransactionReceipt.md) | | [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ErrorDetails.md b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ErrorDetails.md new file mode 100644 index 0000000..0e4416b --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ErrorDetails.md @@ -0,0 +1,10 @@ +# TransactionPreviewV2ErrorDetails + +## Enum Variants + +| Name | Value | +|---- | -----| + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ErrorDetailsType.md b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ErrorDetailsType.md new file mode 100644 index 0000000..cfa6be4 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ErrorDetailsType.md @@ -0,0 +1,12 @@ +# TransactionPreviewV2ErrorDetailsType + +## Enum Variants + +| Name | Value | +|---- | -----| +| Invalid | Invalid | + + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ErrorResponse.md b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ErrorResponse.md new file mode 100644 index 0000000..6d24cd0 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ErrorResponse.md @@ -0,0 +1,14 @@ +# TransactionPreviewV2ErrorResponse + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**code** | **i32** | A numeric code corresponding to the given HTTP error code. | +**details** | Option<[**models::TransactionPreviewV2ErrorDetails**](TransactionPreviewV2ErrorDetails.md)> | | [optional] +**message** | **String** | A human-readable error message. | +**trace_id** | Option<**String**> | A GUID to be used when reporting errors, to allow correlation with the Core API's error logs, in the case where the Core API details are hidden. | [optional] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2Request.md b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2Request.md new file mode 100644 index 0000000..481cfe8 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2Request.md @@ -0,0 +1,15 @@ +# TransactionPreviewV2Request + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**at_ledger_state** | Option<[**models::LedgerStateSelector**](LedgerStateSelector.md)> | | [optional] +**flags** | Option<[**models::PreviewFlags**](PreviewFlags.md)> | | [optional] +**network** | **String** | The logical name of the network | +**options** | Option<[**models::TransactionPreviewV2ResponseOptions**](TransactionPreviewV2ResponseOptions.md)> | | [optional] +**preview_transaction** | [**models::PreviewTransaction**](PreviewTransaction.md) | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2Response.md b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2Response.md new file mode 100644 index 0000000..486c5ee --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2Response.md @@ -0,0 +1,14 @@ +# TransactionPreviewV2Response + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**at_ledger_state** | [**models::LedgerStateSummary**](LedgerStateSummary.md) | A summarized state of the ledger on top of which the preview was performed. | +**logs** | Option<[**Vec**](TransactionPreviewResponse_logs_inner.md)> | An optional field which is only provided if the `logs` flag is set to true in the `options` property of the request. If present, it gives the emitted logs from the transaction execution. | [optional] +**radix_engine_toolkit_receipt** | Option<[**serde_json::Value**](.md)> | An optional field which is only provided if the `radix_engine_toolkit_receipt` flag is set to true in the `options` property of the request. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. | [optional] +**receipt** | Option<[**models::TransactionReceipt**](TransactionReceipt.md)> | This is provided unless the `core_api_receipt` flag is set to false in the `options` property of the request. | [optional] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ResponseOptions.md b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ResponseOptions.md new file mode 100644 index 0000000..e032b27 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/TransactionPreviewV2ResponseOptions.md @@ -0,0 +1,13 @@ +# TransactionPreviewV2ResponseOptions + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**core_api_receipt** | Option<**bool**> | This flag controls whether the preview response will include a Core API receipt or not. If not provided, this defaults to `false` and no core api receipt is provided in the response. | [optional] +**logs** | Option<**bool**> | This flag controls whether the preview response will include execution logs. If not provided, this defaults to `false` and no logs will be provided in the response. | [optional] +**radix_engine_toolkit_receipt** | Option<**bool**> | This flag controls whether the preview response will include a Radix Engine Toolkit serializable receipt or not. If not provided, this defaults to `false` and no toolkit receipt is provided in the response. | [optional] + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionReceipt.md b/generated-clients/core-api-client/sync-client/docs/TransactionReceipt.md index 3428842..69286c7 100644 --- a/generated-clients/core-api-client/sync-client/docs/TransactionReceipt.md +++ b/generated-clients/core-api-client/sync-client/docs/TransactionReceipt.md @@ -5,13 +5,13 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- **costing_parameters** | [**models::CostingParameters**](CostingParameters.md) | | -**error_message** | Option<**String**> | Error message (only present if status is `Failed` or `Rejected`) | [optional] +**error_message** | Option<**String**> | The error message. This property is only present if the status is `Failed` or `Rejected`. | [optional] **events** | Option<[**Vec**](Event.md)> | | [optional] **fee_destination** | Option<[**models::FeeDestination**](FeeDestination.md)> | Only present if the `status` is not `Rejected`. | [optional] **fee_source** | Option<[**models::FeeSource**](FeeSource.md)> | Only present if the `status` is not `Rejected`. | [optional] **fee_summary** | [**models::FeeSummary**](FeeSummary.md) | | **next_epoch** | Option<[**models::NextEpoch**](NextEpoch.md)> | | [optional] -**output** | Option<[**Vec**](SborData.md)> | The manifest line-by-line engine return data (only present if `status` is `Succeeded`) | [optional] +**output** | Option<[**Vec**](SborData.md)> | The return data for each line of the transaction intent's manifest. This property is only present if the `status` is `Succeeded`. | [optional] **state_updates** | [**models::StateUpdates**](StateUpdates.md) | | **status** | [**models::TransactionStatus**](TransactionStatus.md) | | diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionSubmitPriorityThresholdNotMetErrorDetails.md b/generated-clients/core-api-client/sync-client/docs/TransactionSubmitPriorityThresholdNotMetErrorDetails.md index 49bd332..9d1b2a2 100644 --- a/generated-clients/core-api-client/sync-client/docs/TransactionSubmitPriorityThresholdNotMetErrorDetails.md +++ b/generated-clients/core-api-client/sync-client/docs/TransactionSubmitPriorityThresholdNotMetErrorDetails.md @@ -4,8 +4,10 @@ Name | Type | Description | Notes ------------ | ------------- | ------------- | ------------- -**min_tip_percentage_required** | Option<**u32**> | A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] -**tip_percentage** | **u32** | Tip percentage of the submitted (and rejected) transaction. | +**min_tip_percentage_required** | Option<**u32**> | NOTE: This is kept for backwards compatibility, but we recommend using `min_tip_proportion_required` instead. A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] +**min_tip_proportion_required** | Option<**String**> | A lower bound for tip proportion at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. | [optional] +**tip_percentage** | **u32** | NOTE: This is kept for backwards compatibility, but we recommend using `tip_proportion` instead. Tip percentage of the submitted (and rejected) transaction. For V2 transactions specifying basis point tips, the amount is rounded down. | +**tip_proportion** | Option<**String**> | The string-encoded decimal tip proportion of the submitted (and rejected) transaction. This field will always be present on Cuttlefish nodes, but is marked as not-required for Cuttlefish launch, to avoid a dependency on clients to update after the node is updated. | [optional] [[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) diff --git a/generated-clients/core-api-client/sync-client/docs/TransactionValidationConfig.md b/generated-clients/core-api-client/sync-client/docs/TransactionValidationConfig.md new file mode 100644 index 0000000..15767be --- /dev/null +++ b/generated-clients/core-api-client/sync-client/docs/TransactionValidationConfig.md @@ -0,0 +1,26 @@ +# TransactionValidationConfig + +## Properties + +Name | Type | Description | Notes +------------ | ------------- | ------------- | ------------- +**manifest_validation** | [**models::ManifestValidationRuleset**](ManifestValidationRuleset.md) | | +**max_epoch_range** | **String** | | +**max_instructions** | **String** | | +**max_references_per_intent** | **String** | | +**max_signer_signatures_per_intent** | **String** | | +**max_subintent_depth** | **String** | | +**max_tip_basis_points** | **u64** | | +**max_tip_percentage** | **u32** | Only applies to V1 transactions | +**max_total_references** | **String** | | +**max_total_signature_validations** | **String** | | +**message_validation** | [**models::MessageValidationConfig**](MessageValidationConfig.md) | | +**min_tip_basis_points** | **u64** | | +**min_tip_percentage** | **u32** | Only applies to V1 transactions | +**preparation_settings** | [**models::PreparationSettings**](PreparationSettings.md) | | +**v1_transactions_allow_notary_to_duplicate_signer** | **bool** | | +**v2_transactions_allowed** | **bool** | | + +[[Back to Model list]](../README.md#documentation-for-models) [[Back to API list]](../README.md#documentation-for-api-endpoints) [[Back to README]](../README.md) + + diff --git a/generated-clients/core-api-client/sync-client/src/apis/configuration.rs b/generated-clients/core-api-client/sync-client/src/apis/configuration.rs index 2fa29bd..6c96c56 100644 --- a/generated-clients/core-api-client/sync-client/src/apis/configuration.rs +++ b/generated-clients/core-api-client/sync-client/src/apis/configuration.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -41,7 +41,7 @@ impl Default for Configuration { fn default() -> Self { Configuration { base_path: "http://localhost:3333/core".to_owned(), - user_agent: Some("OpenAPI-Generator/v1.2.3/rust".to_owned()), + user_agent: Some("OpenAPI-Generator/v1.3.0/rust".to_owned()), client: reqwest::blocking::Client::new(), basic_auth: None, oauth_access_token: None, diff --git a/generated-clients/core-api-client/sync-client/src/apis/lts_api.rs b/generated-clients/core-api-client/sync-client/src/apis/lts_api.rs index b6f79ae..af0aafe 100644 --- a/generated-clients/core-api-client/sync-client/src/apis/lts_api.rs +++ b/generated-clients/core-api-client/sync-client/src/apis/lts_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/apis/mempool_api.rs b/generated-clients/core-api-client/sync-client/src/apis/mempool_api.rs index 3275de7..da58697 100644 --- a/generated-clients/core-api-client/sync-client/src/apis/mempool_api.rs +++ b/generated-clients/core-api-client/sync-client/src/apis/mempool_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/apis/state_api.rs b/generated-clients/core-api-client/sync-client/src/apis/state_api.rs index 86574a9..b60b0ff 100644 --- a/generated-clients/core-api-client/sync-client/src/apis/state_api.rs +++ b/generated-clients/core-api-client/sync-client/src/apis/state_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/apis/status_api.rs b/generated-clients/core-api-client/sync-client/src/apis/status_api.rs index e3bc3cb..9311d3c 100644 --- a/generated-clients/core-api-client/sync-client/src/apis/status_api.rs +++ b/generated-clients/core-api-client/sync-client/src/apis/status_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/apis/stream_api.rs b/generated-clients/core-api-client/sync-client/src/apis/stream_api.rs index 6a287fd..12360ec 100644 --- a/generated-clients/core-api-client/sync-client/src/apis/stream_api.rs +++ b/generated-clients/core-api-client/sync-client/src/apis/stream_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/apis/transaction_api.rs b/generated-clients/core-api-client/sync-client/src/apis/transaction_api.rs index 6f0c518..b3c6e07 100644 --- a/generated-clients/core-api-client/sync-client/src/apis/transaction_api.rs +++ b/generated-clients/core-api-client/sync-client/src/apis/transaction_api.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -42,6 +42,15 @@ pub enum TransactionPreviewPostError { UnknownValue(serde_json::Value), } +/// struct for typed errors of method [`transaction_preview_v2_post`] +#[derive(Debug, Clone, Serialize, Deserialize)] +#[serde(untagged)] +pub enum TransactionPreviewV2PostError { + Status400(models::TransactionPreviewV2ErrorResponse), + Status500(models::TransactionPreviewV2ErrorResponse), + UnknownValue(serde_json::Value), +} + /// struct for typed errors of method [`transaction_receipt_post`] #[derive(Debug, Clone, Serialize, Deserialize)] #[serde(untagged)] @@ -129,7 +138,7 @@ pub fn transaction_parse_post(configuration: &configuration::Configuration, tran } } -/// Preview a transaction against the latest network state, and returns the preview receipt. +/// Preview a transaction against the latest network state, and returns the preview receipt. If the node has enabled it, you may be able to also preview against recent network state. For V2 transactions (and beyond) the `/preview-v2` endpoint should be used instead. pub fn transaction_preview_post(configuration: &configuration::Configuration, transaction_preview_request: models::TransactionPreviewRequest) -> Result> { let local_var_configuration = configuration; @@ -158,6 +167,35 @@ pub fn transaction_preview_post(configuration: &configuration::Configuration, tr } } +/// Previews a transaction against the latest network state, and returns the preview receipt. If the node has enabled it, you may be able to also preview against recent network state. This endpoint supports V2 transactions (and beyond). If you still need to preview V1 transactions, you should use the `/preview` endpoint instead. +pub fn transaction_preview_v2_post(configuration: &configuration::Configuration, transaction_preview_v2_request: models::TransactionPreviewV2Request) -> Result> { + let local_var_configuration = configuration; + + let local_var_client = &local_var_configuration.client; + + let local_var_uri_str = format!("{}/transaction/preview-v2", local_var_configuration.base_path); + let mut local_var_req_builder = local_var_client.request(reqwest::Method::POST, local_var_uri_str.as_str()); + + if let Some(ref local_var_user_agent) = local_var_configuration.user_agent { + local_var_req_builder = local_var_req_builder.header(reqwest::header::USER_AGENT, local_var_user_agent.clone()); + } + local_var_req_builder = local_var_req_builder.json(&transaction_preview_v2_request); + + let local_var_req = local_var_req_builder.build()?; + let local_var_resp = local_var_client.execute(local_var_req)?; + + let local_var_status = local_var_resp.status(); + let local_var_content = local_var_resp.text()?; + + if !local_var_status.is_client_error() && !local_var_status.is_server_error() { + serde_json::from_str(&local_var_content).map_err(Error::from) + } else { + let local_var_entity: Option = serde_json::from_str(&local_var_content).ok(); + let local_var_error = ResponseContent { status: local_var_status, content: local_var_content, entity: local_var_entity }; + Err(Error::ResponseError(local_var_error)) + } +} + /// Gets the transaction receipt for a committed transaction. pub fn transaction_receipt_post(configuration: &configuration::Configuration, transaction_receipt_request: models::TransactionReceiptRequest) -> Result> { let local_var_configuration = configuration; diff --git a/generated-clients/core-api-client/sync-client/src/models/access_controller_field_state_substate.rs b/generated-clients/core-api-client/sync-client/src/models/access_controller_field_state_substate.rs index 895f65d..d709a22 100644 --- a/generated-clients/core-api-client/sync-client/src/models/access_controller_field_state_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/access_controller_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/access_controller_field_state_value.rs b/generated-clients/core-api-client/sync-client/src/models/access_controller_field_state_value.rs index f056d24..3e43f16 100644 --- a/generated-clients/core-api-client/sync-client/src/models/access_controller_field_state_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/access_controller_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/access_rule.rs b/generated-clients/core-api-client/sync-client/src/models/access_rule.rs index ab2ec13..0eba7da 100644 --- a/generated-clients/core-api-client/sync-client/src/models/access_rule.rs +++ b/generated-clients/core-api-client/sync-client/src/models/access_rule.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,6 +11,7 @@ use crate::models; use serde::{Deserialize, Serialize}; +/// AccessRule : A representation of an access rule in the Radix Engine. Note that some of the field and discriminator names use an older naming schema, for backwards compatibility. See the [advanced access rules](https://docs.radixdlt.com/docs/advanced-accessrules) docs for more information. #[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] #[serde(tag = "type")] pub enum AccessRule { diff --git a/generated-clients/core-api-client/sync-client/src/models/access_rule_type.rs b/generated-clients/core-api-client/sync-client/src/models/access_rule_type.rs index 1bbe63a..a073343 100644 --- a/generated-clients/core-api-client/sync-client/src/models/access_rule_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/access_rule_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/account_address_key.rs b/generated-clients/core-api-client/sync-client/src/models/account_address_key.rs index 0109dce..08d53ac 100644 --- a/generated-clients/core-api-client/sync-client/src/models/account_address_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/account_address_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/account_authorized_depositor_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/account_authorized_depositor_entry_substate.rs index 4ed5b8f..88eada4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/account_authorized_depositor_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/account_authorized_depositor_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/account_authorized_depositor_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/account_authorized_depositor_entry_value.rs index d95d188..edeb3a7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/account_authorized_depositor_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/account_authorized_depositor_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/account_field_state_substate.rs b/generated-clients/core-api-client/sync-client/src/models/account_field_state_substate.rs index ededb98..a8ae81a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/account_field_state_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/account_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/account_field_state_value.rs b/generated-clients/core-api-client/sync-client/src/models/account_field_state_value.rs index bbdb649..5bb8eac 100644 --- a/generated-clients/core-api-client/sync-client/src/models/account_field_state_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/account_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/account_locker_account_claims_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/account_locker_account_claims_entry_substate.rs index 82fccd2..13ce6d8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/account_locker_account_claims_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/account_locker_account_claims_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/account_locker_account_claims_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/account_locker_account_claims_entry_value.rs index 99a1f66..8cffb50 100644 --- a/generated-clients/core-api-client/sync-client/src/models/account_locker_account_claims_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/account_locker_account_claims_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/account_resource_preference_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/account_resource_preference_entry_substate.rs index 4f27cd5..7421080 100644 --- a/generated-clients/core-api-client/sync-client/src/models/account_resource_preference_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/account_resource_preference_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/account_resource_preference_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/account_resource_preference_entry_value.rs index 3f82e1a..a1fadb7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/account_resource_preference_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/account_resource_preference_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/account_vault_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/account_vault_entry_substate.rs index 880178f..57692a3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/account_vault_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/account_vault_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/account_vault_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/account_vault_entry_value.rs index 53f6a68..d54f8ae 100644 --- a/generated-clients/core-api-client/sync-client/src/models/account_vault_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/account_vault_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/active_validator.rs b/generated-clients/core-api-client/sync-client/src/models/active_validator.rs index e8512aa..a6836aa 100644 --- a/generated-clients/core-api-client/sync-client/src/models/active_validator.rs +++ b/generated-clients/core-api-client/sync-client/src/models/active_validator.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/active_validator_index.rs b/generated-clients/core-api-client/sync-client/src/models/active_validator_index.rs index 55fd828..26da2d6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/active_validator_index.rs +++ b/generated-clients/core-api-client/sync-client/src/models/active_validator_index.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/active_validator_key.rs b/generated-clients/core-api-client/sync-client/src/models/active_validator_key.rs index acc55a9..371e491 100644 --- a/generated-clients/core-api-client/sync-client/src/models/active_validator_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/active_validator_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/address_type.rs b/generated-clients/core-api-client/sync-client/src/models/address_type.rs index bbf8a30..4c2ae85 100644 --- a/generated-clients/core-api-client/sync-client/src/models/address_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/address_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/any_of_proof_rule.rs b/generated-clients/core-api-client/sync-client/src/models/all_of_basic_requirement.rs similarity index 90% rename from generated-clients/core-api-client/async-client/src/models/any_of_proof_rule.rs rename to generated-clients/core-api-client/sync-client/src/models/all_of_basic_requirement.rs index 69f8e89..c630f64 100644 --- a/generated-clients/core-api-client/async-client/src/models/any_of_proof_rule.rs +++ b/generated-clients/core-api-client/sync-client/src/models/all_of_basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct AnyOfProofRule { +pub struct AllOfBasicRequirement { #[serde(rename = "list")] pub list: Vec, } -impl AnyOfProofRule { - pub fn new(list: Vec) -> AnyOfProofRule { - AnyOfProofRule { +impl AllOfBasicRequirement { + pub fn new(list: Vec) -> AllOfBasicRequirement { + AllOfBasicRequirement { list, } } diff --git a/generated-clients/core-api-client/sync-client/src/models/any_of_access_rule_node.rs b/generated-clients/core-api-client/sync-client/src/models/all_of_composite_requirement.rs similarity index 87% rename from generated-clients/core-api-client/sync-client/src/models/any_of_access_rule_node.rs rename to generated-clients/core-api-client/sync-client/src/models/all_of_composite_requirement.rs index e481eb4..7603b02 100644 --- a/generated-clients/core-api-client/sync-client/src/models/any_of_access_rule_node.rs +++ b/generated-clients/core-api-client/sync-client/src/models/all_of_composite_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct AnyOfAccessRuleNode { +pub struct AllOfCompositeRequirement { #[serde(rename = "access_rules")] - pub access_rules: Vec, + pub access_rules: Vec, } -impl AnyOfAccessRuleNode { - pub fn new(access_rules: Vec) -> AnyOfAccessRuleNode { - AnyOfAccessRuleNode { +impl AllOfCompositeRequirement { + pub fn new(access_rules: Vec) -> AllOfCompositeRequirement { + AllOfCompositeRequirement { access_rules, } } diff --git a/generated-clients/core-api-client/sync-client/src/models/always_visible_global_nodes_version.rs b/generated-clients/core-api-client/sync-client/src/models/always_visible_global_nodes_version.rs index ad022e7..5d20ff5 100644 --- a/generated-clients/core-api-client/sync-client/src/models/always_visible_global_nodes_version.rs +++ b/generated-clients/core-api-client/sync-client/src/models/always_visible_global_nodes_version.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/amount_of_proof_rule.rs b/generated-clients/core-api-client/sync-client/src/models/amount_of_basic_requirement.rs similarity index 90% rename from generated-clients/core-api-client/async-client/src/models/amount_of_proof_rule.rs rename to generated-clients/core-api-client/sync-client/src/models/amount_of_basic_requirement.rs index c019f33..0772c94 100644 --- a/generated-clients/core-api-client/async-client/src/models/amount_of_proof_rule.rs +++ b/generated-clients/core-api-client/sync-client/src/models/amount_of_basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,7 +12,7 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct AmountOfProofRule { +pub struct AmountOfBasicRequirement { #[serde(rename = "amount")] pub amount: String, /// The Bech32m-encoded human readable version of the resource address @@ -20,9 +20,9 @@ pub struct AmountOfProofRule { pub resource: String, } -impl AmountOfProofRule { - pub fn new(amount: String, resource: String) -> AmountOfProofRule { - AmountOfProofRule { +impl AmountOfBasicRequirement { + pub fn new(amount: String, resource: String) -> AmountOfBasicRequirement { + AmountOfBasicRequirement { amount, resource, } diff --git a/generated-clients/core-api-client/sync-client/src/models/all_of_proof_rule.rs b/generated-clients/core-api-client/sync-client/src/models/any_of_basic_requirement.rs similarity index 90% rename from generated-clients/core-api-client/sync-client/src/models/all_of_proof_rule.rs rename to generated-clients/core-api-client/sync-client/src/models/any_of_basic_requirement.rs index c8cf7b9..aac58bd 100644 --- a/generated-clients/core-api-client/sync-client/src/models/all_of_proof_rule.rs +++ b/generated-clients/core-api-client/sync-client/src/models/any_of_basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct AllOfProofRule { +pub struct AnyOfBasicRequirement { #[serde(rename = "list")] pub list: Vec, } -impl AllOfProofRule { - pub fn new(list: Vec) -> AllOfProofRule { - AllOfProofRule { +impl AnyOfBasicRequirement { + pub fn new(list: Vec) -> AnyOfBasicRequirement { + AnyOfBasicRequirement { list, } } diff --git a/generated-clients/core-api-client/async-client/src/models/all_of_access_rule_node.rs b/generated-clients/core-api-client/sync-client/src/models/any_of_composite_requirement.rs similarity index 87% rename from generated-clients/core-api-client/async-client/src/models/all_of_access_rule_node.rs rename to generated-clients/core-api-client/sync-client/src/models/any_of_composite_requirement.rs index 441cb14..dacd1c0 100644 --- a/generated-clients/core-api-client/async-client/src/models/all_of_access_rule_node.rs +++ b/generated-clients/core-api-client/sync-client/src/models/any_of_composite_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct AllOfAccessRuleNode { +pub struct AnyOfCompositeRequirement { #[serde(rename = "access_rules")] - pub access_rules: Vec, + pub access_rules: Vec, } -impl AllOfAccessRuleNode { - pub fn new(access_rules: Vec) -> AllOfAccessRuleNode { - AllOfAccessRuleNode { +impl AnyOfCompositeRequirement { + pub fn new(access_rules: Vec) -> AnyOfCompositeRequirement { + AnyOfCompositeRequirement { access_rules, } } diff --git a/generated-clients/core-api-client/sync-client/src/models/attached_module_id.rs b/generated-clients/core-api-client/sync-client/src/models/attached_module_id.rs index 16418ee..459d61d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/attached_module_id.rs +++ b/generated-clients/core-api-client/sync-client/src/models/attached_module_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/auth_config.rs b/generated-clients/core-api-client/sync-client/src/models/auth_config.rs index 116ce09..6208cee 100644 --- a/generated-clients/core-api-client/sync-client/src/models/auth_config.rs +++ b/generated-clients/core-api-client/sync-client/src/models/auth_config.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_badge.rs b/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_badge.rs index 524ecb1..354e837 100644 --- a/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_badge.rs +++ b/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_badge_type.rs b/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_badge_type.rs index 65c5a8c..089b7b2 100644 --- a/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_badge_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_badge_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_key.rs b/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_key.rs index 88a0527..4593708 100644 --- a/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/authorized_depositor_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/basic_error_response.rs b/generated-clients/core-api-client/sync-client/src/models/basic_error_response.rs index 6737a21..ae0f8c8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/basic_error_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/basic_error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/proof_rule.rs b/generated-clients/core-api-client/sync-client/src/models/basic_requirement.rs similarity index 87% rename from generated-clients/core-api-client/sync-client/src/models/proof_rule.rs rename to generated-clients/core-api-client/sync-client/src/models/basic_requirement.rs index 2c8585d..da6fa0f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/proof_rule.rs +++ b/generated-clients/core-api-client/sync-client/src/models/basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -13,20 +13,20 @@ use serde::{Deserialize, Serialize}; #[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] #[serde(tag = "type")] -pub enum ProofRule { +pub enum BasicRequirement { #[serde(rename="Require")] - Require(models::RequireProofRule), + Require(models::RequireBasicRequirement), #[serde(rename="AmountOf")] - AmountOf(models::AmountOfProofRule), + AmountOf(models::AmountOfBasicRequirement), #[serde(rename="AllOf")] - AllOf(models::AllOfProofRule), + AllOf(models::AllOfBasicRequirement), #[serde(rename="AnyOf")] - AnyOf(models::AnyOfProofRule), + AnyOf(models::AnyOfBasicRequirement), #[serde(rename="CountOf")] - CountOf(models::CountOfProofRule), + CountOf(models::CountOfBasicRequirement), } -impl Default for ProofRule { +impl Default for BasicRequirement { fn default() -> Self { Self::Require(Default::default()) } diff --git a/generated-clients/core-api-client/sync-client/src/models/proof_rule_type.rs b/generated-clients/core-api-client/sync-client/src/models/basic_requirement_type.rs similarity index 92% rename from generated-clients/core-api-client/sync-client/src/models/proof_rule_type.rs rename to generated-clients/core-api-client/sync-client/src/models/basic_requirement_type.rs index 8bdb708..dae9ac0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/proof_rule_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/basic_requirement_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -13,7 +13,7 @@ use serde::{Deserialize, Serialize}; /// #[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] -pub enum ProofRuleType { +pub enum BasicRequirementType { #[serde(rename = "Require")] Require, #[serde(rename = "AmountOf")] @@ -27,7 +27,7 @@ pub enum ProofRuleType { } -impl std::fmt::Display for ProofRuleType { +impl std::fmt::Display for BasicRequirementType { fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { match self { Self::Require => write!(f, "Require"), @@ -39,8 +39,8 @@ impl std::fmt::Display for ProofRuleType { } } -impl Default for ProofRuleType { - fn default() -> ProofRuleType { +impl Default for BasicRequirementType { + fn default() -> BasicRequirementType { Self::Require } } diff --git a/generated-clients/core-api-client/sync-client/src/models/binary_plaintext_message_content.rs b/generated-clients/core-api-client/sync-client/src/models/binary_plaintext_message_content.rs index abe301c..c6876a1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/binary_plaintext_message_content.rs +++ b/generated-clients/core-api-client/sync-client/src/models/binary_plaintext_message_content.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_collection_schema.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_collection_schema.rs index 54f34f8..9a19ad5 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_collection_schema.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_collection_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_collection_schema_type.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_collection_schema_type.rs index 3515099..ad74392 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_collection_schema_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_collection_schema_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_definition.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_definition.rs index 56e8e2f..3baaf1f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_definition.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_definition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_dependencies.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_dependencies.rs index ec5606a..95fe488 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_dependencies.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_dependencies.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_function_target_identifier.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_function_target_identifier.rs index 43b5703..62155d2 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_function_target_identifier.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_function_target_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_info.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_info.rs index 8d5d432..3d49384 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_info.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_info.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_interface.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_interface.rs index 6be5ab3..5b771c4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_interface.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_interface.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_method_royalty.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_method_royalty.rs index a11dd5c..f532054 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_method_royalty.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_method_royalty.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_payload_def.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_payload_def.rs index 29f307b..20e1f5c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_payload_def.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_payload_def.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_payload_def_type.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_payload_def_type.rs index 6f68ec0..ead6943 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_payload_def_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_payload_def_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_royalty_config.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_royalty_config.rs index 25c7d36..579ef2d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_royalty_config.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_royalty_config.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_blueprint_type_reference.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_blueprint_type_reference.rs index 92858f4..c7af549 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_blueprint_type_reference.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_blueprint_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_collection_partition.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_collection_partition.rs index 508e35e..5d88bc2 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_collection_partition.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_collection_partition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_field_partition.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_field_partition.rs index e40d039..dda3721 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_field_partition.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_schema_field_partition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_type_identifier.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_type_identifier.rs index 665a89d..23458c0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_type_identifier.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_type_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_type_reference.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_type_reference.rs index 4a3c188..6fe3838 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_type_reference.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_type_reference_kind.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_type_reference_kind.rs index d96dc35..fa78acf 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_type_reference_kind.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_type_reference_kind.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/blueprint_version_key.rs b/generated-clients/core-api-client/sync-client/src/models/blueprint_version_key.rs index c0a69a6..d0d2baa 100644 --- a/generated-clients/core-api-client/sync-client/src/models/blueprint_version_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/blueprint_version_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_kernel_boot_substate.rs b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_kernel_boot_substate.rs index eb16e5f..29cfd66 100644 --- a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_kernel_boot_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_kernel_boot_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_kernel_boot_value.rs b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_kernel_boot_value.rs index 647eb45..cb17b5d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_kernel_boot_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_kernel_boot_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_system_boot_substate.rs b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_system_boot_substate.rs index 68f1d04..fb8edf1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_system_boot_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_system_boot_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_system_boot_value.rs b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_system_boot_value.rs index c1ef37a..cef5474 100644 --- a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_system_boot_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_system_boot_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_transaction_validation_configuration_substate.rs b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_transaction_validation_configuration_substate.rs index a0d817f..2a25c75 100644 --- a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_transaction_validation_configuration_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_transaction_validation_configuration_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -13,13 +13,16 @@ use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] pub struct BootLoaderModuleFieldTransactionValidationConfigurationSubstate { + #[serde(rename = "config")] + pub config: models::TransactionValidationConfig, #[serde(rename = "is_locked")] pub is_locked: bool, } impl BootLoaderModuleFieldTransactionValidationConfigurationSubstate { - pub fn new(is_locked: bool) -> BootLoaderModuleFieldTransactionValidationConfigurationSubstate { + pub fn new(config: models::TransactionValidationConfig, is_locked: bool) -> BootLoaderModuleFieldTransactionValidationConfigurationSubstate { BootLoaderModuleFieldTransactionValidationConfigurationSubstate { + config, is_locked, } } diff --git a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_vm_boot_substate.rs b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_vm_boot_substate.rs index cde5c22..b19c523 100644 --- a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_vm_boot_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_vm_boot_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_vm_boot_value.rs b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_vm_boot_value.rs index 4a13f59..0970e17 100644 --- a/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_vm_boot_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/boot_loader_module_field_vm_boot_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/committed_intent_metadata.rs b/generated-clients/core-api-client/sync-client/src/models/committed_intent_metadata.rs index 80c60e9..7c05823 100644 --- a/generated-clients/core-api-client/sync-client/src/models/committed_intent_metadata.rs +++ b/generated-clients/core-api-client/sync-client/src/models/committed_intent_metadata.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/committed_state_identifier.rs b/generated-clients/core-api-client/sync-client/src/models/committed_state_identifier.rs index e5f9e91..6f8213f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/committed_state_identifier.rs +++ b/generated-clients/core-api-client/sync-client/src/models/committed_state_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/committed_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/committed_transaction.rs index 6d497f0..416a100 100644 --- a/generated-clients/core-api-client/sync-client/src/models/committed_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/committed_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/committed_transaction_balance_changes.rs b/generated-clients/core-api-client/sync-client/src/models/committed_transaction_balance_changes.rs index 9f51914..a325b9c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/committed_transaction_balance_changes.rs +++ b/generated-clients/core-api-client/sync-client/src/models/committed_transaction_balance_changes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/compiled_preview_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/compiled_preview_transaction.rs new file mode 100644 index 0000000..7a57d62 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/compiled_preview_transaction.rs @@ -0,0 +1,28 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct CompiledPreviewTransaction { + /// A hex-encoded, compiled `RawPreviewTransaction`. As of Cuttlefish, only `PreviewTransactionV2` is supported. A `PreviewTransactionV2` can be created with a v2 transaction builder: * If using Rust, it can be created with a `TransactionV2Builder` using `build_preview_transaction()` and then converted to hex with `preview_transaction.to_raw().unwrap().to_hex()` * If using the toolkit, you can create this using the v2 transaction builder. Some subtleties: * Partial transactions can't be previewed. Instead, they must be wrapped inside a transaction wrapper, so that the engine knows how to yield to them appropriately. * Currently the builder assumes that the signed partial transactions have real signatures. This isn't strictly required, and we may create a builder in future which allows providing public keys when building partial transactions for use in preview. * If you don't have signatures to hand, you can simply not sign the partial transactions, and then use the `assume_all_signature_proofs` preview flag, although be advised that this may result in the fee estimate being slightly lower during preview. * We may create more ergonomic builders for PreviewTransactions which allow use of public keys to denote the signers of subintents. Let us know if this is important for your use case. + #[serde(rename = "preview_transaction_hex")] + pub preview_transaction_hex: String, +} + +impl CompiledPreviewTransaction { + pub fn new(preview_transaction_hex: String) -> CompiledPreviewTransaction { + CompiledPreviewTransaction { + preview_transaction_hex, + } + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/component_method_target_identifier.rs b/generated-clients/core-api-client/sync-client/src/models/component_method_target_identifier.rs index a20ac81..1434bf4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/component_method_target_identifier.rs +++ b/generated-clients/core-api-client/sync-client/src/models/component_method_target_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/access_rule_node.rs b/generated-clients/core-api-client/sync-client/src/models/composite_requirement.rs similarity index 86% rename from generated-clients/core-api-client/sync-client/src/models/access_rule_node.rs rename to generated-clients/core-api-client/sync-client/src/models/composite_requirement.rs index 1fe6d75..204c475 100644 --- a/generated-clients/core-api-client/sync-client/src/models/access_rule_node.rs +++ b/generated-clients/core-api-client/sync-client/src/models/composite_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,18 +11,19 @@ use crate::models; use serde::{Deserialize, Serialize}; +/// CompositeRequirement : This type was historically called `AccessRuleNode`. #[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] #[serde(tag = "type")] -pub enum AccessRuleNode { +pub enum CompositeRequirement { #[serde(rename="ProofRule")] - ProofRule(models::ProofAccessRuleNode), + ProofRule(models::ProofRuleCompositeRequirement), #[serde(rename="AnyOf")] - AnyOf(models::AnyOfAccessRuleNode), + AnyOf(models::AnyOfCompositeRequirement), #[serde(rename="AllOf")] - AllOf(models::AllOfAccessRuleNode), + AllOf(models::AllOfCompositeRequirement), } -impl Default for AccessRuleNode { +impl Default for CompositeRequirement { fn default() -> Self { Self::ProofRule(Default::default()) } diff --git a/generated-clients/core-api-client/async-client/src/models/access_rule_node_type.rs b/generated-clients/core-api-client/sync-client/src/models/composite_requirement_type.rs similarity index 87% rename from generated-clients/core-api-client/async-client/src/models/access_rule_node_type.rs rename to generated-clients/core-api-client/sync-client/src/models/composite_requirement_type.rs index be711f2..92f2194 100644 --- a/generated-clients/core-api-client/async-client/src/models/access_rule_node_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/composite_requirement_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,9 +11,10 @@ use crate::models; use serde::{Deserialize, Serialize}; -/// +/// CompositeRequirementType : `ProofRule` is now called `BasicRequirement`. +/// `ProofRule` is now called `BasicRequirement`. #[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] -pub enum AccessRuleNodeType { +pub enum CompositeRequirementType { #[serde(rename = "ProofRule")] ProofRule, #[serde(rename = "AnyOf")] @@ -23,7 +24,7 @@ pub enum AccessRuleNodeType { } -impl std::fmt::Display for AccessRuleNodeType { +impl std::fmt::Display for CompositeRequirementType { fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { match self { Self::ProofRule => write!(f, "ProofRule"), @@ -33,8 +34,8 @@ impl std::fmt::Display for AccessRuleNodeType { } } -impl Default for AccessRuleNodeType { - fn default() -> AccessRuleNodeType { +impl Default for CompositeRequirementType { + fn default() -> CompositeRequirementType { Self::ProofRule } } diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_ledger_proof_origin.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_ledger_proof_origin.rs index 24df61d..2e99e35 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_ledger_proof_origin.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_ledger_proof_origin.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_config_substate.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_config_substate.rs index 8bcca99..f0473aa 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_config_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_config_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_config_value.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_config_value.rs index ff85bde..3568ed2 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_config_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_config_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_proposal_statistic_substate.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_proposal_statistic_substate.rs index d3356fa..7dfa45a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_proposal_statistic_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_proposal_statistic_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_proposal_statistic_value.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_proposal_statistic_value.rs index 442d508..21b2cdc 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_proposal_statistic_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_proposal_statistic_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs index 0d34f43..3c0a921 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs index 189c04b..93876b3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_substate.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_substate.rs index 0682420..caf1c96 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_value.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_value.rs index 9091210..1b81e40 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_time_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_validator_set_substate.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_validator_set_substate.rs index 88a06c7..a745f43 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_validator_set_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_validator_set_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_validator_set_value.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_validator_set_value.rs index c41dca0..9c874a7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_validator_set_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_current_validator_set_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_state_substate.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_state_substate.rs index 214a93c..743705c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_state_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_state_value.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_state_value.rs index e35c34f..2e49345 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_state_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_validator_rewards_substate.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_validator_rewards_substate.rs index f51ee82..3a51bdc 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_validator_rewards_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_validator_rewards_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_validator_rewards_value.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_validator_rewards_value.rs index 39accad..ae08268 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_validator_rewards_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_field_validator_rewards_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs index 65deed9..ab600ae 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs index 82280c1..f1978a7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/costing_module_config.rs b/generated-clients/core-api-client/sync-client/src/models/costing_module_config.rs index 058ac8e..d064a54 100644 --- a/generated-clients/core-api-client/sync-client/src/models/costing_module_config.rs +++ b/generated-clients/core-api-client/sync-client/src/models/costing_module_config.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/costing_parameters.rs b/generated-clients/core-api-client/sync-client/src/models/costing_parameters.rs index 2b62252..7702b4a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/costing_parameters.rs +++ b/generated-clients/core-api-client/sync-client/src/models/costing_parameters.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -28,9 +28,12 @@ pub struct CostingParameters { /// The string-encoded decimal representing the XRD price of a single cost unit of transaction finalization. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. #[serde(rename = "finalization_cost_unit_price")] pub finalization_cost_unit_price: String, - /// An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to 1% of the fee. + /// NOTE: V2 transactions specify the tip in basis points, which gets rounded down for this `tip_percentage` field. It is recommended to instead use the `tip_proportion` field to get a fully accurate value. An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to 1% of the fee. #[serde(rename = "tip_percentage")] pub tip_percentage: u32, + /// A string-encoded decimal, giving the validator tip as a proportional amount. A value of `\"0.01\"` corresponds to 1% of the fee being paid as a tip. NOTE: This field is not marked as required for Cuttlefish launch, to permit cuttlefish clients to talk to pre-cuttlefish nodes. This can be changed after Cuttlefish enactment once all nodes are on Cuttlefish. + #[serde(rename = "tip_proportion", skip_serializing_if = "Option::is_none")] + pub tip_proportion: Option, /// The string-encoded decimal representing the price of 1 byte of archive storage, expressed in XRD. A decimal is formed of some signed integer `m` of attos (`10^(-18)`) units, where `-2^(192 - 1) <= m < 2^(192 - 1)`. #[serde(rename = "xrd_archive_storage_price")] pub xrd_archive_storage_price: String, @@ -51,6 +54,7 @@ impl CostingParameters { finalization_cost_unit_limit, finalization_cost_unit_price, tip_percentage, + tip_proportion: None, xrd_archive_storage_price, xrd_storage_price, xrd_usd_price, diff --git a/generated-clients/core-api-client/async-client/src/models/count_of_proof_rule.rs b/generated-clients/core-api-client/sync-client/src/models/count_of_basic_requirement.rs similarity index 92% rename from generated-clients/core-api-client/async-client/src/models/count_of_proof_rule.rs rename to generated-clients/core-api-client/sync-client/src/models/count_of_basic_requirement.rs index b240d16..eed045d 100644 --- a/generated-clients/core-api-client/async-client/src/models/count_of_proof_rule.rs +++ b/generated-clients/core-api-client/sync-client/src/models/count_of_basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,16 +12,16 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct CountOfProofRule { +pub struct CountOfBasicRequirement { #[serde(rename = "count")] pub count: i32, #[serde(rename = "list")] pub list: Vec, } -impl CountOfProofRule { - pub fn new(count: i32, list: Vec) -> CountOfProofRule { - CountOfProofRule { +impl CountOfBasicRequirement { + pub fn new(count: i32, list: Vec) -> CountOfBasicRequirement { + CountOfBasicRequirement { count, list, } diff --git a/generated-clients/core-api-client/sync-client/src/models/created_substate.rs b/generated-clients/core-api-client/sync-client/src/models/created_substate.rs index 120eaab..b46eea8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/created_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/created_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/data_struct.rs b/generated-clients/core-api-client/sync-client/src/models/data_struct.rs index 04bd2cf..d1d1f5f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/data_struct.rs +++ b/generated-clients/core-api-client/sync-client/src/models/data_struct.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/default_deposit_rule.rs b/generated-clients/core-api-client/sync-client/src/models/default_deposit_rule.rs index 9945329..f5e17b0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/default_deposit_rule.rs +++ b/generated-clients/core-api-client/sync-client/src/models/default_deposit_rule.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/deleted_substate.rs b/generated-clients/core-api-client/sync-client/src/models/deleted_substate.rs index d178195..9b2dd31 100644 --- a/generated-clients/core-api-client/sync-client/src/models/deleted_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/deleted_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_public_key.rs b/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_public_key.rs index f1da63d..a85c909 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_public_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_signature.rs b/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_signature.rs index 89a07fe..5783707 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_signature.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_signature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_signature_with_public_key.rs b/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_signature_with_public_key.rs index b219e23..4d1cc9a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_signature_with_public_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ecdsa_secp256k1_signature_with_public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_public_key.rs b/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_public_key.rs index 0b1177e..81dee70 100644 --- a/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_public_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_signature.rs b/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_signature.rs index fe7172b..20e4de8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_signature.rs +++ b/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_signature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_signature_with_public_key.rs b/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_signature_with_public_key.rs index 8218fbd..b4a213d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_signature_with_public_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/eddsa_ed25519_signature_with_public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/encrypted_message_curve_decryptor_set.rs b/generated-clients/core-api-client/sync-client/src/models/encrypted_message_curve_decryptor_set.rs index 6e3ce19..031719e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/encrypted_message_curve_decryptor_set.rs +++ b/generated-clients/core-api-client/sync-client/src/models/encrypted_message_curve_decryptor_set.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/encrypted_message_decryptor.rs b/generated-clients/core-api-client/sync-client/src/models/encrypted_message_decryptor.rs index 281632a..09253a2 100644 --- a/generated-clients/core-api-client/sync-client/src/models/encrypted_message_decryptor.rs +++ b/generated-clients/core-api-client/sync-client/src/models/encrypted_message_decryptor.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/encrypted_transaction_message.rs b/generated-clients/core-api-client/sync-client/src/models/encrypted_transaction_message.rs index a91bb36..fda96f3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/encrypted_transaction_message.rs +++ b/generated-clients/core-api-client/sync-client/src/models/encrypted_transaction_message.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/entity_module.rs b/generated-clients/core-api-client/sync-client/src/models/entity_module.rs index 8e4810a..e0f61b6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/entity_module.rs +++ b/generated-clients/core-api-client/sync-client/src/models/entity_module.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/entity_reference.rs b/generated-clients/core-api-client/sync-client/src/models/entity_reference.rs index 2760914..e4fa353 100644 --- a/generated-clients/core-api-client/sync-client/src/models/entity_reference.rs +++ b/generated-clients/core-api-client/sync-client/src/models/entity_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/entity_type.rs b/generated-clients/core-api-client/sync-client/src/models/entity_type.rs index 0a72a63..f3cc3cd 100644 --- a/generated-clients/core-api-client/sync-client/src/models/entity_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/entity_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,7 +11,8 @@ use crate::models; use serde::{Deserialize, Serialize}; -/// +/// EntityType : To improve clarity, some `EntityType` names have been updated at Cuttlefish. But, due to backwards compatibility, the old names continue to be used here. Notably: * `GlobalVirtualSecp256k1Account` is now `GlobalPreallocatedSecp256k1Account` elsewhere * `GlobalVirtualSecp256k1Identity` is now `GlobalPreallocatedSecp256k1Identity` elsewhere * `GlobalVirtualEd25519Account` is now `GlobalPreallocatedEd25519Account` elsewhere * `GlobalVirtualEd25519Identity` is now `GlobalPreallocatedEd25519Identity` elsewhere +/// To improve clarity, some `EntityType` names have been updated at Cuttlefish. But, due to backwards compatibility, the old names continue to be used here. Notably: * `GlobalVirtualSecp256k1Account` is now `GlobalPreallocatedSecp256k1Account` elsewhere * `GlobalVirtualSecp256k1Identity` is now `GlobalPreallocatedSecp256k1Identity` elsewhere * `GlobalVirtualEd25519Account` is now `GlobalPreallocatedEd25519Account` elsewhere * `GlobalVirtualEd25519Identity` is now `GlobalPreallocatedEd25519Identity` elsewhere #[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] pub enum EntityType { #[serde(rename = "GlobalPackage")] diff --git a/generated-clients/core-api-client/sync-client/src/models/epoch_change_condition.rs b/generated-clients/core-api-client/sync-client/src/models/epoch_change_condition.rs index bd0174f..4b78c1a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/epoch_change_condition.rs +++ b/generated-clients/core-api-client/sync-client/src/models/epoch_change_condition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/epoch_end_ledger_proof.rs b/generated-clients/core-api-client/sync-client/src/models/epoch_end_ledger_proof.rs index 0daf347..59acf2f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/epoch_end_ledger_proof.rs +++ b/generated-clients/core-api-client/sync-client/src/models/epoch_end_ledger_proof.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/epoch_round.rs b/generated-clients/core-api-client/sync-client/src/models/epoch_round.rs index 960f41d..2465aa4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/epoch_round.rs +++ b/generated-clients/core-api-client/sync-client/src/models/epoch_round.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/error_response.rs b/generated-clients/core-api-client/sync-client/src/models/error_response.rs index e0e02d5..2e6690b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/error_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -20,6 +20,8 @@ pub enum ErrorResponse { TransactionSubmit(models::TransactionSubmitErrorResponse), #[serde(rename="LtsTransactionSubmit")] LtsTransactionSubmit(models::LtsTransactionSubmitErrorResponse), + #[serde(rename="TransactionPreviewV2")] + TransactionPreviewV2(models::TransactionPreviewV2ErrorResponse), #[serde(rename="StreamTransactions")] StreamTransactions(models::StreamTransactionsErrorResponse), #[serde(rename="StreamProofs")] diff --git a/generated-clients/core-api-client/sync-client/src/models/error_response_type.rs b/generated-clients/core-api-client/sync-client/src/models/error_response_type.rs index 2e81f5f..1d3e2ae 100644 --- a/generated-clients/core-api-client/sync-client/src/models/error_response_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/error_response_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -20,6 +20,8 @@ pub enum ErrorResponseType { TransactionSubmit, #[serde(rename = "LtsTransactionSubmit")] LtsTransactionSubmit, + #[serde(rename = "TransactionPreviewV2")] + TransactionPreviewV2, #[serde(rename = "StreamTransactions")] StreamTransactions, #[serde(rename = "StreamProofs")] @@ -33,6 +35,7 @@ impl std::fmt::Display for ErrorResponseType { Self::Basic => write!(f, "Basic"), Self::TransactionSubmit => write!(f, "TransactionSubmit"), Self::LtsTransactionSubmit => write!(f, "LtsTransactionSubmit"), + Self::TransactionPreviewV2 => write!(f, "TransactionPreviewV2"), Self::StreamTransactions => write!(f, "StreamTransactions"), Self::StreamProofs => write!(f, "StreamProofs"), } diff --git a/generated-clients/core-api-client/sync-client/src/models/event.rs b/generated-clients/core-api-client/sync-client/src/models/event.rs index 94c93f1..7af7dfa 100644 --- a/generated-clients/core-api-client/sync-client/src/models/event.rs +++ b/generated-clients/core-api-client/sync-client/src/models/event.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/event_emitter_identifier.rs b/generated-clients/core-api-client/sync-client/src/models/event_emitter_identifier.rs index f4601e9..ac48071 100644 --- a/generated-clients/core-api-client/sync-client/src/models/event_emitter_identifier.rs +++ b/generated-clients/core-api-client/sync-client/src/models/event_emitter_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/event_emitter_identifier_type.rs b/generated-clients/core-api-client/sync-client/src/models/event_emitter_identifier_type.rs index baa5d71..d53fff0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/event_emitter_identifier_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/event_emitter_identifier_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/event_type_identifier.rs b/generated-clients/core-api-client/sync-client/src/models/event_type_identifier.rs index 6c8b947..26bcad7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/event_type_identifier.rs +++ b/generated-clients/core-api-client/sync-client/src/models/event_type_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/executed_scenario.rs b/generated-clients/core-api-client/sync-client/src/models/executed_scenario.rs index ffe808f..417c19d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/executed_scenario.rs +++ b/generated-clients/core-api-client/sync-client/src/models/executed_scenario.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/executed_scenario_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/executed_scenario_transaction.rs index bc07b44..b29a5bc 100644 --- a/generated-clients/core-api-client/sync-client/src/models/executed_scenario_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/executed_scenario_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fee_destination.rs b/generated-clients/core-api-client/sync-client/src/models/fee_destination.rs index 1b6199b..0f71049 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fee_destination.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fee_destination.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fee_source.rs b/generated-clients/core-api-client/sync-client/src/models/fee_source.rs index 2d10612..9ceaab1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fee_source.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fee_source.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fee_summary.rs b/generated-clients/core-api-client/sync-client/src/models/fee_summary.rs index 9b62a63..0290bd6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fee_summary.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fee_summary.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/field_schema.rs b/generated-clients/core-api-client/sync-client/src/models/field_schema.rs index 0c4edc1..e7982e1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/field_schema.rs +++ b/generated-clients/core-api-client/sync-client/src/models/field_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition.rs b/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition.rs index a015a56..6a9cbaa 100644 --- a/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition.rs +++ b/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_if_outer_object_feature.rs b/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_if_outer_object_feature.rs index 8a9df1e..e9e803f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_if_outer_object_feature.rs +++ b/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_if_outer_object_feature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_if_own_feature.rs b/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_if_own_feature.rs index a67f7cc..8e4f1fe 100644 --- a/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_if_own_feature.rs +++ b/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_if_own_feature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_type.rs b/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_type.rs index 472a9c2..c99b56e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/field_schema_feature_condition_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/field_substate_key.rs b/generated-clients/core-api-client/sync-client/src/models/field_substate_key.rs index e4496f0..8e4c8d5 100644 --- a/generated-clients/core-api-client/sync-client/src/models/field_substate_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/field_substate_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/flash_ledger_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/flash_ledger_transaction.rs index 9ef8615..76f20f4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/flash_ledger_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/flash_ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/flash_set_substate.rs b/generated-clients/core-api-client/sync-client/src/models/flash_set_substate.rs index 8cd435c..aece4a9 100644 --- a/generated-clients/core-api-client/sync-client/src/models/flash_set_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/flash_set_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/flashed_state_updates.rs b/generated-clients/core-api-client/sync-client/src/models/flashed_state_updates.rs index 0a27677..8545a88 100644 --- a/generated-clients/core-api-client/sync-client/src/models/flashed_state_updates.rs +++ b/generated-clients/core-api-client/sync-client/src/models/flashed_state_updates.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/frozen_status.rs b/generated-clients/core-api-client/sync-client/src/models/frozen_status.rs index 0db9af5..b455d79 100644 --- a/generated-clients/core-api-client/sync-client/src/models/frozen_status.rs +++ b/generated-clients/core-api-client/sync-client/src/models/frozen_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fully_scoped_type_id.rs b/generated-clients/core-api-client/sync-client/src/models/fully_scoped_type_id.rs index d430e47..3137e3c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fully_scoped_type_id.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fully_scoped_type_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/function_auth_type.rs b/generated-clients/core-api-client/sync-client/src/models/function_auth_type.rs index a77a680..537120f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/function_auth_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/function_auth_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/function_event_emitter_identifier.rs b/generated-clients/core-api-client/sync-client/src/models/function_event_emitter_identifier.rs index 84b6d1a..5f95c9f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/function_event_emitter_identifier.rs +++ b/generated-clients/core-api-client/sync-client/src/models/function_event_emitter_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/function_schema.rs b/generated-clients/core-api-client/sync-client/src/models/function_schema.rs index 891cfc1..3ba2214 100644 --- a/generated-clients/core-api-client/sync-client/src/models/function_schema.rs +++ b/generated-clients/core-api-client/sync-client/src/models/function_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fungible_resource_amount.rs b/generated-clients/core-api-client/sync-client/src/models/fungible_resource_amount.rs index 906585c..a80ea3e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fungible_resource_amount.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fungible_resource_amount.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_divisibility_substate.rs b/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_divisibility_substate.rs index c92ecbf..3711d46 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_divisibility_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_divisibility_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_divisibility_value.rs b/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_divisibility_value.rs index 576ab40..e97b265 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_divisibility_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_divisibility_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_total_supply_substate.rs b/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_total_supply_substate.rs index 181cad2..5fc29e2 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_total_supply_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_total_supply_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_total_supply_value.rs b/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_total_supply_value.rs index 4d78f48..9ef468e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_total_supply_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fungible_resource_manager_field_total_supply_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_balance_substate.rs b/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_balance_substate.rs index 96c8682..2572ad8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_balance_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_balance_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_balance_value.rs b/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_balance_value.rs index e7d82a1..daaa3ad 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_balance_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_balance_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_frozen_status_substate.rs b/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_frozen_status_substate.rs index 3bd23d3..df3ab65 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_frozen_status_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_frozen_status_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_frozen_status_value.rs b/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_frozen_status_value.rs index 56ce5ae..2ce63f6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_frozen_status_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/fungible_vault_field_frozen_status_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/generic_blueprint_payload_def.rs b/generated-clients/core-api-client/sync-client/src/models/generic_blueprint_payload_def.rs index 54f7fa4..76023ff 100644 --- a/generated-clients/core-api-client/sync-client/src/models/generic_blueprint_payload_def.rs +++ b/generated-clients/core-api-client/sync-client/src/models/generic_blueprint_payload_def.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/generic_key.rs b/generated-clients/core-api-client/sync-client/src/models/generic_key.rs index a9509ba..a2fd877 100644 --- a/generated-clients/core-api-client/sync-client/src/models/generic_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/generic_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/generic_key_value_store_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/generic_key_value_store_entry_substate.rs index 3572ce1..58cddb6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/generic_key_value_store_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/generic_key_value_store_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/generic_key_value_store_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/generic_key_value_store_entry_value.rs index 816bf7e..4103de1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/generic_key_value_store_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/generic_key_value_store_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/generic_scrypto_component_field_state_substate.rs b/generated-clients/core-api-client/sync-client/src/models/generic_scrypto_component_field_state_substate.rs index 0ed46aa..6ef3b0f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/generic_scrypto_component_field_state_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/generic_scrypto_component_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/generic_scrypto_component_field_state_value.rs b/generated-clients/core-api-client/sync-client/src/models/generic_scrypto_component_field_state_value.rs index 4349aef..58fd287 100644 --- a/generated-clients/core-api-client/sync-client/src/models/generic_scrypto_component_field_state_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/generic_scrypto_component_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/generic_substitution.rs b/generated-clients/core-api-client/sync-client/src/models/generic_substitution.rs index 0ee1095..1bb1176 100644 --- a/generated-clients/core-api-client/sync-client/src/models/generic_substitution.rs +++ b/generated-clients/core-api-client/sync-client/src/models/generic_substitution.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/generic_substitution_type.rs b/generated-clients/core-api-client/sync-client/src/models/generic_substitution_type.rs index 69f1ae5..7e4b08e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/generic_substitution_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/generic_substitution_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/generic_type_parameter.rs b/generated-clients/core-api-client/sync-client/src/models/generic_type_parameter.rs index 7af9bd3..248a2d1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/generic_type_parameter.rs +++ b/generated-clients/core-api-client/sync-client/src/models/generic_type_parameter.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/generic_type_parameter_constraints.rs b/generated-clients/core-api-client/sync-client/src/models/generic_type_parameter_constraints.rs index 2fb33b9..a93e3e3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/generic_type_parameter_constraints.rs +++ b/generated-clients/core-api-client/sync-client/src/models/generic_type_parameter_constraints.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/genesis_ledger_proof_origin.rs b/generated-clients/core-api-client/sync-client/src/models/genesis_ledger_proof_origin.rs index 6482120..96f62a4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/genesis_ledger_proof_origin.rs +++ b/generated-clients/core-api-client/sync-client/src/models/genesis_ledger_proof_origin.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/genesis_ledger_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/genesis_ledger_transaction.rs index be078da..b07c689 100644 --- a/generated-clients/core-api-client/sync-client/src/models/genesis_ledger_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/genesis_ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/hook_export.rs b/generated-clients/core-api-client/sync-client/src/models/hook_export.rs index 9ad12b2..50588a8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/hook_export.rs +++ b/generated-clients/core-api-client/sync-client/src/models/hook_export.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/in_progress_protocol_update_status.rs b/generated-clients/core-api-client/sync-client/src/models/in_progress_protocol_update_status.rs index 1923ff9..200dedf 100644 --- a/generated-clients/core-api-client/sync-client/src/models/in_progress_protocol_update_status.rs +++ b/generated-clients/core-api-client/sync-client/src/models/in_progress_protocol_update_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/index_blueprint_collection_schema.rs b/generated-clients/core-api-client/sync-client/src/models/index_blueprint_collection_schema.rs index dfc1829..f2bae3e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/index_blueprint_collection_schema.rs +++ b/generated-clients/core-api-client/sync-client/src/models/index_blueprint_collection_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/indexed_state_schema.rs b/generated-clients/core-api-client/sync-client/src/models/indexed_state_schema.rs index e5c23b2..3fe90ee 100644 --- a/generated-clients/core-api-client/sync-client/src/models/indexed_state_schema.rs +++ b/generated-clients/core-api-client/sync-client/src/models/indexed_state_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/instance_schema_blueprint_type_reference.rs b/generated-clients/core-api-client/sync-client/src/models/instance_schema_blueprint_type_reference.rs index cad0c6b..9c8d820 100644 --- a/generated-clients/core-api-client/sync-client/src/models/instance_schema_blueprint_type_reference.rs +++ b/generated-clients/core-api-client/sync-client/src/models/instance_schema_blueprint_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/instant_ms.rs b/generated-clients/core-api-client/sync-client/src/models/instant_ms.rs index 5649adb..299fe12 100644 --- a/generated-clients/core-api-client/sync-client/src/models/instant_ms.rs +++ b/generated-clients/core-api-client/sync-client/src/models/instant_ms.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/instruction_resource_changes.rs b/generated-clients/core-api-client/sync-client/src/models/instruction_resource_changes.rs index 287505e..8a9818e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/instruction_resource_changes.rs +++ b/generated-clients/core-api-client/sync-client/src/models/instruction_resource_changes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/intent_core_v2.rs b/generated-clients/core-api-client/sync-client/src/models/intent_core_v2.rs index e8d7020..30e09f5 100644 --- a/generated-clients/core-api-client/sync-client/src/models/intent_core_v2.rs +++ b/generated-clients/core-api-client/sync-client/src/models/intent_core_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/intent_header_v2.rs b/generated-clients/core-api-client/sync-client/src/models/intent_header_v2.rs index e3d6873..9cbbf50 100644 --- a/generated-clients/core-api-client/sync-client/src/models/intent_header_v2.rs +++ b/generated-clients/core-api-client/sync-client/src/models/intent_header_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/intent_signatures.rs b/generated-clients/core-api-client/sync-client/src/models/intent_signatures.rs index 49b8499..75f706f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/intent_signatures.rs +++ b/generated-clients/core-api-client/sync-client/src/models/intent_signatures.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/invalid_transaction_preview_v2_error_details.rs b/generated-clients/core-api-client/sync-client/src/models/invalid_transaction_preview_v2_error_details.rs new file mode 100644 index 0000000..fb14a34 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/invalid_transaction_preview_v2_error_details.rs @@ -0,0 +1,27 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct InvalidTransactionPreviewV2ErrorDetails { + #[serde(rename = "validation_error")] + pub validation_error: String, +} + +impl InvalidTransactionPreviewV2ErrorDetails { + pub fn new(validation_error: String) -> InvalidTransactionPreviewV2ErrorDetails { + InvalidTransactionPreviewV2ErrorDetails { + validation_error, + } + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/key_value_based_structure.rs b/generated-clients/core-api-client/sync-client/src/models/key_value_based_structure.rs index 80e0644..c099f93 100644 --- a/generated-clients/core-api-client/sync-client/src/models/key_value_based_structure.rs +++ b/generated-clients/core-api-client/sync-client/src/models/key_value_based_structure.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/key_value_blueprint_collection_schema.rs b/generated-clients/core-api-client/sync-client/src/models/key_value_blueprint_collection_schema.rs index 523d1e2..f991765 100644 --- a/generated-clients/core-api-client/sync-client/src/models/key_value_blueprint_collection_schema.rs +++ b/generated-clients/core-api-client/sync-client/src/models/key_value_blueprint_collection_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/key_value_store_entry_structure.rs b/generated-clients/core-api-client/sync-client/src/models/key_value_store_entry_structure.rs index 9a9851a..9d694a7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/key_value_store_entry_structure.rs +++ b/generated-clients/core-api-client/sync-client/src/models/key_value_store_entry_structure.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/key_value_store_info.rs b/generated-clients/core-api-client/sync-client/src/models/key_value_store_info.rs index 0d10fff..a1a1184 100644 --- a/generated-clients/core-api-client/sync-client/src/models/key_value_store_info.rs +++ b/generated-clients/core-api-client/sync-client/src/models/key_value_store_info.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/key_value_store_type_info_details.rs b/generated-clients/core-api-client/sync-client/src/models/key_value_store_type_info_details.rs index acb72f2..0294134 100644 --- a/generated-clients/core-api-client/sync-client/src/models/key_value_store_type_info_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/key_value_store_type_info_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/leader_proposal_history.rs b/generated-clients/core-api-client/sync-client/src/models/leader_proposal_history.rs index 58986ec..58964b5 100644 --- a/generated-clients/core-api-client/sync-client/src/models/leader_proposal_history.rs +++ b/generated-clients/core-api-client/sync-client/src/models/leader_proposal_history.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ledger_hashes.rs b/generated-clients/core-api-client/sync-client/src/models/ledger_hashes.rs index c9f4292..e8e4f84 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ledger_hashes.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ledger_hashes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ledger_header.rs b/generated-clients/core-api-client/sync-client/src/models/ledger_header.rs index 98a12d9..5fc68dc 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ledger_header.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ledger_header.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ledger_header_summary.rs b/generated-clients/core-api-client/sync-client/src/models/ledger_header_summary.rs index 0c54901..239a33f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ledger_header_summary.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ledger_header_summary.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ledger_proof.rs b/generated-clients/core-api-client/sync-client/src/models/ledger_proof.rs index 370c3d2..e7315c0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ledger_proof.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ledger_proof.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ledger_proof_origin.rs b/generated-clients/core-api-client/sync-client/src/models/ledger_proof_origin.rs index 1632619..43d217c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ledger_proof_origin.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ledger_proof_origin.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ledger_proof_origin_type.rs b/generated-clients/core-api-client/sync-client/src/models/ledger_proof_origin_type.rs index 20ef4dd..3907d62 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ledger_proof_origin_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ledger_proof_origin_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ledger_state_selector.rs b/generated-clients/core-api-client/sync-client/src/models/ledger_state_selector.rs index 2906f86..09d436f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ledger_state_selector.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ledger_state_selector.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ledger_state_selector_type.rs b/generated-clients/core-api-client/sync-client/src/models/ledger_state_selector_type.rs index 86e52d5..5b8dbf5 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ledger_state_selector_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ledger_state_selector_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ledger_state_summary.rs b/generated-clients/core-api-client/sync-client/src/models/ledger_state_summary.rs index 76e5a00..5250a45 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ledger_state_summary.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ledger_state_summary.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ledger_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/ledger_transaction.rs index de5d4ab..ae9e7d0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ledger_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/ledger_transaction_type.rs b/generated-clients/core-api-client/sync-client/src/models/ledger_transaction_type.rs index a80cd57..0433b8a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/ledger_transaction_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/ledger_transaction_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/limit_parameters.rs b/generated-clients/core-api-client/sync-client/src/models/limit_parameters.rs index 1e30219..ad5e528 100644 --- a/generated-clients/core-api-client/sync-client/src/models/limit_parameters.rs +++ b/generated-clients/core-api-client/sync-client/src/models/limit_parameters.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/local_generic_substitution.rs b/generated-clients/core-api-client/sync-client/src/models/local_generic_substitution.rs index fa35e17..fc1e03b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/local_generic_substitution.rs +++ b/generated-clients/core-api-client/sync-client/src/models/local_generic_substitution.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/local_non_fungible_key.rs b/generated-clients/core-api-client/sync-client/src/models/local_non_fungible_key.rs index ea4535e..e078775 100644 --- a/generated-clients/core-api-client/sync-client/src/models/local_non_fungible_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/local_non_fungible_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/local_type_id.rs b/generated-clients/core-api-client/sync-client/src/models/local_type_id.rs index 9ab3ce1..6f8dc1a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/local_type_id.rs +++ b/generated-clients/core-api-client/sync-client/src/models/local_type_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_committed_transaction_outcome.rs b/generated-clients/core-api-client/sync-client/src/models/lts_committed_transaction_outcome.rs index 795ec53..e052577 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_committed_transaction_outcome.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_committed_transaction_outcome.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_committed_transaction_status.rs b/generated-clients/core-api-client/sync-client/src/models/lts_committed_transaction_status.rs index f8fde21..56d8e76 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_committed_transaction_status.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_committed_transaction_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_entity_fungible_balance_changes.rs b/generated-clients/core-api-client/sync-client/src/models/lts_entity_fungible_balance_changes.rs index 2081fa7..e5e5e92 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_entity_fungible_balance_changes.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_entity_fungible_balance_changes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_entity_non_fungible_balance_changes.rs b/generated-clients/core-api-client/sync-client/src/models/lts_entity_non_fungible_balance_changes.rs index 97911f8..c204a37 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_entity_non_fungible_balance_changes.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_entity_non_fungible_balance_changes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_fee_fungible_resource_balance_change.rs b/generated-clients/core-api-client/sync-client/src/models/lts_fee_fungible_resource_balance_change.rs index 595f05d..15ed6ef 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_fee_fungible_resource_balance_change.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_fee_fungible_resource_balance_change.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_fee_fungible_resource_balance_change_type.rs b/generated-clients/core-api-client/sync-client/src/models/lts_fee_fungible_resource_balance_change_type.rs index a66db06..266c849 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_fee_fungible_resource_balance_change_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_fee_fungible_resource_balance_change_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_fungible_resource_balance.rs b/generated-clients/core-api-client/sync-client/src/models/lts_fungible_resource_balance.rs index 93c32ca..c185809 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_fungible_resource_balance.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_fungible_resource_balance.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_fungible_resource_balance_change.rs b/generated-clients/core-api-client/sync-client/src/models/lts_fungible_resource_balance_change.rs index 999a44f..89f10c6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_fungible_resource_balance_change.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_fungible_resource_balance_change.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_resultant_account_fungible_balances.rs b/generated-clients/core-api-client/sync-client/src/models/lts_resultant_account_fungible_balances.rs index 23bbc0c..2fadd1f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_resultant_account_fungible_balances.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_resultant_account_fungible_balances.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_resultant_fungible_balance.rs b/generated-clients/core-api-client/sync-client/src/models/lts_resultant_fungible_balance.rs index f18621a..fa3203f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_resultant_fungible_balance.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_resultant_fungible_balance.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_all_fungible_resource_balances_request.rs b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_all_fungible_resource_balances_request.rs index bdc8518..745b4d6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_all_fungible_resource_balances_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_all_fungible_resource_balances_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_all_fungible_resource_balances_response.rs b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_all_fungible_resource_balances_response.rs index 240fa2e..6b48eec 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_all_fungible_resource_balances_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_all_fungible_resource_balances_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_deposit_behaviour_request.rs b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_deposit_behaviour_request.rs index e603a7c..ba60db7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_deposit_behaviour_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_deposit_behaviour_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_deposit_behaviour_response.rs b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_deposit_behaviour_response.rs index d980fa3..4fe49c4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_deposit_behaviour_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_deposit_behaviour_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_fungible_resource_balance_request.rs b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_fungible_resource_balance_request.rs index 82512a2..5640730 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_fungible_resource_balance_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_fungible_resource_balance_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_fungible_resource_balance_response.rs b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_fungible_resource_balance_response.rs index 6dc53c3..5a92c8c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_state_account_fungible_resource_balance_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_state_account_fungible_resource_balance_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_stream_account_transaction_outcomes_request.rs b/generated-clients/core-api-client/sync-client/src/models/lts_stream_account_transaction_outcomes_request.rs index 5f4a0ab..02379f3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_stream_account_transaction_outcomes_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_stream_account_transaction_outcomes_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_stream_account_transaction_outcomes_response.rs b/generated-clients/core-api-client/sync-client/src/models/lts_stream_account_transaction_outcomes_response.rs index ac7a713..98017fc 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_stream_account_transaction_outcomes_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_stream_account_transaction_outcomes_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_stream_transaction_outcomes_request.rs b/generated-clients/core-api-client/sync-client/src/models/lts_stream_transaction_outcomes_request.rs index 16f8da8..0e24ec0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_stream_transaction_outcomes_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_stream_transaction_outcomes_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_stream_transaction_outcomes_response.rs b/generated-clients/core-api-client/sync-client/src/models/lts_stream_transaction_outcomes_response.rs index 384527a..eeac9d0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_stream_transaction_outcomes_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_stream_transaction_outcomes_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_construction_request.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_construction_request.rs index f482e5d..36cb7db 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_construction_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_construction_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_construction_response.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_construction_response.rs index 9bb96bf..59c6ca5 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_construction_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_construction_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_intent_status.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_intent_status.rs index fcab6b5..7dceab9 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_intent_status.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_intent_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_payload_details.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_payload_details.rs index ca520d7..e3ea533 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_payload_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_payload_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_payload_status.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_payload_status.rs index af6a202..c34dc12 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_payload_status.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_payload_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_status_request.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_status_request.rs index ecf94bf..a81c5a1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_status_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_status_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_status_response.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_status_response.rs index e38adbc..a252d9b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_status_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_status_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_details.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_details.rs index bfc1c76..55dc3a9 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_details_type.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_details_type.rs index 94a554e..1aab9ba 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_details_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_details_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_response.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_response.rs index 3eaccda..b3a2060 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_intent_already_committed.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_intent_already_committed.rs index 393eb99..8c1ee2a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_intent_already_committed.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_intent_already_committed.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs index 31794ed..3b55916 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -13,19 +13,27 @@ use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] pub struct LtsTransactionSubmitPriorityThresholdNotMetErrorDetails { - /// A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. + /// NOTE: This is kept for backwards compatibility, but we recommend using `min_tip_proportion_required` instead. A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. #[serde(rename = "min_tip_percentage_required", skip_serializing_if = "Option::is_none")] pub min_tip_percentage_required: Option, - /// Tip percentage of the submitted (and rejected) transaction. + /// A lower bound for tip proportion at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. + #[serde(rename = "min_tip_proportion_required", skip_serializing_if = "Option::is_none")] + pub min_tip_proportion_required: Option, + /// NOTE: This is kept for backwards compatibility, but we recommend using `tip_proportion` instead. Tip percentage of the submitted (and rejected) transaction. For V2 transactions specifying basis point tips, the amount is rounded down. #[serde(rename = "tip_percentage")] pub tip_percentage: u32, + /// The string-encoded decimal tip proportion of the submitted (and rejected) transaction. This field will always be present on Cuttlefish nodes, but is marked as not-required for Cuttlefish launch, to avoid a dependency on clients to update after the node is updated. + #[serde(rename = "tip_proportion", skip_serializing_if = "Option::is_none")] + pub tip_proportion: Option, } impl LtsTransactionSubmitPriorityThresholdNotMetErrorDetails { pub fn new(tip_percentage: u32) -> LtsTransactionSubmitPriorityThresholdNotMetErrorDetails { LtsTransactionSubmitPriorityThresholdNotMetErrorDetails { min_tip_percentage_required: None, + min_tip_proportion_required: None, tip_percentage, + tip_proportion: None, } } } diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_rejected_error_details.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_rejected_error_details.rs index 8ff6a5d..6ac067d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_rejected_error_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_rejected_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_request.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_request.rs index 7cc864e..2951b8d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_response.rs b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_response.rs index 80bead5..82fa6f0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/lts_transaction_submit_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/main_method_key.rs b/generated-clients/core-api-client/sync-client/src/models/main_method_key.rs index 7f1959f..0b0b591 100644 --- a/generated-clients/core-api-client/sync-client/src/models/main_method_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/main_method_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/manifest_validation_ruleset.rs b/generated-clients/core-api-client/sync-client/src/models/manifest_validation_ruleset.rs new file mode 100644 index 0000000..96308e9 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/manifest_validation_ruleset.rs @@ -0,0 +1,38 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +/// +#[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] +pub enum ManifestValidationRuleset { + #[serde(rename = "Basic")] + Basic, + #[serde(rename = "Cuttlefish")] + Cuttlefish, + +} + +impl std::fmt::Display for ManifestValidationRuleset { + fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { + match self { + Self::Basic => write!(f, "Basic"), + Self::Cuttlefish => write!(f, "Cuttlefish"), + } + } +} + +impl Default for ManifestValidationRuleset { + fn default() -> ManifestValidationRuleset { + Self::Basic + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/map_substate_key.rs b/generated-clients/core-api-client/sync-client/src/models/map_substate_key.rs index 8ac2aa2..0473451 100644 --- a/generated-clients/core-api-client/sync-client/src/models/map_substate_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/map_substate_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/mempool_list_request.rs b/generated-clients/core-api-client/sync-client/src/models/mempool_list_request.rs index b6c81cb..4ffe6ca 100644 --- a/generated-clients/core-api-client/sync-client/src/models/mempool_list_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/mempool_list_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/mempool_list_response.rs b/generated-clients/core-api-client/sync-client/src/models/mempool_list_response.rs index 49f5d50..3102386 100644 --- a/generated-clients/core-api-client/sync-client/src/models/mempool_list_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/mempool_list_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_hashes.rs b/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_hashes.rs index 2b22f3d..8110875 100644 --- a/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_hashes.rs +++ b/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_hashes.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_request.rs b/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_request.rs index ea8e487..1d80e34 100644 --- a/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_response.rs b/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_response.rs index b9833fe..99c24ac 100644 --- a/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_response_payloads_inner.rs b/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_response_payloads_inner.rs index 328ae9b..c7caf1b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_response_payloads_inner.rs +++ b/generated-clients/core-api-client/sync-client/src/models/mempool_transaction_response_payloads_inner.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/message_validation_config.rs b/generated-clients/core-api-client/sync-client/src/models/message_validation_config.rs new file mode 100644 index 0000000..b1852f7 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/message_validation_config.rs @@ -0,0 +1,36 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct MessageValidationConfig { + #[serde(rename = "max_decryptors")] + pub max_decryptors: String, + #[serde(rename = "max_encrypted_message_length")] + pub max_encrypted_message_length: String, + #[serde(rename = "max_mime_type_length")] + pub max_mime_type_length: String, + #[serde(rename = "max_plaintext_message_length")] + pub max_plaintext_message_length: String, +} + +impl MessageValidationConfig { + pub fn new(max_decryptors: String, max_encrypted_message_length: String, max_mime_type_length: String, max_plaintext_message_length: String) -> MessageValidationConfig { + MessageValidationConfig { + max_decryptors, + max_encrypted_message_length, + max_mime_type_length, + max_plaintext_message_length, + } + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/metadata_key.rs b/generated-clients/core-api-client/sync-client/src/models/metadata_key.rs index a3b98eb..9d4f7e9 100644 --- a/generated-clients/core-api-client/sync-client/src/models/metadata_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/metadata_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/metadata_module_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/metadata_module_entry_substate.rs index 2f5e51f..45d29a6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/metadata_module_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/metadata_module_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/metadata_module_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/metadata_module_entry_value.rs index 0c53333..fc85f3b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/metadata_module_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/metadata_module_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/method_accessibility.rs b/generated-clients/core-api-client/sync-client/src/models/method_accessibility.rs index bb02a10..b3fc0da 100644 --- a/generated-clients/core-api-client/sync-client/src/models/method_accessibility.rs +++ b/generated-clients/core-api-client/sync-client/src/models/method_accessibility.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/method_accessibility_type.rs b/generated-clients/core-api-client/sync-client/src/models/method_accessibility_type.rs index e74aac7..7f4b793 100644 --- a/generated-clients/core-api-client/sync-client/src/models/method_accessibility_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/method_accessibility_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/method_auth_type.rs b/generated-clients/core-api-client/sync-client/src/models/method_auth_type.rs index ba1e953..388414b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/method_auth_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/method_auth_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/method_event_emitter_identifier.rs b/generated-clients/core-api-client/sync-client/src/models/method_event_emitter_identifier.rs index b2979a8..df5c603 100644 --- a/generated-clients/core-api-client/sync-client/src/models/method_event_emitter_identifier.rs +++ b/generated-clients/core-api-client/sync-client/src/models/method_event_emitter_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/mod.rs b/generated-clients/core-api-client/sync-client/src/models/mod.rs index 6ae55d6..d0dfbbf 100644 --- a/generated-clients/core-api-client/sync-client/src/models/mod.rs +++ b/generated-clients/core-api-client/sync-client/src/models/mod.rs @@ -4,10 +4,6 @@ pub mod access_controller_field_state_value; pub use self::access_controller_field_state_value::AccessControllerFieldStateValue; pub mod access_rule; pub use self::access_rule::AccessRule; -pub mod access_rule_node; -pub use self::access_rule_node::AccessRuleNode; -pub mod access_rule_node_type; -pub use self::access_rule_node_type::AccessRuleNodeType; pub mod access_rule_type; pub use self::access_rule_type::AccessRuleType; pub mod account_address_key; @@ -40,18 +36,18 @@ pub mod active_validator_key; pub use self::active_validator_key::ActiveValidatorKey; pub mod address_type; pub use self::address_type::AddressType; -pub mod all_of_access_rule_node; -pub use self::all_of_access_rule_node::AllOfAccessRuleNode; -pub mod all_of_proof_rule; -pub use self::all_of_proof_rule::AllOfProofRule; +pub mod all_of_basic_requirement; +pub use self::all_of_basic_requirement::AllOfBasicRequirement; +pub mod all_of_composite_requirement; +pub use self::all_of_composite_requirement::AllOfCompositeRequirement; pub mod always_visible_global_nodes_version; pub use self::always_visible_global_nodes_version::AlwaysVisibleGlobalNodesVersion; -pub mod amount_of_proof_rule; -pub use self::amount_of_proof_rule::AmountOfProofRule; -pub mod any_of_access_rule_node; -pub use self::any_of_access_rule_node::AnyOfAccessRuleNode; -pub mod any_of_proof_rule; -pub use self::any_of_proof_rule::AnyOfProofRule; +pub mod amount_of_basic_requirement; +pub use self::amount_of_basic_requirement::AmountOfBasicRequirement; +pub mod any_of_basic_requirement; +pub use self::any_of_basic_requirement::AnyOfBasicRequirement; +pub mod any_of_composite_requirement; +pub use self::any_of_composite_requirement::AnyOfCompositeRequirement; pub mod attached_module_id; pub use self::attached_module_id::AttachedModuleId; pub mod auth_config; @@ -64,6 +60,10 @@ pub mod authorized_depositor_key; pub use self::authorized_depositor_key::AuthorizedDepositorKey; pub mod basic_error_response; pub use self::basic_error_response::BasicErrorResponse; +pub mod basic_requirement; +pub use self::basic_requirement::BasicRequirement; +pub mod basic_requirement_type; +pub use self::basic_requirement_type::BasicRequirementType; pub mod binary_plaintext_message_content; pub use self::binary_plaintext_message_content::BinaryPlaintextMessageContent; pub mod blueprint_collection_schema; @@ -124,8 +124,14 @@ pub mod committed_transaction; pub use self::committed_transaction::CommittedTransaction; pub mod committed_transaction_balance_changes; pub use self::committed_transaction_balance_changes::CommittedTransactionBalanceChanges; +pub mod compiled_preview_transaction; +pub use self::compiled_preview_transaction::CompiledPreviewTransaction; pub mod component_method_target_identifier; pub use self::component_method_target_identifier::ComponentMethodTargetIdentifier; +pub mod composite_requirement; +pub use self::composite_requirement::CompositeRequirement; +pub mod composite_requirement_type; +pub use self::composite_requirement_type::CompositeRequirementType; pub mod consensus_ledger_proof_origin; pub use self::consensus_ledger_proof_origin::ConsensusLedgerProofOrigin; pub mod consensus_manager_field_config_substate; @@ -164,8 +170,8 @@ pub mod costing_module_config; pub use self::costing_module_config::CostingModuleConfig; pub mod costing_parameters; pub use self::costing_parameters::CostingParameters; -pub mod count_of_proof_rule; -pub use self::count_of_proof_rule::CountOfProofRule; +pub mod count_of_basic_requirement; +pub use self::count_of_basic_requirement::CountOfBasicRequirement; pub mod created_substate; pub use self::created_substate::CreatedSubstate; pub mod data_struct; @@ -316,6 +322,8 @@ pub mod intent_header_v2; pub use self::intent_header_v2::IntentHeaderV2; pub mod intent_signatures; pub use self::intent_signatures::IntentSignatures; +pub mod invalid_transaction_preview_v2_error_details; +pub use self::invalid_transaction_preview_v2_error_details::InvalidTransactionPreviewV2ErrorDetails; pub mod key_value_based_structure; pub use self::key_value_based_structure::KeyValueBasedStructure; pub mod key_value_blueprint_collection_schema; @@ -430,6 +438,8 @@ pub mod lts_transaction_submit_response; pub use self::lts_transaction_submit_response::LtsTransactionSubmitResponse; pub mod main_method_key; pub use self::main_method_key::MainMethodKey; +pub mod manifest_validation_ruleset; +pub use self::manifest_validation_ruleset::ManifestValidationRuleset; pub mod map_substate_key; pub use self::map_substate_key::MapSubstateKey; pub mod mempool_list_request; @@ -444,6 +454,8 @@ pub mod mempool_transaction_response; pub use self::mempool_transaction_response::MempoolTransactionResponse; pub mod mempool_transaction_response_payloads_inner; pub use self::mempool_transaction_response_payloads_inner::MempoolTransactionResponsePayloadsInner; +pub mod message_validation_config; +pub use self::message_validation_config::MessageValidationConfig; pub mod metadata_key; pub use self::metadata_key::MetadataKey; pub mod metadata_module_entry_substate; @@ -634,18 +646,22 @@ pub mod plaintext_transaction_message; pub use self::plaintext_transaction_message::PlaintextTransactionMessage; pub mod pool_vault; pub use self::pool_vault::PoolVault; +pub mod preparation_settings; +pub use self::preparation_settings::PreparationSettings; pub mod presented_badge; pub use self::presented_badge::PresentedBadge; pub mod presented_badge_type; pub use self::presented_badge_type::PresentedBadgeType; +pub mod preview_flags; +pub use self::preview_flags::PreviewFlags; +pub mod preview_transaction; +pub use self::preview_transaction::PreviewTransaction; +pub mod preview_transaction_type; +pub use self::preview_transaction_type::PreviewTransactionType; pub mod primary_role_recovery_attempt; pub use self::primary_role_recovery_attempt::PrimaryRoleRecoveryAttempt; -pub mod proof_access_rule_node; -pub use self::proof_access_rule_node::ProofAccessRuleNode; -pub mod proof_rule; -pub use self::proof_rule::ProofRule; -pub mod proof_rule_type; -pub use self::proof_rule_type::ProofRuleType; +pub mod proof_rule_composite_requirement; +pub use self::proof_rule_composite_requirement::ProofRuleCompositeRequirement; pub mod proposer_reward; pub use self::proposer_reward::ProposerReward; pub mod protected_access_rule; @@ -678,8 +694,8 @@ pub mod remote_generic_substitution; pub use self::remote_generic_substitution::RemoteGenericSubstitution; pub mod requested_state_version_out_of_bounds_error_details; pub use self::requested_state_version_out_of_bounds_error_details::RequestedStateVersionOutOfBoundsErrorDetails; -pub mod require_proof_rule; -pub use self::require_proof_rule::RequireProofRule; +pub mod require_basic_requirement; +pub use self::require_basic_requirement::RequireBasicRequirement; pub mod requirement; pub use self::requirement::Requirement; pub mod requirement_type; @@ -922,14 +938,24 @@ pub mod transaction_payload_status; pub use self::transaction_payload_status::TransactionPayloadStatus; pub mod transaction_preview_request; pub use self::transaction_preview_request::TransactionPreviewRequest; -pub mod transaction_preview_request_flags; -pub use self::transaction_preview_request_flags::TransactionPreviewRequestFlags; pub mod transaction_preview_response; pub use self::transaction_preview_response::TransactionPreviewResponse; pub mod transaction_preview_response_logs_inner; pub use self::transaction_preview_response_logs_inner::TransactionPreviewResponseLogsInner; pub mod transaction_preview_response_options; pub use self::transaction_preview_response_options::TransactionPreviewResponseOptions; +pub mod transaction_preview_v2_error_details; +pub use self::transaction_preview_v2_error_details::TransactionPreviewV2ErrorDetails; +pub mod transaction_preview_v2_error_details_type; +pub use self::transaction_preview_v2_error_details_type::TransactionPreviewV2ErrorDetailsType; +pub mod transaction_preview_v2_error_response; +pub use self::transaction_preview_v2_error_response::TransactionPreviewV2ErrorResponse; +pub mod transaction_preview_v2_request; +pub use self::transaction_preview_v2_request::TransactionPreviewV2Request; +pub mod transaction_preview_v2_response; +pub use self::transaction_preview_v2_response::TransactionPreviewV2Response; +pub mod transaction_preview_v2_response_options; +pub use self::transaction_preview_v2_response_options::TransactionPreviewV2ResponseOptions; pub mod transaction_receipt; pub use self::transaction_receipt::TransactionReceipt; pub mod transaction_receipt_request; @@ -968,6 +994,8 @@ pub mod transaction_tracker_field_state_value; pub use self::transaction_tracker_field_state_value::TransactionTrackerFieldStateValue; pub mod transaction_tracker_transaction_status; pub use self::transaction_tracker_transaction_status::TransactionTrackerTransactionStatus; +pub mod transaction_validation_config; +pub use self::transaction_validation_config::TransactionValidationConfig; pub mod two_resource_pool_field_state_substate; pub use self::two_resource_pool_field_state_substate::TwoResourcePoolFieldStateSubstate; pub mod two_resource_pool_field_state_value; diff --git a/generated-clients/core-api-client/sync-client/src/models/module_id.rs b/generated-clients/core-api-client/sync-client/src/models/module_id.rs index 1af4a29..fb29526 100644 --- a/generated-clients/core-api-client/sync-client/src/models/module_id.rs +++ b/generated-clients/core-api-client/sync-client/src/models/module_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/module_version.rs b/generated-clients/core-api-client/sync-client/src/models/module_version.rs index 04bc27b..f8a134e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/module_version.rs +++ b/generated-clients/core-api-client/sync-client/src/models/module_version.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/multi_resource_pool_field_state_substate.rs b/generated-clients/core-api-client/sync-client/src/models/multi_resource_pool_field_state_substate.rs index 601fe96..135c625 100644 --- a/generated-clients/core-api-client/sync-client/src/models/multi_resource_pool_field_state_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/multi_resource_pool_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/multi_resource_pool_field_state_value.rs b/generated-clients/core-api-client/sync-client/src/models/multi_resource_pool_field_state_value.rs index 3ec9f84..9cc1a19 100644 --- a/generated-clients/core-api-client/sync-client/src/models/multi_resource_pool_field_state_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/multi_resource_pool_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/mutable_field.rs b/generated-clients/core-api-client/sync-client/src/models/mutable_field.rs index 4b07389..a8d4334 100644 --- a/generated-clients/core-api-client/sync-client/src/models/mutable_field.rs +++ b/generated-clients/core-api-client/sync-client/src/models/mutable_field.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/network_configuration_response.rs b/generated-clients/core-api-client/sync-client/src/models/network_configuration_response.rs index a38c7f6..fa2ecd8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/network_configuration_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/network_configuration_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/network_configuration_response_version.rs b/generated-clients/core-api-client/sync-client/src/models/network_configuration_response_version.rs index b2d8bd4..6f00373 100644 --- a/generated-clients/core-api-client/sync-client/src/models/network_configuration_response_version.rs +++ b/generated-clients/core-api-client/sync-client/src/models/network_configuration_response_version.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/network_configuration_response_well_known_addresses.rs b/generated-clients/core-api-client/sync-client/src/models/network_configuration_response_well_known_addresses.rs index f1e4367..cc32864 100644 --- a/generated-clients/core-api-client/sync-client/src/models/network_configuration_response_well_known_addresses.rs +++ b/generated-clients/core-api-client/sync-client/src/models/network_configuration_response_well_known_addresses.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,7 +11,7 @@ use crate::models; use serde::{Deserialize, Serialize}; -/// NetworkConfigurationResponseWellKnownAddresses : Key addresses for this network. +/// NetworkConfigurationResponseWellKnownAddresses : Key addresses for this network, as per https://docs.radixdlt.com/docs/well-known-addresses. Note that at Cuttlefish, some of these names have been updated elsewhere in the stack, but for backwards compatibility, we must use the old names here. Notably: - `secp256k1_signature_virtual_badge` is now `secp256k1_signature_resource` elsewhere - `ed25519_signature_virtual_badge` is now `ed25519_signature_resource` elsewhere - `package_of_direct_caller_virtual_badge` is now `package_of_direct_caller_resource` elsewhere - `global_caller_virtual_badge` is now `global_caller_resource` elsewhere - `system_transaction_badge` is now `system_transaction_resource` elsewhere #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] pub struct NetworkConfigurationResponseWellKnownAddresses { #[serde(rename = "access_controller_package")] @@ -62,10 +62,14 @@ pub struct NetworkConfigurationResponseWellKnownAddresses { pub secp256k1_signature_virtual_badge: String, #[serde(rename = "system_transaction_badge")] pub system_transaction_badge: String, + #[serde(rename = "test_utils_package", skip_serializing_if = "Option::is_none")] + pub test_utils_package: Option, #[serde(rename = "transaction_processor_package")] pub transaction_processor_package: String, #[serde(rename = "transaction_tracker")] pub transaction_tracker: String, + #[serde(rename = "transaction_tracker_package", skip_serializing_if = "Option::is_none")] + pub transaction_tracker_package: Option, #[serde(rename = "validator_owner_badge")] pub validator_owner_badge: String, #[serde(rename = "xrd")] @@ -73,7 +77,7 @@ pub struct NetworkConfigurationResponseWellKnownAddresses { } impl NetworkConfigurationResponseWellKnownAddresses { - /// Key addresses for this network. + /// Key addresses for this network, as per https://docs.radixdlt.com/docs/well-known-addresses. Note that at Cuttlefish, some of these names have been updated elsewhere in the stack, but for backwards compatibility, we must use the old names here. Notably: - `secp256k1_signature_virtual_badge` is now `secp256k1_signature_resource` elsewhere - `ed25519_signature_virtual_badge` is now `ed25519_signature_resource` elsewhere - `package_of_direct_caller_virtual_badge` is now `package_of_direct_caller_resource` elsewhere - `global_caller_virtual_badge` is now `global_caller_resource` elsewhere - `system_transaction_badge` is now `system_transaction_resource` elsewhere pub fn new(access_controller_package: String, account_owner_badge: String, account_package: String, consensus_manager: String, consensus_manager_package: String, ed25519_signature_virtual_badge: String, faucet: String, faucet_package: String, genesis_helper: String, genesis_helper_package: String, global_caller_virtual_badge: String, identity_owner_badge: String, identity_package: String, metadata_module_package: String, package_of_direct_caller_virtual_badge: String, package_owner_badge: String, package_package: String, pool_package: String, resource_package: String, role_assignment_module_package: String, royalty_module_package: String, secp256k1_signature_virtual_badge: String, system_transaction_badge: String, transaction_processor_package: String, transaction_tracker: String, validator_owner_badge: String, xrd: String) -> NetworkConfigurationResponseWellKnownAddresses { NetworkConfigurationResponseWellKnownAddresses { access_controller_package, @@ -100,8 +104,10 @@ impl NetworkConfigurationResponseWellKnownAddresses { royalty_module_package, secp256k1_signature_virtual_badge, system_transaction_badge, + test_utils_package: None, transaction_processor_package, transaction_tracker, + transaction_tracker_package: None, validator_owner_badge, xrd, } diff --git a/generated-clients/core-api-client/sync-client/src/models/network_definition.rs b/generated-clients/core-api-client/sync-client/src/models/network_definition.rs index 7623404..d599eae 100644 --- a/generated-clients/core-api-client/sync-client/src/models/network_definition.rs +++ b/generated-clients/core-api-client/sync-client/src/models/network_definition.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/network_status_request.rs b/generated-clients/core-api-client/sync-client/src/models/network_status_request.rs index 9342657..5f529ab 100644 --- a/generated-clients/core-api-client/sync-client/src/models/network_status_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/network_status_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/network_status_response.rs b/generated-clients/core-api-client/sync-client/src/models/network_status_response.rs index 8e4d355..0829ff2 100644 --- a/generated-clients/core-api-client/sync-client/src/models/network_status_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/network_status_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -19,9 +19,9 @@ pub struct NetworkStatusResponse { /// A descriptor for the current protocol version that the node is running. #[serde(rename = "current_protocol_version")] pub current_protocol_version: String, - /// The current state identifier at the top of the node's copy of the ledger (ie as of the latest committed transaction). It is not present until genesis has been run. - #[serde(rename = "current_state_identifier", skip_serializing_if = "Option::is_none")] - pub current_state_identifier: Option, + /// The current state identifier at the top of the node's copy of the ledger (i.e. as of the latest committed transaction). + #[serde(rename = "current_state_identifier")] + pub current_state_identifier: models::CommittedStateIdentifier, /// The epoch details for the genesis epoch and round. The genesis epoch will be the last Olympia epoch + 1, and have a \"fake\" round-number 1 (because there is no round for the genesis transaction). In the Gateway, this can be used for the epoch and round number before the first RoundUpdate transaction. It is not present until genesis has been run. #[serde(rename = "genesis_epoch_round", skip_serializing_if = "Option::is_none")] pub genesis_epoch_round: Option, @@ -37,11 +37,11 @@ pub struct NetworkStatusResponse { } impl NetworkStatusResponse { - pub fn new(current_protocol_version: String, pre_genesis_state_identifier: models::CommittedStateIdentifier) -> NetworkStatusResponse { + pub fn new(current_protocol_version: String, current_state_identifier: models::CommittedStateIdentifier, pre_genesis_state_identifier: models::CommittedStateIdentifier) -> NetworkStatusResponse { NetworkStatusResponse { current_epoch_round: None, current_protocol_version, - current_state_identifier: None, + current_state_identifier, genesis_epoch_round: None, post_genesis_epoch_round: None, post_genesis_state_identifier: None, diff --git a/generated-clients/core-api-client/sync-client/src/models/next_epoch.rs b/generated-clients/core-api-client/sync-client/src/models/next_epoch.rs index d9784c7..c542588 100644 --- a/generated-clients/core-api-client/sync-client/src/models/next_epoch.rs +++ b/generated-clients/core-api-client/sync-client/src/models/next_epoch.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_authorized_depositor_badge.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_authorized_depositor_badge.rs index ebc89da..b2e8bf7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_authorized_depositor_badge.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_authorized_depositor_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_global_id.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_global_id.rs index 01dbb85..26c812f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_global_id.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_global_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_id_type.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_id_type.rs index 0916299..eaa0527 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_id_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_id_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_local_id.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_local_id.rs index d665923..e455e3c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_local_id.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_local_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_presented_badge.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_presented_badge.rs index 4e4bc37..0ad8e32 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_presented_badge.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_presented_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_requirement.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_requirement.rs index bc0bd14..0360573 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_requirement.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_amount.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_amount.rs index a2f63e1..9b38f9d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_amount.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_amount.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_data_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_data_entry_substate.rs index 85e3ad2..24c4cab 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_data_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_data_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_data_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_data_entry_value.rs index 14ca3c7..4d27b31 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_data_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_data_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_id_type_substate.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_id_type_substate.rs index cc92215..7d84c83 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_id_type_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_id_type_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_id_type_value.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_id_type_value.rs index ce65365..e81cd51 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_id_type_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_id_type_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_mutable_fields_substate.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_mutable_fields_substate.rs index 463866e..d8938e9 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_mutable_fields_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_mutable_fields_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_mutable_fields_value.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_mutable_fields_value.rs index c32f6a8..476dfd3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_mutable_fields_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_mutable_fields_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_total_supply_substate.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_total_supply_substate.rs index 68a6fd3..fc04f5a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_total_supply_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_total_supply_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_total_supply_value.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_total_supply_value.rs index f915a37..094baee 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_total_supply_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_resource_manager_field_total_supply_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_contents_index_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_contents_index_entry_substate.rs index c417aed..74b681f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_contents_index_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_contents_index_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_contents_index_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_contents_index_entry_value.rs index e11cafc..f6fd686 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_contents_index_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_contents_index_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_balance_substate.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_balance_substate.rs index a119127..af28415 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_balance_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_balance_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_balance_value.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_balance_value.rs index ea45187..2a15c8b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_balance_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_balance_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_frozen_status_substate.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_frozen_status_substate.rs index bc4b5f8..406d2ba 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_frozen_status_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_frozen_status_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_frozen_status_value.rs b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_frozen_status_value.rs index 12d0c0c..cd06772 100644 --- a/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_frozen_status_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/non_fungible_vault_field_frozen_status_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/notarized_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/notarized_transaction.rs index db6fc5a..a411101 100644 --- a/generated-clients/core-api-client/sync-client/src/models/notarized_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/notarized_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/notarized_transaction_v2.rs b/generated-clients/core-api-client/sync-client/src/models/notarized_transaction_v2.rs index 881249e..41f8a30 100644 --- a/generated-clients/core-api-client/sync-client/src/models/notarized_transaction_v2.rs +++ b/generated-clients/core-api-client/sync-client/src/models/notarized_transaction_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/object_field_structure.rs b/generated-clients/core-api-client/sync-client/src/models/object_field_structure.rs index de51380..c74f14b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/object_field_structure.rs +++ b/generated-clients/core-api-client/sync-client/src/models/object_field_structure.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/object_hook.rs b/generated-clients/core-api-client/sync-client/src/models/object_hook.rs index e75abd3..e3a54b4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/object_hook.rs +++ b/generated-clients/core-api-client/sync-client/src/models/object_hook.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/object_instance_type_reference.rs b/generated-clients/core-api-client/sync-client/src/models/object_instance_type_reference.rs index 94b714f..7816a61 100644 --- a/generated-clients/core-api-client/sync-client/src/models/object_instance_type_reference.rs +++ b/generated-clients/core-api-client/sync-client/src/models/object_instance_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/object_role_key.rs b/generated-clients/core-api-client/sync-client/src/models/object_role_key.rs index 10a6f24..7a6f5b4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/object_role_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/object_role_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/object_substate_type_reference.rs b/generated-clients/core-api-client/sync-client/src/models/object_substate_type_reference.rs index d56112f..be6867d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/object_substate_type_reference.rs +++ b/generated-clients/core-api-client/sync-client/src/models/object_substate_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/object_substate_type_reference_type.rs b/generated-clients/core-api-client/sync-client/src/models/object_substate_type_reference_type.rs index 78b109c..d7d7c94 100644 --- a/generated-clients/core-api-client/sync-client/src/models/object_substate_type_reference_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/object_substate_type_reference_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/object_type_info_details.rs b/generated-clients/core-api-client/sync-client/src/models/object_type_info_details.rs index 0318d34..c55e40b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/object_type_info_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/object_type_info_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/one_resource_pool_field_state_substate.rs b/generated-clients/core-api-client/sync-client/src/models/one_resource_pool_field_state_substate.rs index 8afe6af..7a8ff76 100644 --- a/generated-clients/core-api-client/sync-client/src/models/one_resource_pool_field_state_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/one_resource_pool_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/one_resource_pool_field_state_value.rs b/generated-clients/core-api-client/sync-client/src/models/one_resource_pool_field_state_value.rs index 6c0a1f7..a53bc31 100644 --- a/generated-clients/core-api-client/sync-client/src/models/one_resource_pool_field_state_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/one_resource_pool_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/owner_role.rs b/generated-clients/core-api-client/sync-client/src/models/owner_role.rs index 0360b3c..4e0a69b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/owner_role.rs +++ b/generated-clients/core-api-client/sync-client/src/models/owner_role.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/owner_role_updater.rs b/generated-clients/core-api-client/sync-client/src/models/owner_role_updater.rs index e23a53a..285226d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/owner_role_updater.rs +++ b/generated-clients/core-api-client/sync-client/src/models/owner_role_updater.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_auth_template_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_auth_template_entry_substate.rs index 4faf06e..f51001f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_auth_template_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_auth_template_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_auth_template_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_auth_template_entry_value.rs index ca5402f..ad49191 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_auth_template_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_auth_template_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_definition_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_definition_entry_substate.rs index 02a1eb8..84f9c76 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_definition_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_definition_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_definition_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_definition_entry_value.rs index 90fea75..9ac60c3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_definition_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_definition_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_dependencies_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_dependencies_entry_substate.rs index 63cbd54..b0d13ac 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_dependencies_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_dependencies_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_dependencies_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_dependencies_entry_value.rs index 2bdc464..598f8e1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_dependencies_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_dependencies_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_royalty_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_royalty_entry_substate.rs index d3bf6a4..ac7395a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_royalty_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_royalty_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_royalty_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_royalty_entry_value.rs index 22870ca..fbb130e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_blueprint_royalty_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_blueprint_royalty_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_code_instrumented_code_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/package_code_instrumented_code_entry_substate.rs index e4fc637..21b508e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_code_instrumented_code_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_code_instrumented_code_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_code_instrumented_code_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/package_code_instrumented_code_entry_value.rs index 1bab95e..450a8f1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_code_instrumented_code_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_code_instrumented_code_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_code_key.rs b/generated-clients/core-api-client/sync-client/src/models/package_code_key.rs index a751490..12585ae 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_code_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_code_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_code_original_code_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/package_code_original_code_entry_substate.rs index 34afa90..afca2a6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_code_original_code_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_code_original_code_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_code_original_code_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/package_code_original_code_entry_value.rs index 6ecae25..0ff89fb 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_code_original_code_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_code_original_code_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_code_vm_type_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/package_code_vm_type_entry_substate.rs index a33da4c..7dca79a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_code_vm_type_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_code_vm_type_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_code_vm_type_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/package_code_vm_type_entry_value.rs index 1cf8c01..d595e6c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_code_vm_type_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_code_vm_type_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_export.rs b/generated-clients/core-api-client/sync-client/src/models/package_export.rs index 1999493..2da9dee 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_export.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_export.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_field_royalty_accumulator_substate.rs b/generated-clients/core-api-client/sync-client/src/models/package_field_royalty_accumulator_substate.rs index e10eab9..6adfd73 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_field_royalty_accumulator_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_field_royalty_accumulator_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_field_royalty_accumulator_value.rs b/generated-clients/core-api-client/sync-client/src/models/package_field_royalty_accumulator_value.rs index 726c98c..06232aa 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_field_royalty_accumulator_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_field_royalty_accumulator_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/package_type_reference.rs b/generated-clients/core-api-client/sync-client/src/models/package_type_reference.rs index 8b31035..f3346c3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/package_type_reference.rs +++ b/generated-clients/core-api-client/sync-client/src/models/package_type_reference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_ledger_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_ledger_transaction.rs index 5ad855f..4092931 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_ledger_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_ledger_transaction_identifiers.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_ledger_transaction_identifiers.rs index 3536e91..b39c745 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_ledger_transaction_identifiers.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_ledger_transaction_identifiers.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction.rs index 5399b3b..ae27871 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_identifiers.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_identifiers.rs index 2d7cb25..3905066 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_identifiers.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_identifiers.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_v2.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_v2.rs index 39344b1..337137c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_v2.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_validation_error.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_validation_error.rs index 4c30eba..4169d1d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_validation_error.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_notarized_transaction_validation_error.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_signed_transaction_intent.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_signed_transaction_intent.rs index 27b709c..cdc5b6a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_signed_transaction_intent.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_signed_transaction_intent.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_signed_transaction_intent_identifiers.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_signed_transaction_intent_identifiers.rs index 81f3443..04c78aa 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_signed_transaction_intent_identifiers.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_signed_transaction_intent_identifiers.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_transaction.rs index b5bd7dd..b435791 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_intent.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_intent.rs index 67e319e..54a1b68 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_intent.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_intent.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_intent_identifiers.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_intent_identifiers.rs index 45cb16e..368359b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_intent_identifiers.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_intent_identifiers.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_type.rs b/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_type.rs index 51ca108..b6126bc 100644 --- a/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/parsed_transaction_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/partition_description.rs b/generated-clients/core-api-client/sync-client/src/models/partition_description.rs index 02d11d6..9ada6c4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/partition_description.rs +++ b/generated-clients/core-api-client/sync-client/src/models/partition_description.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/partition_description_type.rs b/generated-clients/core-api-client/sync-client/src/models/partition_description_type.rs index d7c25e0..046e040 100644 --- a/generated-clients/core-api-client/sync-client/src/models/partition_description_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/partition_description_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/partition_id.rs b/generated-clients/core-api-client/sync-client/src/models/partition_id.rs index 3e90627..9adc9db 100644 --- a/generated-clients/core-api-client/sync-client/src/models/partition_id.rs +++ b/generated-clients/core-api-client/sync-client/src/models/partition_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/partition_kind.rs b/generated-clients/core-api-client/sync-client/src/models/partition_kind.rs index 9d168da..8da4b73 100644 --- a/generated-clients/core-api-client/sync-client/src/models/partition_kind.rs +++ b/generated-clients/core-api-client/sync-client/src/models/partition_kind.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/payment_from_vault.rs b/generated-clients/core-api-client/sync-client/src/models/payment_from_vault.rs index 9d102b2..5354aa9 100644 --- a/generated-clients/core-api-client/sync-client/src/models/payment_from_vault.rs +++ b/generated-clients/core-api-client/sync-client/src/models/payment_from_vault.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/payment_to_royalty_recipient.rs b/generated-clients/core-api-client/sync-client/src/models/payment_to_royalty_recipient.rs index 8bc26c6..6617322 100644 --- a/generated-clients/core-api-client/sync-client/src/models/payment_to_royalty_recipient.rs +++ b/generated-clients/core-api-client/sync-client/src/models/payment_to_royalty_recipient.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/pending_owner_stake_withdrawal.rs b/generated-clients/core-api-client/sync-client/src/models/pending_owner_stake_withdrawal.rs index a5fa459..9176120 100644 --- a/generated-clients/core-api-client/sync-client/src/models/pending_owner_stake_withdrawal.rs +++ b/generated-clients/core-api-client/sync-client/src/models/pending_owner_stake_withdrawal.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/plaintext_message_content.rs b/generated-clients/core-api-client/sync-client/src/models/plaintext_message_content.rs index 016d2d2..29a0f84 100644 --- a/generated-clients/core-api-client/sync-client/src/models/plaintext_message_content.rs +++ b/generated-clients/core-api-client/sync-client/src/models/plaintext_message_content.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/plaintext_message_content_type.rs b/generated-clients/core-api-client/sync-client/src/models/plaintext_message_content_type.rs index 848cc9b..0a1d1f0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/plaintext_message_content_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/plaintext_message_content_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/plaintext_transaction_message.rs b/generated-clients/core-api-client/sync-client/src/models/plaintext_transaction_message.rs index b804be8..eaf6b51 100644 --- a/generated-clients/core-api-client/sync-client/src/models/plaintext_transaction_message.rs +++ b/generated-clients/core-api-client/sync-client/src/models/plaintext_transaction_message.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/pool_vault.rs b/generated-clients/core-api-client/sync-client/src/models/pool_vault.rs index 683669d..c7299ad 100644 --- a/generated-clients/core-api-client/sync-client/src/models/pool_vault.rs +++ b/generated-clients/core-api-client/sync-client/src/models/pool_vault.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/preparation_settings.rs b/generated-clients/core-api-client/sync-client/src/models/preparation_settings.rs new file mode 100644 index 0000000..360eea3 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/preparation_settings.rs @@ -0,0 +1,42 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct PreparationSettings { + #[serde(rename = "max_blobs")] + pub max_blobs: String, + #[serde(rename = "max_child_subintents_per_intent")] + pub max_child_subintents_per_intent: String, + #[serde(rename = "max_ledger_payload_length")] + pub max_ledger_payload_length: String, + #[serde(rename = "max_subintents_per_transaction")] + pub max_subintents_per_transaction: String, + #[serde(rename = "max_user_payload_length")] + pub max_user_payload_length: String, + #[serde(rename = "v2_transactions_permitted")] + pub v2_transactions_permitted: bool, +} + +impl PreparationSettings { + pub fn new(max_blobs: String, max_child_subintents_per_intent: String, max_ledger_payload_length: String, max_subintents_per_transaction: String, max_user_payload_length: String, v2_transactions_permitted: bool) -> PreparationSettings { + PreparationSettings { + max_blobs, + max_child_subintents_per_intent, + max_ledger_payload_length, + max_subintents_per_transaction, + max_user_payload_length, + v2_transactions_permitted, + } + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/presented_badge.rs b/generated-clients/core-api-client/sync-client/src/models/presented_badge.rs index 88ee0f0..0d3be76 100644 --- a/generated-clients/core-api-client/sync-client/src/models/presented_badge.rs +++ b/generated-clients/core-api-client/sync-client/src/models/presented_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/presented_badge_type.rs b/generated-clients/core-api-client/sync-client/src/models/presented_badge_type.rs index a64ca64..0c74bfb 100644 --- a/generated-clients/core-api-client/sync-client/src/models/presented_badge_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/presented_badge_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/preview_flags.rs b/generated-clients/core-api-client/sync-client/src/models/preview_flags.rs new file mode 100644 index 0000000..2c0991e --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/preview_flags.rs @@ -0,0 +1,40 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct PreviewFlags { + /// If enabled, each manifest processor's auth zone will be given a simulated proof of every signature, which can be used to pass signature access rules. This can be used to preview transactions even if the required signatures are not known ahead of time. See the documentation on [advanced access rules](https://docs.radixdlt.com/docs/advanced-accessrules#signature-requirements) for more information. + #[serde(rename = "assume_all_signature_proofs", skip_serializing_if = "Option::is_none")] + pub assume_all_signature_proofs: Option, + /// If enabled, all authorization checks are skipped during execution. This could be used to e.g.: * Preview protocol update style transactions. * Mint resources for previewing trades with resources you don't own. If doing this, be warned: only resources which were potentially mintable/burnable at creation time will be mintable/burnable, due to feature flags on the resource. Warning: this mode of operation is quite a departure from normal operation: * Calculated fees will likely be lower than a standard execution. * This mode can subtly break invariants some dApp code might rely on, or result in unexpected behaviour, so the execution result might not be valid for your needs. For example, if this flag was used to mint pool units to preview a redemption (or some dApp interaction which behind the scenes redeemed them), they'd redeem for less than they're currently worth, because the blueprint code relies on the total supply of the pool units to calculate their redemption worth, and you've just inflated the total supply through the mint operation. + #[serde(rename = "disable_auth_checks", skip_serializing_if = "Option::is_none")] + pub disable_auth_checks: Option, + /// If enabled, the various runtime epoch-related verifications are skipped: - The `start_epoch_inclusive` and `end_epoch_exclusive` parameters, if specified, are ignored. - The duplicate intent checks (which rely on the expiry epoch) are also ignored. However, if the start and end epoch are provided, they must still be statically valid. We recommend using a value of `start_epoch_inclusive = 1` and `end_epoch_exclusive = 2` in this case. + #[serde(rename = "skip_epoch_check", skip_serializing_if = "Option::is_none")] + pub skip_epoch_check: Option, + /// If enabled, a large simulated pool of XRD is marked as locked. This mode can be used to estimate fees. To get a reliable estimate, we recommend that your transaction is as close as possible to the real transaction. For example: - You should still use a lock fee command, but you can set it to lock a fee of 0. - You should include the public keys that will sign the transaction, so the cost of signature verification and payload size can be accounted for. + #[serde(rename = "use_free_credit", skip_serializing_if = "Option::is_none")] + pub use_free_credit: Option, +} + +impl PreviewFlags { + pub fn new() -> PreviewFlags { + PreviewFlags { + assume_all_signature_proofs: None, + disable_auth_checks: None, + skip_epoch_check: None, + use_free_credit: None, + } + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/preview_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/preview_transaction.rs new file mode 100644 index 0000000..8cbe3ad --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/preview_transaction.rs @@ -0,0 +1,27 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] +#[serde(tag = "type")] +pub enum PreviewTransaction { + #[serde(rename="Compiled")] + Compiled(models::CompiledPreviewTransaction), +} + +impl Default for PreviewTransaction { + fn default() -> Self { + Self::Compiled(Default::default()) + } +} + + diff --git a/generated-clients/core-api-client/sync-client/src/models/preview_transaction_type.rs b/generated-clients/core-api-client/sync-client/src/models/preview_transaction_type.rs new file mode 100644 index 0000000..e738a00 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/preview_transaction_type.rs @@ -0,0 +1,35 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +/// +#[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] +pub enum PreviewTransactionType { + #[serde(rename = "Compiled")] + Compiled, + +} + +impl std::fmt::Display for PreviewTransactionType { + fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { + match self { + Self::Compiled => write!(f, "Compiled"), + } + } +} + +impl Default for PreviewTransactionType { + fn default() -> PreviewTransactionType { + Self::Compiled + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/primary_role_recovery_attempt.rs b/generated-clients/core-api-client/sync-client/src/models/primary_role_recovery_attempt.rs index cdc0df2..7a488a3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/primary_role_recovery_attempt.rs +++ b/generated-clients/core-api-client/sync-client/src/models/primary_role_recovery_attempt.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/proof_access_rule_node.rs b/generated-clients/core-api-client/sync-client/src/models/proof_rule_composite_requirement.rs similarity index 87% rename from generated-clients/core-api-client/sync-client/src/models/proof_access_rule_node.rs rename to generated-clients/core-api-client/sync-client/src/models/proof_rule_composite_requirement.rs index d323e22..6567bad 100644 --- a/generated-clients/core-api-client/sync-client/src/models/proof_access_rule_node.rs +++ b/generated-clients/core-api-client/sync-client/src/models/proof_rule_composite_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct ProofAccessRuleNode { +pub struct ProofRuleCompositeRequirement { #[serde(rename = "proof_rule")] - pub proof_rule: models::ProofRule, + pub proof_rule: models::BasicRequirement, } -impl ProofAccessRuleNode { - pub fn new(proof_rule: models::ProofRule) -> ProofAccessRuleNode { - ProofAccessRuleNode { +impl ProofRuleCompositeRequirement { + pub fn new(proof_rule: models::BasicRequirement) -> ProofRuleCompositeRequirement { + ProofRuleCompositeRequirement { proof_rule, } } diff --git a/generated-clients/core-api-client/sync-client/src/models/proposer_reward.rs b/generated-clients/core-api-client/sync-client/src/models/proposer_reward.rs index e3b9251..8dbbe7b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/proposer_reward.rs +++ b/generated-clients/core-api-client/sync-client/src/models/proposer_reward.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/protected_access_rule.rs b/generated-clients/core-api-client/sync-client/src/models/protected_access_rule.rs index d8ecdaa..1daebe7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/protected_access_rule.rs +++ b/generated-clients/core-api-client/sync-client/src/models/protected_access_rule.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -14,11 +14,11 @@ use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] pub struct ProtectedAccessRule { #[serde(rename = "access_rule")] - pub access_rule: models::AccessRuleNode, + pub access_rule: models::CompositeRequirement, } impl ProtectedAccessRule { - pub fn new(access_rule: models::AccessRuleNode) -> ProtectedAccessRule { + pub fn new(access_rule: models::CompositeRequirement) -> ProtectedAccessRule { ProtectedAccessRule { access_rule, } diff --git a/generated-clients/core-api-client/sync-client/src/models/protocol_update_ledger_proof_origin.rs b/generated-clients/core-api-client/sync-client/src/models/protocol_update_ledger_proof_origin.rs index 7605cb1..7bed3b3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/protocol_update_ledger_proof_origin.rs +++ b/generated-clients/core-api-client/sync-client/src/models/protocol_update_ledger_proof_origin.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/protocol_update_status.rs b/generated-clients/core-api-client/sync-client/src/models/protocol_update_status.rs index 98d4614..5cdfe9d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/protocol_update_status.rs +++ b/generated-clients/core-api-client/sync-client/src/models/protocol_update_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_latest_commit.rs b/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_latest_commit.rs index 0a88818..3b76182 100644 --- a/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_latest_commit.rs +++ b/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_latest_commit.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_module_field_summary_substate.rs b/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_module_field_summary_substate.rs index 48c867f..cd65885 100644 --- a/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_module_field_summary_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_module_field_summary_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_type.rs b/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_type.rs index ba2186a..f5e2475 100644 --- a/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/protocol_update_status_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/protocol_version_readiness.rs b/generated-clients/core-api-client/sync-client/src/models/protocol_version_readiness.rs index 25b169d..04c2e60 100644 --- a/generated-clients/core-api-client/sync-client/src/models/protocol_version_readiness.rs +++ b/generated-clients/core-api-client/sync-client/src/models/protocol_version_readiness.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/public_key.rs b/generated-clients/core-api-client/sync-client/src/models/public_key.rs index 6c05a66..fc78a05 100644 --- a/generated-clients/core-api-client/sync-client/src/models/public_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/public_key_type.rs b/generated-clients/core-api-client/sync-client/src/models/public_key_type.rs index fd1819c..1ff206a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/public_key_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/public_key_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/receiver_info.rs b/generated-clients/core-api-client/sync-client/src/models/receiver_info.rs index f2812ce..f3a037a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/receiver_info.rs +++ b/generated-clients/core-api-client/sync-client/src/models/receiver_info.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/recovery_proposal.rs b/generated-clients/core-api-client/sync-client/src/models/recovery_proposal.rs index 1db54cb..3524322 100644 --- a/generated-clients/core-api-client/sync-client/src/models/recovery_proposal.rs +++ b/generated-clients/core-api-client/sync-client/src/models/recovery_proposal.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/recovery_role_recovery_attempt.rs b/generated-clients/core-api-client/sync-client/src/models/recovery_role_recovery_attempt.rs index 97c13fb..a8daa27 100644 --- a/generated-clients/core-api-client/sync-client/src/models/recovery_role_recovery_attempt.rs +++ b/generated-clients/core-api-client/sync-client/src/models/recovery_role_recovery_attempt.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/reference_type.rs b/generated-clients/core-api-client/sync-client/src/models/reference_type.rs index c83f817..9780e1a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/reference_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/reference_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/remote_generic_substitution.rs b/generated-clients/core-api-client/sync-client/src/models/remote_generic_substitution.rs index 9a4cf95..ac8cbc1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/remote_generic_substitution.rs +++ b/generated-clients/core-api-client/sync-client/src/models/remote_generic_substitution.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/requested_state_version_out_of_bounds_error_details.rs b/generated-clients/core-api-client/sync-client/src/models/requested_state_version_out_of_bounds_error_details.rs index 3d0b89c..ec4e488 100644 --- a/generated-clients/core-api-client/sync-client/src/models/requested_state_version_out_of_bounds_error_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/requested_state_version_out_of_bounds_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/async-client/src/models/require_proof_rule.rs b/generated-clients/core-api-client/sync-client/src/models/require_basic_requirement.rs similarity index 90% rename from generated-clients/core-api-client/async-client/src/models/require_proof_rule.rs rename to generated-clients/core-api-client/sync-client/src/models/require_basic_requirement.rs index bfd7b7b..479e264 100644 --- a/generated-clients/core-api-client/async-client/src/models/require_proof_rule.rs +++ b/generated-clients/core-api-client/sync-client/src/models/require_basic_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -12,14 +12,14 @@ use crate::models; use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct RequireProofRule { +pub struct RequireBasicRequirement { #[serde(rename = "requirement")] pub requirement: models::Requirement, } -impl RequireProofRule { - pub fn new(requirement: models::Requirement) -> RequireProofRule { - RequireProofRule { +impl RequireBasicRequirement { + pub fn new(requirement: models::Requirement) -> RequireBasicRequirement { + RequireBasicRequirement { requirement, } } diff --git a/generated-clients/core-api-client/sync-client/src/models/requirement.rs b/generated-clients/core-api-client/sync-client/src/models/requirement.rs index 190b98f..ff3e115 100644 --- a/generated-clients/core-api-client/sync-client/src/models/requirement.rs +++ b/generated-clients/core-api-client/sync-client/src/models/requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -11,6 +11,7 @@ use crate::models; use serde::{Deserialize, Serialize}; +/// Requirement : This is called `ResourceOrNonFungible` in the engine. #[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] #[serde(tag = "type")] pub enum Requirement { diff --git a/generated-clients/core-api-client/sync-client/src/models/requirement_type.rs b/generated-clients/core-api-client/sync-client/src/models/requirement_type.rs index 17282e0..d297144 100644 --- a/generated-clients/core-api-client/sync-client/src/models/requirement_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/requirement_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/resource_amount.rs b/generated-clients/core-api-client/sync-client/src/models/resource_amount.rs index a459219..8556d32 100644 --- a/generated-clients/core-api-client/sync-client/src/models/resource_amount.rs +++ b/generated-clients/core-api-client/sync-client/src/models/resource_amount.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/resource_authorized_depositor_badge.rs b/generated-clients/core-api-client/sync-client/src/models/resource_authorized_depositor_badge.rs index 7750a37..62ace51 100644 --- a/generated-clients/core-api-client/sync-client/src/models/resource_authorized_depositor_badge.rs +++ b/generated-clients/core-api-client/sync-client/src/models/resource_authorized_depositor_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/resource_change.rs b/generated-clients/core-api-client/sync-client/src/models/resource_change.rs index 1640576..510a4b3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/resource_change.rs +++ b/generated-clients/core-api-client/sync-client/src/models/resource_change.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/resource_key.rs b/generated-clients/core-api-client/sync-client/src/models/resource_key.rs index 3129999..fe90b30 100644 --- a/generated-clients/core-api-client/sync-client/src/models/resource_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/resource_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/resource_preference.rs b/generated-clients/core-api-client/sync-client/src/models/resource_preference.rs index 1ee79cb..eb5d485 100644 --- a/generated-clients/core-api-client/sync-client/src/models/resource_preference.rs +++ b/generated-clients/core-api-client/sync-client/src/models/resource_preference.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/resource_presented_badge.rs b/generated-clients/core-api-client/sync-client/src/models/resource_presented_badge.rs index ee6f3e9..f264fa1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/resource_presented_badge.rs +++ b/generated-clients/core-api-client/sync-client/src/models/resource_presented_badge.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/resource_requirement.rs b/generated-clients/core-api-client/sync-client/src/models/resource_requirement.rs index 653bbdc..002cde3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/resource_requirement.rs +++ b/generated-clients/core-api-client/sync-client/src/models/resource_requirement.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/resource_specific_deposit_behaviour.rs b/generated-clients/core-api-client/sync-client/src/models/resource_specific_deposit_behaviour.rs index ba89d27..0d1e174 100644 --- a/generated-clients/core-api-client/sync-client/src/models/resource_specific_deposit_behaviour.rs +++ b/generated-clients/core-api-client/sync-client/src/models/resource_specific_deposit_behaviour.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/resource_type.rs b/generated-clients/core-api-client/sync-client/src/models/resource_type.rs index a468e9e..a7e81aa 100644 --- a/generated-clients/core-api-client/sync-client/src/models/resource_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/resource_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_field_owner_role_substate.rs b/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_field_owner_role_substate.rs index 1088c53..539ccb8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_field_owner_role_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_field_owner_role_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_field_owner_role_value.rs b/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_field_owner_role_value.rs index 01a85fc..5de94ed 100644 --- a/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_field_owner_role_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_field_owner_role_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_rule_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_rule_entry_substate.rs index bc498c0..cf636af 100644 --- a/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_rule_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_rule_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_rule_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_rule_entry_value.rs index 0a2fdc0..936f9d1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_rule_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/role_assignment_module_rule_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/role_details.rs b/generated-clients/core-api-client/sync-client/src/models/role_details.rs index a499b49..2521cce 100644 --- a/generated-clients/core-api-client/sync-client/src/models/role_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/role_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/role_protected_method_accessibility.rs b/generated-clients/core-api-client/sync-client/src/models/role_protected_method_accessibility.rs index c630516..68f5324 100644 --- a/generated-clients/core-api-client/sync-client/src/models/role_protected_method_accessibility.rs +++ b/generated-clients/core-api-client/sync-client/src/models/role_protected_method_accessibility.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/role_specification.rs b/generated-clients/core-api-client/sync-client/src/models/role_specification.rs index 9d8d900..ec55585 100644 --- a/generated-clients/core-api-client/sync-client/src/models/role_specification.rs +++ b/generated-clients/core-api-client/sync-client/src/models/role_specification.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/round_update_ledger_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/round_update_ledger_transaction.rs index 3e82935..640791f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/round_update_ledger_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/round_update_ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/round_update_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/round_update_transaction.rs index 00786e5..2dbc625 100644 --- a/generated-clients/core-api-client/sync-client/src/models/round_update_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/round_update_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/royalty_amount.rs b/generated-clients/core-api-client/sync-client/src/models/royalty_amount.rs index f3dcf7f..a97a3f7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/royalty_amount.rs +++ b/generated-clients/core-api-client/sync-client/src/models/royalty_amount.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/royalty_module_field_state_substate.rs b/generated-clients/core-api-client/sync-client/src/models/royalty_module_field_state_substate.rs index 094bfeb..03a8871 100644 --- a/generated-clients/core-api-client/sync-client/src/models/royalty_module_field_state_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/royalty_module_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/royalty_module_field_state_value.rs b/generated-clients/core-api-client/sync-client/src/models/royalty_module_field_state_value.rs index ead8f50..ff303bd 100644 --- a/generated-clients/core-api-client/sync-client/src/models/royalty_module_field_state_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/royalty_module_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/royalty_module_method_royalty_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/royalty_module_method_royalty_entry_substate.rs index fe154b2..809f8cb 100644 --- a/generated-clients/core-api-client/sync-client/src/models/royalty_module_method_royalty_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/royalty_module_method_royalty_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/royalty_module_method_royalty_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/royalty_module_method_royalty_entry_value.rs index bf114c8..4beb45e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/royalty_module_method_royalty_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/royalty_module_method_royalty_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/sbor_data.rs b/generated-clients/core-api-client/sync-client/src/models/sbor_data.rs index 0bd33db..ce4d0d5 100644 --- a/generated-clients/core-api-client/sync-client/src/models/sbor_data.rs +++ b/generated-clients/core-api-client/sync-client/src/models/sbor_data.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/sbor_format_options.rs b/generated-clients/core-api-client/sync-client/src/models/sbor_format_options.rs index 448048a..24ef8f7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/sbor_format_options.rs +++ b/generated-clients/core-api-client/sync-client/src/models/sbor_format_options.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/scenarios_request.rs b/generated-clients/core-api-client/sync-client/src/models/scenarios_request.rs index 8d42423..763c22d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/scenarios_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/scenarios_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/scenarios_response.rs b/generated-clients/core-api-client/sync-client/src/models/scenarios_response.rs index dbba31b..7c903a3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/scenarios_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/scenarios_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/schema_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/schema_entry_substate.rs index 28a4582..d8fe4fc 100644 --- a/generated-clients/core-api-client/sync-client/src/models/schema_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/schema_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/schema_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/schema_entry_value.rs index 3d1d42a..937591c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/schema_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/schema_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/schema_key.rs b/generated-clients/core-api-client/sync-client/src/models/schema_key.rs index 6b61f27..2d5453f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/schema_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/schema_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/scoped_type_id.rs b/generated-clients/core-api-client/sync-client/src/models/scoped_type_id.rs index 246ccce..d3c732c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/scoped_type_id.rs +++ b/generated-clients/core-api-client/sync-client/src/models/scoped_type_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/scrypto_instant.rs b/generated-clients/core-api-client/sync-client/src/models/scrypto_instant.rs index 58b90e9..cd9dfa4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/scrypto_instant.rs +++ b/generated-clients/core-api-client/sync-client/src/models/scrypto_instant.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/scrypto_schema.rs b/generated-clients/core-api-client/sync-client/src/models/scrypto_schema.rs index a19d8dc..8becd78 100644 --- a/generated-clients/core-api-client/sync-client/src/models/scrypto_schema.rs +++ b/generated-clients/core-api-client/sync-client/src/models/scrypto_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/signalling_validator.rs b/generated-clients/core-api-client/sync-client/src/models/signalling_validator.rs index 977c260..28b4c72 100644 --- a/generated-clients/core-api-client/sync-client/src/models/signalling_validator.rs +++ b/generated-clients/core-api-client/sync-client/src/models/signalling_validator.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/signature.rs b/generated-clients/core-api-client/sync-client/src/models/signature.rs index fb3d211..ab8713b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/signature.rs +++ b/generated-clients/core-api-client/sync-client/src/models/signature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/signature_with_public_key.rs b/generated-clients/core-api-client/sync-client/src/models/signature_with_public_key.rs index c6d8061..630e4c8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/signature_with_public_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/signature_with_public_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/signed_transaction_intent.rs b/generated-clients/core-api-client/sync-client/src/models/signed_transaction_intent.rs index 62b8bba..aa8f2f3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/signed_transaction_intent.rs +++ b/generated-clients/core-api-client/sync-client/src/models/signed_transaction_intent.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/signed_transaction_intent_v2.rs b/generated-clients/core-api-client/sync-client/src/models/signed_transaction_intent_v2.rs index 01ed4b1..d0d6885 100644 --- a/generated-clients/core-api-client/sync-client/src/models/signed_transaction_intent_v2.rs +++ b/generated-clients/core-api-client/sync-client/src/models/signed_transaction_intent_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/significant_protocol_update_readiness_entry.rs b/generated-clients/core-api-client/sync-client/src/models/significant_protocol_update_readiness_entry.rs index 56c0c2c..1f55336 100644 --- a/generated-clients/core-api-client/sync-client/src/models/significant_protocol_update_readiness_entry.rs +++ b/generated-clients/core-api-client/sync-client/src/models/significant_protocol_update_readiness_entry.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/sorted_index_blueprint_collection_schema.rs b/generated-clients/core-api-client/sync-client/src/models/sorted_index_blueprint_collection_schema.rs index 7e00f71..77a4b4a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/sorted_index_blueprint_collection_schema.rs +++ b/generated-clients/core-api-client/sync-client/src/models/sorted_index_blueprint_collection_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/sorted_substate_key.rs b/generated-clients/core-api-client/sync-client/src/models/sorted_substate_key.rs index 72be277..78213f7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/sorted_substate_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/sorted_substate_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_access_controller_request.rs b/generated-clients/core-api-client/sync-client/src/models/state_access_controller_request.rs index aa6f280..55b8d15 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_access_controller_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_access_controller_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_access_controller_response.rs b/generated-clients/core-api-client/sync-client/src/models/state_access_controller_response.rs index 29f591a..5dbde3f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_access_controller_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_access_controller_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_account_request.rs b/generated-clients/core-api-client/sync-client/src/models/state_account_request.rs index ad9cd32..c2b8943 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_account_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_account_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_account_response.rs b/generated-clients/core-api-client/sync-client/src/models/state_account_response.rs index 58b9d8a..65be49a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_account_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_account_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_component_descendent_node.rs b/generated-clients/core-api-client/sync-client/src/models/state_component_descendent_node.rs index 7fd76b5..3f7f616 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_component_descendent_node.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_component_descendent_node.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_component_request.rs b/generated-clients/core-api-client/sync-client/src/models/state_component_request.rs index c5a7be6..b7ba98b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_component_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_component_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_component_response.rs b/generated-clients/core-api-client/sync-client/src/models/state_component_response.rs index 43ea2d8..4783f91 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_component_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_component_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_consensus_manager_request.rs b/generated-clients/core-api-client/sync-client/src/models/state_consensus_manager_request.rs index 73feb56..48b0c41 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_consensus_manager_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_consensus_manager_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_consensus_manager_response.rs b/generated-clients/core-api-client/sync-client/src/models/state_consensus_manager_response.rs index 21e5f60..f0e9b79 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_consensus_manager_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_consensus_manager_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_fungible_resource_manager.rs b/generated-clients/core-api-client/sync-client/src/models/state_fungible_resource_manager.rs index 50547a9..1bba010 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_fungible_resource_manager.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_fungible_resource_manager.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_request.rs b/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_request.rs index 0280144..3a39bf9 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_resource_manager.rs b/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_resource_manager.rs index dd63c43..b535a8d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_resource_manager.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_resource_manager.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_response.rs b/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_response.rs index 6fe607e..08c2470 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_non_fungible_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_package_request.rs b/generated-clients/core-api-client/sync-client/src/models/state_package_request.rs index 10b46e5..921c2b0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_package_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_package_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_package_response.rs b/generated-clients/core-api-client/sync-client/src/models/state_package_response.rs index 43369f7..557d887 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_package_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_package_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_resource_manager.rs b/generated-clients/core-api-client/sync-client/src/models/state_resource_manager.rs index 8febfbe..d9600c4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_resource_manager.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_resource_manager.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_resource_request.rs b/generated-clients/core-api-client/sync-client/src/models/state_resource_request.rs index 63895a2..f04b514 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_resource_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_resource_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_resource_response.rs b/generated-clients/core-api-client/sync-client/src/models/state_resource_response.rs index 26b9a2b..36f62df 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_resource_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_resource_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_updates.rs b/generated-clients/core-api-client/sync-client/src/models/state_updates.rs index 90f45fb..1ed3ec9 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_updates.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_updates.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_validator_request.rs b/generated-clients/core-api-client/sync-client/src/models/state_validator_request.rs index 4d54cf0..0e4d3a2 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_validator_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_validator_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/state_validator_response.rs b/generated-clients/core-api-client/sync-client/src/models/state_validator_response.rs index 4f827f2..e95c183 100644 --- a/generated-clients/core-api-client/sync-client/src/models/state_validator_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/state_validator_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/static_blueprint_payload_def.rs b/generated-clients/core-api-client/sync-client/src/models/static_blueprint_payload_def.rs index 7dd684e..cea4e22 100644 --- a/generated-clients/core-api-client/sync-client/src/models/static_blueprint_payload_def.rs +++ b/generated-clients/core-api-client/sync-client/src/models/static_blueprint_payload_def.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/static_role_definition_auth_template.rs b/generated-clients/core-api-client/sync-client/src/models/static_role_definition_auth_template.rs index ad4534c..8c04257 100644 --- a/generated-clients/core-api-client/sync-client/src/models/static_role_definition_auth_template.rs +++ b/generated-clients/core-api-client/sync-client/src/models/static_role_definition_auth_template.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details.rs index ae71b43..1bf3f53 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs index cf1c328..e1145d6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs index ba2ed82..014a80b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_type.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_type.rs index b9c1f20..9cbc18b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_details_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_response.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_response.rs index a9fa665..9952ffa 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter.rs index 507c2a4..4ca608b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_any.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_any.rs index 56e0752..50d2725 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_any.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_any.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_new_epochs.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_new_epochs.rs index 2d8eeb6..b469912 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_new_epochs.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_new_epochs.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_protocol_update_execution.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_protocol_update_execution.rs index ff3a5c8..3447dfb 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_protocol_update_execution.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_protocol_update_execution.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_protocol_update_initializations.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_protocol_update_initializations.rs index 4bd1d3c..7bb0190 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_protocol_update_initializations.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_protocol_update_initializations.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_type.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_type.rs index 549bc0d..a7420b5 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_filter_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_request.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_request.rs index 482342b..cef4d67 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_response.rs b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_response.rs index dd968f4..8db4a72 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_proofs_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_proofs_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_details.rs b/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_details.rs index e0d76a0..0791f1e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_details_type.rs b/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_details_type.rs index a5c69fc..e079806 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_details_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_details_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_response.rs b/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_response.rs index 483d68e..a0458eb 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_transactions_error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_transactions_request.rs b/generated-clients/core-api-client/sync-client/src/models/stream_transactions_request.rs index c6ef403..d3993ae 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_transactions_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_transactions_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/stream_transactions_response.rs b/generated-clients/core-api-client/sync-client/src/models/stream_transactions_response.rs index 583b522..9c56f24 100644 --- a/generated-clients/core-api-client/sync-client/src/models/stream_transactions_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/stream_transactions_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/string_plaintext_message_content.rs b/generated-clients/core-api-client/sync-client/src/models/string_plaintext_message_content.rs index b3bfa57..78f4bba 100644 --- a/generated-clients/core-api-client/sync-client/src/models/string_plaintext_message_content.rs +++ b/generated-clients/core-api-client/sync-client/src/models/string_plaintext_message_content.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/subintent_v2.rs b/generated-clients/core-api-client/sync-client/src/models/subintent_v2.rs index b2cfb4e..d7959e8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/subintent_v2.rs +++ b/generated-clients/core-api-client/sync-client/src/models/subintent_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/substate.rs b/generated-clients/core-api-client/sync-client/src/models/substate.rs index 7bd3f8d..d530bc3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/substate_format_options.rs b/generated-clients/core-api-client/sync-client/src/models/substate_format_options.rs index c3604d1..f6091e6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/substate_format_options.rs +++ b/generated-clients/core-api-client/sync-client/src/models/substate_format_options.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/substate_id.rs b/generated-clients/core-api-client/sync-client/src/models/substate_id.rs index 0fb8f0a..58ded5d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/substate_id.rs +++ b/generated-clients/core-api-client/sync-client/src/models/substate_id.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/substate_key.rs b/generated-clients/core-api-client/sync-client/src/models/substate_key.rs index 75de8a0..12b051b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/substate_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/substate_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/substate_key_type.rs b/generated-clients/core-api-client/sync-client/src/models/substate_key_type.rs index 44c6a64..f04e5c1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/substate_key_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/substate_key_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/substate_system_structure.rs b/generated-clients/core-api-client/sync-client/src/models/substate_system_structure.rs index 8d57602..5852a98 100644 --- a/generated-clients/core-api-client/sync-client/src/models/substate_system_structure.rs +++ b/generated-clients/core-api-client/sync-client/src/models/substate_system_structure.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/substate_system_structure_type.rs b/generated-clients/core-api-client/sync-client/src/models/substate_system_structure_type.rs index cdf96a4..aed1e3e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/substate_system_structure_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/substate_system_structure_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/substate_type.rs b/generated-clients/core-api-client/sync-client/src/models/substate_type.rs index bc33935..343f47a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/substate_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/substate_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/substate_value.rs b/generated-clients/core-api-client/sync-client/src/models/substate_value.rs index a09a5fb..940e48a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/substate_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/substate_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/system_costing_parameters.rs b/generated-clients/core-api-client/sync-client/src/models/system_costing_parameters.rs index 1afd056..4640ed4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/system_costing_parameters.rs +++ b/generated-clients/core-api-client/sync-client/src/models/system_costing_parameters.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/system_field_kind.rs b/generated-clients/core-api-client/sync-client/src/models/system_field_kind.rs index a759cfc..126bb5e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/system_field_kind.rs +++ b/generated-clients/core-api-client/sync-client/src/models/system_field_kind.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/system_field_structure.rs b/generated-clients/core-api-client/sync-client/src/models/system_field_structure.rs index 1fdb903..1360ba9 100644 --- a/generated-clients/core-api-client/sync-client/src/models/system_field_structure.rs +++ b/generated-clients/core-api-client/sync-client/src/models/system_field_structure.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/system_parameters.rs b/generated-clients/core-api-client/sync-client/src/models/system_parameters.rs index 3487647..2a1b2c6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/system_parameters.rs +++ b/generated-clients/core-api-client/sync-client/src/models/system_parameters.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/system_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/system_transaction.rs index 788f949..56df887 100644 --- a/generated-clients/core-api-client/sync-client/src/models/system_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/system_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/system_version.rs b/generated-clients/core-api-client/sync-client/src/models/system_version.rs index 28319d9..8c9c81f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/system_version.rs +++ b/generated-clients/core-api-client/sync-client/src/models/system_version.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -19,6 +19,8 @@ pub enum SystemVersion { V1, #[serde(rename = "V2")] V2, + #[serde(rename = "V3")] + V3, } @@ -27,6 +29,7 @@ impl std::fmt::Display for SystemVersion { match self { Self::V1 => write!(f, "V1"), Self::V2 => write!(f, "V2"), + Self::V3 => write!(f, "V3"), } } } diff --git a/generated-clients/core-api-client/sync-client/src/models/target_identifier.rs b/generated-clients/core-api-client/sync-client/src/models/target_identifier.rs index 05e89eb..a76eba4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/target_identifier.rs +++ b/generated-clients/core-api-client/sync-client/src/models/target_identifier.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/target_identifier_type.rs b/generated-clients/core-api-client/sync-client/src/models/target_identifier_type.rs index 0af46a5..ad7023e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/target_identifier_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/target_identifier_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/timestamped_validator_signature.rs b/generated-clients/core-api-client/sync-client/src/models/timestamped_validator_signature.rs index e580c98..46d514d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/timestamped_validator_signature.rs +++ b/generated-clients/core-api-client/sync-client/src/models/timestamped_validator_signature.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_call_preview_request.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_call_preview_request.rs index f355b83..823a457 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_call_preview_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_call_preview_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_call_preview_response.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_call_preview_response.rs index 7165cf1..25dbd3f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_call_preview_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_call_preview_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_format_options.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_format_options.rs index cbb4cb6..ee07ee8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_format_options.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_format_options.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_header.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_header.rs index 9fc7151..0e004be 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_header.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_header.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_header_v2.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_header_v2.rs index 5948d8a..553a054 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_header_v2.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_header_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_id_key.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_id_key.rs index 2e9c339..1291ec6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_id_key.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_id_key.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_identifiers.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_identifiers.rs index 68fbf63..4f16afa 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_identifiers.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_identifiers.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_intent.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_intent.rs index 1933e3b..809ac27 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_intent.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_intent.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_intent_status.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_intent_status.rs index 4192b81..6f4ceb4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_intent_status.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_intent_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_intent_v2.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_intent_v2.rs index a99cb41..fb4d8d1 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_intent_v2.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_intent_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_message.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_message.rs index 3866a3c..f8db327 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_message.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_message.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_message_type.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_message_type.rs index bbdc10c..51af06f 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_message_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_message_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_parse_request.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_parse_request.rs index 12379af..44164bd 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_parse_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_parse_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_parse_response.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_parse_response.rs index 8e6b3e2..689ef31 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_parse_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_parse_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_payload_details.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_payload_details.rs index e638443..5832905 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_payload_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_payload_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_payload_status.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_payload_status.rs index 0c43e69..ab24f93 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_payload_status.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_payload_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_request.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_request.rs index 7509985..e6f56be 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -18,11 +18,11 @@ pub struct TransactionPreviewRequest { /// An array of hex-encoded blob data, if referenced by the manifest. #[serde(rename = "blobs_hex", skip_serializing_if = "Option::is_none")] pub blobs_hex: Option>, - /// An integer between `0` and `10^10`, marking the epoch at which the transaction is no longer valid. If omitted, a maximum epoch (relative to the `start_epoch_inclusive`) will be used. + /// An integer between `0` and `10^10`, marking the epoch at which the transaction is no longer valid. If not provided, a maximum epoch (relative to the `start_epoch_inclusive`) will be used. #[serde(rename = "end_epoch_exclusive", skip_serializing_if = "Option::is_none")] pub end_epoch_exclusive: Option, - #[serde(rename = "flags")] - pub flags: models::TransactionPreviewRequestFlags, + #[serde(rename = "flags", skip_serializing_if = "Option::is_none")] + pub flags: Option, /// A text representation of a transaction manifest. #[serde(rename = "manifest")] pub manifest: String, @@ -32,46 +32,45 @@ pub struct TransactionPreviewRequest { /// The logical name of the network #[serde(rename = "network")] pub network: String, - /// An integer between `0` and `2^32 - 1`, chosen to allow a unique intent to be created (to enable submitting an otherwise identical/duplicate intent). - #[serde(rename = "nonce")] - pub nonce: u64, - /// Whether the notary should count as a signatory (defaults to `false`). + /// An integer between `0` and `2^32 - 1`, chosen to allow a unique intent to be created (to enable submitting an otherwise identical/duplicate intent). If not provided, this defaults to 0. + #[serde(rename = "nonce", skip_serializing_if = "Option::is_none")] + pub nonce: Option, + /// Whether the notary should be used as a signer (optional). If not provided, this defaults to false. #[serde(rename = "notary_is_signatory", skip_serializing_if = "Option::is_none")] pub notary_is_signatory: Option, - /// The notary public key to use (optional). + /// The notary public key to use. If not provided, this defaults to a fixed public key. #[serde(rename = "notary_public_key", skip_serializing_if = "Option::is_none")] pub notary_public_key: Option, - /// A set of flags to configure the response of the transaction preview. #[serde(rename = "options", skip_serializing_if = "Option::is_none")] pub options: Option, - /// A list of public keys to be used as transaction signers - #[serde(rename = "signer_public_keys")] - pub signer_public_keys: Vec, - /// An integer between `0` and `10^10`, marking the epoch at which the transaction starts being valid. If omitted, the current epoch will be used (taking into account the `at_ledger_state`, if specified). + /// A list of public keys to be used as transaction signers. If not provided, this defaults to an empty array. + #[serde(rename = "signer_public_keys", skip_serializing_if = "Option::is_none")] + pub signer_public_keys: Option>, + /// An integer between `0` and `10^10`, marking the epoch at which the transaction starts being valid. If not provided, the current epoch will be used (taking into account the `at_ledger_state`, if specified). #[serde(rename = "start_epoch_inclusive", skip_serializing_if = "Option::is_none")] pub start_epoch_inclusive: Option, - /// An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to a 1% fee. - #[serde(rename = "tip_percentage")] - pub tip_percentage: u32, + /// An integer between `0` and `65535`, giving the validator tip as a percentage amount. A value of `1` corresponds to a 1% fee. If not provided, this defaults to 0. + #[serde(rename = "tip_percentage", skip_serializing_if = "Option::is_none")] + pub tip_percentage: Option, } impl TransactionPreviewRequest { - pub fn new(flags: models::TransactionPreviewRequestFlags, manifest: String, network: String, nonce: u64, signer_public_keys: Vec, tip_percentage: u32) -> TransactionPreviewRequest { + pub fn new(manifest: String, network: String) -> TransactionPreviewRequest { TransactionPreviewRequest { at_ledger_state: None, blobs_hex: None, end_epoch_exclusive: None, - flags, + flags: None, manifest, message: None, network, - nonce, + nonce: None, notary_is_signatory: None, notary_public_key: None, options: None, - signer_public_keys, + signer_public_keys: None, start_epoch_inclusive: None, - tip_percentage, + tip_percentage: None, } } } diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_request_flags.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_request_flags.rs deleted file mode 100644 index 2833697..0000000 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_request_flags.rs +++ /dev/null @@ -1,40 +0,0 @@ -/* - * Radix Core API - * - * 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.2.3 - * - * Generated by: https://openapi-generator.tech - */ - -use crate::models; -use serde::{Deserialize, Serialize}; - -#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] -pub struct TransactionPreviewRequestFlags { - /// Whether the virtual signature proofs should be automatically placed in the auth zone. - #[serde(rename = "assume_all_signature_proofs")] - pub assume_all_signature_proofs: bool, - /// Whether to skip the auth checks during execution. This could be used to e.g.: * Preview protocol update style transactions. * Mint resources for previewing trades with resources you don't own. If doing this, be warned: * Only resources which were potentially mintable/burnable at creation time will be mintable/burnable, due to feature flags on the resource. * Please see the below warning about unexpected results if using this approach. Warning: this mode of operation is quite a departure from normal operation: * Calculated fees will likely be lower than a standard execution. * This mode can subtly break invariants some dApp code might rely on, or result in unexpected behaviour, so the resulting execution result might not be valid for your needs. For example, if I used this flag to mint pool units to preview a redemption (or some dApp interaction which behind the scenes redeemed them), they'd redeem for less than they're currently worth, because the blueprint code relies on the total supply of the pool units to calculate their redemption worth, and you've just inflated the total supply through the mint operation. - #[serde(rename = "disable_auth_checks", skip_serializing_if = "Option::is_none")] - pub disable_auth_checks: Option, - /// Whether to skip the epoch range check (i.e. ignoring the `start_epoch_inclusive` and `end_epoch_exclusive` parameters, if specified). Note: effectively, without an epoch range, the Radix Engine cannot perform the *intent hash duplicate* detection, which means that this check will be skipped as well. - #[serde(rename = "skip_epoch_check")] - pub skip_epoch_check: bool, - /// Whether to use a virtual, preview-only pool of XRD to pay for all execution fees. - #[serde(rename = "use_free_credit")] - pub use_free_credit: bool, -} - -impl TransactionPreviewRequestFlags { - pub fn new(assume_all_signature_proofs: bool, skip_epoch_check: bool, use_free_credit: bool) -> TransactionPreviewRequestFlags { - TransactionPreviewRequestFlags { - assume_all_signature_proofs, - disable_auth_checks: None, - skip_epoch_check, - use_free_credit, - } - } -} - diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response.rs index 4e7c244..90dc550 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -23,7 +23,7 @@ pub struct TransactionPreviewResponse { pub instruction_resource_changes: Vec, #[serde(rename = "logs")] pub logs: Vec, - /// An optional field which is only provided if the `request_radix_engine_toolkit_receipt` flag is set to true when requesting a transaction preview from the API. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. + /// An optional field which is only provided if the `radix_engine_toolkit_receipt` flag is set to true when requesting a transaction preview from the API. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. #[serde(rename = "radix_engine_toolkit_receipt", skip_serializing_if = "Option::is_none")] pub radix_engine_toolkit_receipt: Option, #[serde(rename = "receipt")] diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response_logs_inner.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response_logs_inner.rs index f8f8738..8a0248a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response_logs_inner.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response_logs_inner.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response_options.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response_options.rs index 7624c1b..97d4624 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response_options.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_response_options.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_error_details.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_error_details.rs new file mode 100644 index 0000000..b76d084 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_error_details.rs @@ -0,0 +1,27 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Debug, PartialEq, Serialize, Deserialize)] +#[serde(tag = "type")] +pub enum TransactionPreviewV2ErrorDetails { + #[serde(rename="Invalid")] + Invalid(models::InvalidTransactionPreviewV2ErrorDetails), +} + +impl Default for TransactionPreviewV2ErrorDetails { + fn default() -> Self { + Self::Invalid(Default::default()) + } +} + + diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_error_details_type.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_error_details_type.rs new file mode 100644 index 0000000..5c4cc7d --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_error_details_type.rs @@ -0,0 +1,35 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +/// +#[derive(Clone, Copy, Debug, Eq, PartialEq, Ord, PartialOrd, Hash, Serialize, Deserialize)] +pub enum TransactionPreviewV2ErrorDetailsType { + #[serde(rename = "Invalid")] + Invalid, + +} + +impl std::fmt::Display for TransactionPreviewV2ErrorDetailsType { + fn fmt(&self, f: &mut std::fmt::Formatter) -> std::fmt::Result { + match self { + Self::Invalid => write!(f, "Invalid"), + } + } +} + +impl Default for TransactionPreviewV2ErrorDetailsType { + fn default() -> TransactionPreviewV2ErrorDetailsType { + Self::Invalid + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_error_response.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_error_response.rs new file mode 100644 index 0000000..366ed5a --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_error_response.rs @@ -0,0 +1,39 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct TransactionPreviewV2ErrorResponse { + /// A numeric code corresponding to the given HTTP error code. + #[serde(rename = "code")] + pub code: i32, + #[serde(rename = "details", skip_serializing_if = "Option::is_none")] + pub details: Option, + /// A human-readable error message. + #[serde(rename = "message")] + pub message: String, + /// A GUID to be used when reporting errors, to allow correlation with the Core API's error logs, in the case where the Core API details are hidden. + #[serde(rename = "trace_id", skip_serializing_if = "Option::is_none")] + pub trace_id: Option, +} + +impl TransactionPreviewV2ErrorResponse { + pub fn new(code: i32, message: String) -> TransactionPreviewV2ErrorResponse { + TransactionPreviewV2ErrorResponse { + code, + details: None, + message, + trace_id: None, + } + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_request.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_request.rs new file mode 100644 index 0000000..fe0d9ae --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_request.rs @@ -0,0 +1,40 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct TransactionPreviewV2Request { + #[serde(rename = "at_ledger_state", skip_serializing_if = "Option::is_none")] + pub at_ledger_state: Option, + #[serde(rename = "flags", skip_serializing_if = "Option::is_none")] + pub flags: Option, + /// The logical name of the network + #[serde(rename = "network")] + pub network: String, + #[serde(rename = "options", skip_serializing_if = "Option::is_none")] + pub options: Option, + #[serde(rename = "preview_transaction")] + pub preview_transaction: models::PreviewTransaction, +} + +impl TransactionPreviewV2Request { + pub fn new(network: String, preview_transaction: models::PreviewTransaction) -> TransactionPreviewV2Request { + TransactionPreviewV2Request { + at_ledger_state: None, + flags: None, + network, + options: None, + preview_transaction, + } + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_response.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_response.rs new file mode 100644 index 0000000..5d548e4 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_response.rs @@ -0,0 +1,40 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct TransactionPreviewV2Response { + /// A summarized state of the ledger on top of which the preview was performed. + #[serde(rename = "at_ledger_state")] + pub at_ledger_state: models::LedgerStateSummary, + /// An optional field which is only provided if the `logs` flag is set to true in the `options` property of the request. If present, it gives the emitted logs from the transaction execution. + #[serde(rename = "logs", skip_serializing_if = "Option::is_none")] + pub logs: Option>, + /// An optional field which is only provided if the `radix_engine_toolkit_receipt` flag is set to true in the `options` property of the request. This receipt is primarily intended for use with the toolkit and may contain information that is already available in the receipt provided in the `receipt` field of this response. A typical client of this API is not expected to use this receipt. The primary clients this receipt is intended for is the Radix wallet or any client that needs to perform execution summaries on their transactions. + #[serde(rename = "radix_engine_toolkit_receipt", skip_serializing_if = "Option::is_none")] + pub radix_engine_toolkit_receipt: Option, + /// This is provided unless the `core_api_receipt` flag is set to false in the `options` property of the request. + #[serde(rename = "receipt", skip_serializing_if = "Option::is_none")] + pub receipt: Option, +} + +impl TransactionPreviewV2Response { + pub fn new(at_ledger_state: models::LedgerStateSummary) -> TransactionPreviewV2Response { + TransactionPreviewV2Response { + at_ledger_state, + logs: None, + radix_engine_toolkit_receipt: None, + receipt: None, + } + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_response_options.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_response_options.rs new file mode 100644 index 0000000..a35c9f7 --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_preview_v2_response_options.rs @@ -0,0 +1,38 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +/// TransactionPreviewV2ResponseOptions : A set of flags to configure the response of the transaction preview. +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct TransactionPreviewV2ResponseOptions { + /// This flag controls whether the preview response will include a Core API receipt or not. If not provided, this defaults to `false` and no core api receipt is provided in the response. + #[serde(rename = "core_api_receipt", skip_serializing_if = "Option::is_none")] + pub core_api_receipt: Option, + /// This flag controls whether the preview response will include execution logs. If not provided, this defaults to `false` and no logs will be provided in the response. + #[serde(rename = "logs", skip_serializing_if = "Option::is_none")] + pub logs: Option, + /// This flag controls whether the preview response will include a Radix Engine Toolkit serializable receipt or not. If not provided, this defaults to `false` and no toolkit receipt is provided in the response. + #[serde(rename = "radix_engine_toolkit_receipt", skip_serializing_if = "Option::is_none")] + pub radix_engine_toolkit_receipt: Option, +} + +impl TransactionPreviewV2ResponseOptions { + /// A set of flags to configure the response of the transaction preview. + pub fn new() -> TransactionPreviewV2ResponseOptions { + TransactionPreviewV2ResponseOptions { + core_api_receipt: None, + logs: None, + radix_engine_toolkit_receipt: None, + } + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_receipt.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_receipt.rs index b85ec55..f8a69e7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_receipt.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_receipt.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -16,7 +16,7 @@ use serde::{Deserialize, Serialize}; pub struct TransactionReceipt { #[serde(rename = "costing_parameters")] pub costing_parameters: models::CostingParameters, - /// Error message (only present if status is `Failed` or `Rejected`) + /// The error message. This property is only present if the status is `Failed` or `Rejected`. #[serde(rename = "error_message", skip_serializing_if = "Option::is_none")] pub error_message: Option, #[serde(rename = "events", skip_serializing_if = "Option::is_none")] @@ -31,7 +31,7 @@ pub struct TransactionReceipt { pub fee_summary: models::FeeSummary, #[serde(rename = "next_epoch", skip_serializing_if = "Option::is_none")] pub next_epoch: Option, - /// The manifest line-by-line engine return data (only present if `status` is `Succeeded`) + /// The return data for each line of the transaction intent's manifest. This property is only present if the `status` is `Succeeded`. #[serde(rename = "output", skip_serializing_if = "Option::is_none")] pub output: Option>, #[serde(rename = "state_updates")] diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_receipt_request.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_receipt_request.rs index 465ebfd..3a7dd0c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_receipt_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_receipt_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_receipt_response.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_receipt_response.rs index daf4dae..8039b7c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_receipt_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_receipt_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_status.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_status.rs index 2189dcf..ebe24a8 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_status.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_status_request.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_status_request.rs index 7af58c2..8ca668d 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_status_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_status_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_status_response.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_status_response.rs index cd8152b..c8aed2e 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_status_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_status_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_details.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_details.rs index 62b9dfc..0ddf569 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_details_type.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_details_type.rs index ba8e22f..1dceff2 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_details_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_details_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_response.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_response.rs index b146719..6ae2444 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_error_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_intent_already_committed.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_intent_already_committed.rs index e704d04..9ecbfc5 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_intent_already_committed.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_intent_already_committed.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_priority_threshold_not_met_error_details.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_priority_threshold_not_met_error_details.rs index 55f1f2b..19974e4 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_priority_threshold_not_met_error_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_priority_threshold_not_met_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ @@ -13,19 +13,27 @@ use serde::{Deserialize, Serialize}; #[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] pub struct TransactionSubmitPriorityThresholdNotMetErrorDetails { - /// A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. + /// NOTE: This is kept for backwards compatibility, but we recommend using `min_tip_proportion_required` instead. A lower bound for tip percentage at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. #[serde(rename = "min_tip_percentage_required", skip_serializing_if = "Option::is_none")] pub min_tip_percentage_required: Option, - /// Tip percentage of the submitted (and rejected) transaction. + /// A lower bound for tip proportion at current mempool state. Anything lower than this will very likely result in a mempool rejection. A missing value means there is no tip that can guarantee submission. + #[serde(rename = "min_tip_proportion_required", skip_serializing_if = "Option::is_none")] + pub min_tip_proportion_required: Option, + /// NOTE: This is kept for backwards compatibility, but we recommend using `tip_proportion` instead. Tip percentage of the submitted (and rejected) transaction. For V2 transactions specifying basis point tips, the amount is rounded down. #[serde(rename = "tip_percentage")] pub tip_percentage: u32, + /// The string-encoded decimal tip proportion of the submitted (and rejected) transaction. This field will always be present on Cuttlefish nodes, but is marked as not-required for Cuttlefish launch, to avoid a dependency on clients to update after the node is updated. + #[serde(rename = "tip_proportion", skip_serializing_if = "Option::is_none")] + pub tip_proportion: Option, } impl TransactionSubmitPriorityThresholdNotMetErrorDetails { pub fn new(tip_percentage: u32) -> TransactionSubmitPriorityThresholdNotMetErrorDetails { TransactionSubmitPriorityThresholdNotMetErrorDetails { min_tip_percentage_required: None, + min_tip_proportion_required: None, tip_percentage, + tip_proportion: None, } } } diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_rejected_error_details.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_rejected_error_details.rs index c9d35c7..8eb2fc7 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_rejected_error_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_rejected_error_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_request.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_request.rs index ad121ab..63de72a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_response.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_response.rs index bdc85c7..6da7a1c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_submit_response.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_submit_response.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_collection_entry_substate.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_collection_entry_substate.rs index 9d88cb8..fedbecf 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_collection_entry_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_collection_entry_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_collection_entry_value.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_collection_entry_value.rs index c9764c6..351d318 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_collection_entry_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_collection_entry_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_field_state_substate.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_field_state_substate.rs index aeac5ec..a11637a 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_field_state_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_field_state_value.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_field_state_value.rs index bcef329..0f5c76c 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_field_state_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_transaction_status.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_transaction_status.rs index 96c8761..9f57969 100644 --- a/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_transaction_status.rs +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_tracker_transaction_status.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/transaction_validation_config.rs b/generated-clients/core-api-client/sync-client/src/models/transaction_validation_config.rs new file mode 100644 index 0000000..185edbc --- /dev/null +++ b/generated-clients/core-api-client/sync-client/src/models/transaction_validation_config.rs @@ -0,0 +1,74 @@ +/* + * Radix Core API + * + * 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.3.0 + * + * Generated by: https://openapi-generator.tech + */ + +use crate::models; +use serde::{Deserialize, Serialize}; + +#[derive(Clone, Default, Debug, PartialEq, Serialize, Deserialize)] +pub struct TransactionValidationConfig { + #[serde(rename = "manifest_validation")] + pub manifest_validation: models::ManifestValidationRuleset, + #[serde(rename = "max_epoch_range")] + pub max_epoch_range: String, + #[serde(rename = "max_instructions")] + pub max_instructions: String, + #[serde(rename = "max_references_per_intent")] + pub max_references_per_intent: String, + #[serde(rename = "max_signer_signatures_per_intent")] + pub max_signer_signatures_per_intent: String, + #[serde(rename = "max_subintent_depth")] + pub max_subintent_depth: String, + #[serde(rename = "max_tip_basis_points")] + pub max_tip_basis_points: u64, + /// Only applies to V1 transactions + #[serde(rename = "max_tip_percentage")] + pub max_tip_percentage: u32, + #[serde(rename = "max_total_references")] + pub max_total_references: String, + #[serde(rename = "max_total_signature_validations")] + pub max_total_signature_validations: String, + #[serde(rename = "message_validation")] + pub message_validation: models::MessageValidationConfig, + #[serde(rename = "min_tip_basis_points")] + pub min_tip_basis_points: u64, + /// Only applies to V1 transactions + #[serde(rename = "min_tip_percentage")] + pub min_tip_percentage: u32, + #[serde(rename = "preparation_settings")] + pub preparation_settings: models::PreparationSettings, + #[serde(rename = "v1_transactions_allow_notary_to_duplicate_signer")] + pub v1_transactions_allow_notary_to_duplicate_signer: bool, + #[serde(rename = "v2_transactions_allowed")] + pub v2_transactions_allowed: bool, +} + +impl TransactionValidationConfig { + pub fn new(manifest_validation: models::ManifestValidationRuleset, max_epoch_range: String, max_instructions: String, max_references_per_intent: String, max_signer_signatures_per_intent: String, max_subintent_depth: String, max_tip_basis_points: u64, max_tip_percentage: u32, max_total_references: String, max_total_signature_validations: String, message_validation: models::MessageValidationConfig, min_tip_basis_points: u64, min_tip_percentage: u32, preparation_settings: models::PreparationSettings, v1_transactions_allow_notary_to_duplicate_signer: bool, v2_transactions_allowed: bool) -> TransactionValidationConfig { + TransactionValidationConfig { + manifest_validation, + max_epoch_range, + max_instructions, + max_references_per_intent, + max_signer_signatures_per_intent, + max_subintent_depth, + max_tip_basis_points, + max_tip_percentage, + max_total_references, + max_total_signature_validations, + message_validation, + min_tip_basis_points, + min_tip_percentage, + preparation_settings, + v1_transactions_allow_notary_to_duplicate_signer, + v2_transactions_allowed, + } + } +} + diff --git a/generated-clients/core-api-client/sync-client/src/models/two_resource_pool_field_state_substate.rs b/generated-clients/core-api-client/sync-client/src/models/two_resource_pool_field_state_substate.rs index 22b5f51..b27c627 100644 --- a/generated-clients/core-api-client/sync-client/src/models/two_resource_pool_field_state_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/two_resource_pool_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/two_resource_pool_field_state_value.rs b/generated-clients/core-api-client/sync-client/src/models/two_resource_pool_field_state_value.rs index a80e139..6a687ad 100644 --- a/generated-clients/core-api-client/sync-client/src/models/two_resource_pool_field_state_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/two_resource_pool_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/type_info_details.rs b/generated-clients/core-api-client/sync-client/src/models/type_info_details.rs index a49f6d7..95f61a6 100644 --- a/generated-clients/core-api-client/sync-client/src/models/type_info_details.rs +++ b/generated-clients/core-api-client/sync-client/src/models/type_info_details.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/type_info_module_field_type_info_substate.rs b/generated-clients/core-api-client/sync-client/src/models/type_info_module_field_type_info_substate.rs index 13d54e7..1148ba0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/type_info_module_field_type_info_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/type_info_module_field_type_info_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/type_info_module_field_type_info_value.rs b/generated-clients/core-api-client/sync-client/src/models/type_info_module_field_type_info_value.rs index 137056f..f2c63bd 100644 --- a/generated-clients/core-api-client/sync-client/src/models/type_info_module_field_type_info_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/type_info_module_field_type_info_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/type_info_type.rs b/generated-clients/core-api-client/sync-client/src/models/type_info_type.rs index 6327fed..c3d01f5 100644 --- a/generated-clients/core-api-client/sync-client/src/models/type_info_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/type_info_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/updated_substate.rs b/generated-clients/core-api-client/sync-client/src/models/updated_substate.rs index 2c89603..3e87729 100644 --- a/generated-clients/core-api-client/sync-client/src/models/updated_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/updated_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/user_ledger_transaction.rs b/generated-clients/core-api-client/sync-client/src/models/user_ledger_transaction.rs index 8bbac4e..a841d25 100644 --- a/generated-clients/core-api-client/sync-client/src/models/user_ledger_transaction.rs +++ b/generated-clients/core-api-client/sync-client/src/models/user_ledger_transaction.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/user_ledger_transaction_v2.rs b/generated-clients/core-api-client/sync-client/src/models/user_ledger_transaction_v2.rs index a9171f4..b871255 100644 --- a/generated-clients/core-api-client/sync-client/src/models/user_ledger_transaction_v2.rs +++ b/generated-clients/core-api-client/sync-client/src/models/user_ledger_transaction_v2.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/validator_fee_change_request.rs b/generated-clients/core-api-client/sync-client/src/models/validator_fee_change_request.rs index 6312ccf..042ca04 100644 --- a/generated-clients/core-api-client/sync-client/src/models/validator_fee_change_request.rs +++ b/generated-clients/core-api-client/sync-client/src/models/validator_fee_change_request.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/validator_field_protocol_update_readiness_signal_substate.rs b/generated-clients/core-api-client/sync-client/src/models/validator_field_protocol_update_readiness_signal_substate.rs index 89a0bcc..9642c4b 100644 --- a/generated-clients/core-api-client/sync-client/src/models/validator_field_protocol_update_readiness_signal_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/validator_field_protocol_update_readiness_signal_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/validator_field_protocol_update_readiness_signal_value.rs b/generated-clients/core-api-client/sync-client/src/models/validator_field_protocol_update_readiness_signal_value.rs index 68415ef..3c97e20 100644 --- a/generated-clients/core-api-client/sync-client/src/models/validator_field_protocol_update_readiness_signal_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/validator_field_protocol_update_readiness_signal_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/validator_field_state_substate.rs b/generated-clients/core-api-client/sync-client/src/models/validator_field_state_substate.rs index c58c94d..c7d85d3 100644 --- a/generated-clients/core-api-client/sync-client/src/models/validator_field_state_substate.rs +++ b/generated-clients/core-api-client/sync-client/src/models/validator_field_state_substate.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/validator_field_state_value.rs b/generated-clients/core-api-client/sync-client/src/models/validator_field_state_value.rs index c09d08e..bc6f228 100644 --- a/generated-clients/core-api-client/sync-client/src/models/validator_field_state_value.rs +++ b/generated-clients/core-api-client/sync-client/src/models/validator_field_state_value.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/vault_balance.rs b/generated-clients/core-api-client/sync-client/src/models/vault_balance.rs index 33ccb7a..bd83b15 100644 --- a/generated-clients/core-api-client/sync-client/src/models/vault_balance.rs +++ b/generated-clients/core-api-client/sync-client/src/models/vault_balance.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/version_ledger_state_selector.rs b/generated-clients/core-api-client/sync-client/src/models/version_ledger_state_selector.rs index 035e128..6b58e74 100644 --- a/generated-clients/core-api-client/sync-client/src/models/version_ledger_state_selector.rs +++ b/generated-clients/core-api-client/sync-client/src/models/version_ledger_state_selector.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/virtual_lazy_load_schema.rs b/generated-clients/core-api-client/sync-client/src/models/virtual_lazy_load_schema.rs index 7473a9c..1de4f72 100644 --- a/generated-clients/core-api-client/sync-client/src/models/virtual_lazy_load_schema.rs +++ b/generated-clients/core-api-client/sync-client/src/models/virtual_lazy_load_schema.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/generated-clients/core-api-client/sync-client/src/models/vm_type.rs b/generated-clients/core-api-client/sync-client/src/models/vm_type.rs index 5f16ca8..77371a0 100644 --- a/generated-clients/core-api-client/sync-client/src/models/vm_type.rs +++ b/generated-clients/core-api-client/sync-client/src/models/vm_type.rs @@ -3,7 +3,7 @@ * * 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.2.3 + * The version of the OpenAPI document: v1.3.0 * * Generated by: https://openapi-generator.tech */ diff --git a/main.py b/main.py index b6886da..a58ec59 100644 --- a/main.py +++ b/main.py @@ -376,14 +376,16 @@ def generate_crate( os.mkdir(os.path.join(path, package_name, "src")) with open(os.path.join(path, package_name, "src", "lib.rs"), "w") as file: + sync_client_crate_name_underscores = sync_client_crate_name.replace('-', '_') + async_client_crate_name_underscores = async_client_crate_name.replace('-', '_') file.write( '#[cfg(all(feature = "async", feature = "sync"))]\ncompile_error!("features `sync` and `async` are mutually exclusive");\n\n' ) file.write( - f'#[cfg(feature = "sync")]\npub use {sync_client_crate_name.replace('-', '_')}::*;\n' + f'#[cfg(feature = "sync")]\npub use {sync_client_crate_name_underscores}::*;\n' ) file.write( - f'#[cfg(feature = "async")]\npub use {async_client_crate_name.replace('-', '_')}::*;\n' + f'#[cfg(feature = "async")]\npub use {async_client_crate_name_underscores}::*;\n' ) pass @@ -428,7 +430,7 @@ def main(self): ), [ (download_gateway_api_spec, self.gateway_branch), - (download_core_api_spec, self.gateway_branch), + (download_core_api_spec, self.node_branch), ], ), )