diff --git a/.github/workflows/add-artifacts-to-release.yml b/.github/workflows/add-artifacts-to-release.yml index 22f2023c7d..29ef1d8bf7 100644 --- a/.github/workflows/add-artifacts-to-release.yml +++ b/.github/workflows/add-artifacts-to-release.yml @@ -94,7 +94,7 @@ jobs: - name: Build core-rust run: | cd core-rust - cargo build --release --profile=release --target ${{ matrix.target }} + cargo build --release --target ${{ matrix.target }} echo "ls ./target/${{ matrix.target }}/release" ls ./target/${{ matrix.target }}/release/ env: diff --git a/Dockerfile b/Dockerfile index 4ec5e57be9..43e797f91d 100644 --- a/Dockerfile +++ b/Dockerfile @@ -322,4 +322,4 @@ COPY docker/build_scripts/config_radixdlt.sh /opt/radixdlt/config_radixdlt.sh # See https://docs.docker.com/engine/reference/builder/#entrypoint ENTRYPOINT ["/opt/radixdlt/config_radixdlt.sh"] -CMD ["/opt/radixdlt/bin/core"] +CMD ["/opt/radixdlt/bin/core"] \ No newline at end of file diff --git a/core-rust/Cargo.lock b/core-rust/Cargo.lock index 9c1b774564..89bfbc8b67 100644 --- a/core-rust/Cargo.lock +++ b/core-rust/Cargo.lock @@ -150,6 +150,12 @@ version = "0.13.1" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "9e1b586273c5702936fe7b7d6896644d8be71e6314cfe09d3167c95f712589e8" +[[package]] +name = "base64" +version = "0.22.1" +source = "registry+https://github.com/rust-lang/crates.io-index" +checksum = "72b3254f16251a8381aa12e40e3c4d2f0199f8c6508fbecb9d91f575e0fbb8c6" + [[package]] name = "bech32" version = "0.9.1" @@ -376,7 +382,7 @@ checksum = "2674ec482fbc38012cf31e6c42ba0177b431a0cb6f15fe40efa5aab1bda516f6" dependencies = [ "is-terminal", "lazy_static", - "windows-sys 0.48.0", + "windows-sys", ] [[package]] @@ -423,6 +429,7 @@ dependencies = [ "radix-common", "radix-engine", "radix-engine-interface", + "radix-engine-toolkit", "radix-rust", "radix-substate-store-impls", "radix-substate-store-interface", @@ -514,8 +521,18 @@ version = "0.14.4" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "7b750cb3417fd1b327431a470f388520309479ab0bf5e323505daf0290cd3850" dependencies = [ - "darling_core", - "darling_macro", + "darling_core 0.14.4", + "darling_macro 0.14.4", +] + +[[package]] +name = "darling" +version = "0.20.10" +source = "registry+https://github.com/rust-lang/crates.io-index" +checksum = "6f63b86c8a8826a49b8c21f08a2d07338eec8d900540f8630dc76284be802989" +dependencies = [ + "darling_core 0.20.10", + "darling_macro 0.20.10", ] [[package]] @@ -528,21 +545,46 @@ dependencies = [ "ident_case", "proc-macro2", "quote", - "strsim", + "strsim 0.10.0", "syn 1.0.109", ] +[[package]] +name = "darling_core" +version = "0.20.10" +source = "registry+https://github.com/rust-lang/crates.io-index" +checksum = "95133861a8032aaea082871032f5815eb9e98cef03fa916ab4500513994df9e5" +dependencies = [ + "fnv", + "ident_case", + "proc-macro2", + "quote", + "strsim 0.11.1", + "syn 2.0.32", +] + [[package]] name = "darling_macro" version = "0.14.4" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "a4aab4dbc9f7611d8b55048a3a16d2d010c2c8334e46304b40ac1cc14bf3b48e" dependencies = [ - "darling_core", + "darling_core 0.14.4", "quote", "syn 1.0.109", ] +[[package]] +name = "darling_macro" +version = "0.20.10" +source = "registry+https://github.com/rust-lang/crates.io-index" +checksum = "d336a2a514f6ccccaa3e09b02d41d35330c07ddf03a62165fcec10bb561c7806" +dependencies = [ + "darling_core 0.20.10", + "quote", + "syn 2.0.32", +] + [[package]] name = "dashmap" version = "5.5.0" @@ -653,7 +695,7 @@ dependencies = [ "sbor", "serde", "serde_json", - "serde_with", + "serde_with 2.3.0", "state-manager", "tokio", "tower", @@ -669,12 +711,23 @@ checksum = "5443807d6dff69373d433ab9ef5378ad8df50ca6298caf15de6e52e24aaf54d5" [[package]] name = "errno" -version = "0.3.9" +version = "0.3.2" source = "registry+https://github.com/rust-lang/crates.io-index" -checksum = "534c5cf6194dfab3db3242765c03bbe257cf92f22b38f6bc0c58d59108a820ba" +checksum = "6b30f669a7961ef1631673d2766cc92f52d64f7ef354d4fe0ddfd30ed52f0f4f" dependencies = [ + "errno-dragonfly", + "libc", + "windows-sys", +] + +[[package]] +name = "errno-dragonfly" +version = "0.1.2" +source = "registry+https://github.com/rust-lang/crates.io-index" +checksum = "aa68f1b12764fab894d2755d2518754e71b4fd80ecfb822714a1206c2aab39bf" +dependencies = [ + "cc", "libc", - "windows-sys 0.52.0", ] [[package]] @@ -1027,7 +1080,7 @@ checksum = "cb0889898416213fab133e1d33a0e5858a48177452750691bde3666d0fdbaf8b" dependencies = [ "hermit-abi", "rustix", - "windows-sys 0.48.0", + "windows-sys", ] [[package]] @@ -1133,9 +1186,9 @@ checksum = "884e2677b40cc8c339eaefcb701c32ef1fd2493d71118dc0ca4b6a736c93bd67" [[package]] name = "libc" -version = "0.2.155" +version = "0.2.147" source = "registry+https://github.com/rust-lang/crates.io-index" -checksum = "97b3888a4aecf77e811145cadf6eef5901f4782c53886191b2f693f24761847c" +checksum = "b4668fb0ea861c1df094127ac5f1da3409a82116a4ba74fca2e58ef927159bb3" [[package]] name = "libloading" @@ -1182,9 +1235,9 @@ dependencies = [ [[package]] name = "linux-raw-sys" -version = "0.4.14" +version = "0.4.5" source = "registry+https://github.com/rust-lang/crates.io-index" -checksum = "78b3ae25bc7c8c38cec158d1f2757ee79e9b3740fbc7ccf0e59e4b08d793fa89" +checksum = "57bcfdad1b858c2db7c38303a6d2ad4dfaf5eb53dfeb0910128b2c26d6158503" [[package]] name = "lock_api" @@ -1268,7 +1321,7 @@ checksum = "927a765cd3fc26206e66b296465fa9d3e5ab003e651c1b3c060e7956d96b19d2" dependencies = [ "libc", "wasi 0.11.0+wasi-snapshot-preview1", - "windows-sys 0.48.0", + "windows-sys", ] [[package]] @@ -1654,8 +1707,8 @@ dependencies = [ [[package]] name = "radix-blueprint-schema-init" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "bitflags 1.3.2", "radix-common", @@ -1665,8 +1718,8 @@ dependencies = [ [[package]] name = "radix-common" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "bech32", "blake2", @@ -1691,8 +1744,8 @@ dependencies = [ [[package]] name = "radix-common-derive" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "paste", "proc-macro2", @@ -1703,8 +1756,8 @@ dependencies = [ [[package]] name = "radix-engine" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "bitflags 1.3.2", "colored", @@ -1734,8 +1787,8 @@ dependencies = [ [[package]] name = "radix-engine-interface" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "bitflags 1.3.2", "const-sha1", @@ -1755,16 +1808,16 @@ dependencies = [ [[package]] name = "radix-engine-profiling" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "fixedstr", ] [[package]] name = "radix-engine-profiling-derive" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "proc-macro2", "quote", @@ -1772,10 +1825,25 @@ dependencies = [ "syn 1.0.109", ] +[[package]] +name = "radix-engine-toolkit" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" +dependencies = [ + "radix-common", + "radix-engine", + "radix-engine-interface", + "radix-rust", + "radix-substate-store-interface", + "sbor", + "serde", + "serde_with 3.9.0", +] + [[package]] name = "radix-native-sdk" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "radix-common", "radix-engine-interface", @@ -1785,8 +1853,8 @@ dependencies = [ [[package]] name = "radix-rust" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "indexmap 2.2.6", "serde", @@ -1794,8 +1862,8 @@ dependencies = [ [[package]] name = "radix-sbor-derive" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "proc-macro2", "quote", @@ -1805,8 +1873,8 @@ dependencies = [ [[package]] name = "radix-substate-store-impls" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "hex", "itertools", @@ -1819,8 +1887,8 @@ dependencies = [ [[package]] name = "radix-substate-store-interface" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "hex", "itertools", @@ -1831,8 +1899,8 @@ dependencies = [ [[package]] name = "radix-substate-store-queries" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "hex", "itertools", @@ -1848,8 +1916,8 @@ dependencies = [ [[package]] name = "radix-transaction-scenarios" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "hex", "itertools", @@ -1868,8 +1936,8 @@ dependencies = [ [[package]] name = "radix-transactions" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "annotate-snippets", "bech32", @@ -2064,15 +2132,15 @@ dependencies = [ [[package]] name = "rustix" -version = "0.38.34" +version = "0.38.8" source = "registry+https://github.com/rust-lang/crates.io-index" -checksum = "70dc5ec042f7a43c4a73241207cecc9873a06d45debb38b329f8541d85c2730f" +checksum = "19ed4fa021d81c8392ce04db050a3da9a60299050b7ae1cf482d862b54a7218f" dependencies = [ "bitflags 2.4.0", "errno", "libc", "linux-raw-sys", - "windows-sys 0.52.0", + "windows-sys", ] [[package]] @@ -2098,8 +2166,8 @@ dependencies = [ [[package]] name = "sbor" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "const-sha1", "hex", @@ -2112,8 +2180,8 @@ dependencies = [ [[package]] name = "sbor-derive" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "proc-macro2", "sbor-derive-common", @@ -2122,8 +2190,8 @@ dependencies = [ [[package]] name = "sbor-derive-common" -version = "1.3.0-dev" -source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=develop-c02973#c029731f834d0a8093a6371fb595b30c100e58a9" +version = "1.2.0" +source = "git+https://github.com/radixdlt/radixdlt-scrypto?tag=bottlenose-e1f25ed9#e1f25ed9a1e64f720193477504ec46e9850f4ee3" dependencies = [ "const-sha1", "itertools", @@ -2234,13 +2302,31 @@ version = "2.3.0" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "7ea48c9627169d206b35905699f513f513c303ab9d964a59b44fdcf66c1d1ab7" dependencies = [ - "base64", + "base64 0.13.1", + "chrono", + "hex", + "indexmap 1.9.3", + "serde", + "serde_json", + "serde_with_macros 2.3.0", + "time", +] + +[[package]] +name = "serde_with" +version = "3.9.0" +source = "registry+https://github.com/rust-lang/crates.io-index" +checksum = "69cecfa94848272156ea67b2b1a53f20fc7bc638c4a46d2f8abde08f05f4b857" +dependencies = [ + "base64 0.22.1", "chrono", "hex", "indexmap 1.9.3", + "indexmap 2.2.6", "serde", + "serde_derive", "serde_json", - "serde_with_macros", + "serde_with_macros 3.9.0", "time", ] @@ -2250,12 +2336,24 @@ version = "2.3.0" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "9e6b7e52858f9f06c25e1c566bbb4ab428200cb3b30053ea09dc50837de7538b" dependencies = [ - "darling", + "darling 0.14.4", "proc-macro2", "quote", "syn 1.0.109", ] +[[package]] +name = "serde_with_macros" +version = "3.9.0" +source = "registry+https://github.com/rust-lang/crates.io-index" +checksum = "a8fee4991ef4f274617a51ad4af30519438dacb2f56ac773b08a1922ff743350" +dependencies = [ + "darling 0.20.10", + "proc-macro2", + "quote", + "syn 2.0.32", +] + [[package]] name = "sha2" version = "0.9.9" @@ -2375,7 +2473,7 @@ source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "2538b18701741680e0322a2302176d3253a35388e2e62f172f64f4f16605f877" dependencies = [ "libc", - "windows-sys 0.48.0", + "windows-sys", ] [[package]] @@ -2421,6 +2519,12 @@ version = "0.10.0" source = "registry+https://github.com/rust-lang/crates.io-index" checksum = "73473c0e59e6d5812c5dfe2a064a6444949f089e20eec9a2e5506596494e4623" +[[package]] +name = "strsim" +version = "0.11.1" +source = "registry+https://github.com/rust-lang/crates.io-index" +checksum = "7da8b5736845d9f2fcb837ea5d9e2628564b3b043a70948a3f0b778838c5fb4f" + [[package]] name = "strum" version = "0.24.1" @@ -2493,7 +2597,7 @@ dependencies = [ "fastrand", "redox_syscall", "rustix", - "windows-sys 0.48.0", + "windows-sys", ] [[package]] @@ -2595,7 +2699,7 @@ dependencies = [ "signal-hook-registry", "socket2 0.5.3", "tokio-macros", - "windows-sys 0.48.0", + "windows-sys", ] [[package]] @@ -3019,15 +3123,6 @@ dependencies = [ "windows-targets 0.48.5", ] -[[package]] -name = "windows-sys" -version = "0.52.0" -source = "registry+https://github.com/rust-lang/crates.io-index" -checksum = "282be5f36a8ce781fad8c8ae18fa3f9beff57ec1b52cb3de0789201425d9a33d" -dependencies = [ - "windows-targets 0.52.5", -] - [[package]] name = "windows-targets" version = "0.48.5" diff --git a/core-rust/Cargo.toml b/core-rust/Cargo.toml index b8e2e985c5..b3ebb62c76 100644 --- a/core-rust/Cargo.toml +++ b/core-rust/Cargo.toml @@ -23,17 +23,18 @@ resolver = "2" # $ git push origin "release_name-BLAH" # * Then use tag="release_name-BLAH" in the below dependencies. # -sbor = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "develop-c02973", features = ["serde"] } -radix-transactions = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "develop-c02973" } -radix-transaction-scenarios = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "develop-c02973" } -radix-common = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "develop-c02973", features = ["serde"] } -radix-engine-interface = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "develop-c02973" } -radix-engine = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "develop-c02973" } -radix-substate-store-impls = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "develop-c02973" } -radix-substate-store-interface = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "develop-c02973" } -radix-substate-store-queries = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "develop-c02973" } -radix-rust = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "develop-c02973", features = ["serde"] } -radix-blueprint-schema-init = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "develop-c02973", features = ["serde"] } +sbor = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9", features = ["serde"] } +radix-transactions = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9" } +radix-transaction-scenarios = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9" } +radix-common = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9", features = ["serde"] } +radix-engine-interface = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9" } +radix-engine = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9" } +radix-substate-store-impls = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9" } +radix-substate-store-interface = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9" } +radix-substate-store-queries = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9" } +radix-rust = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9", features = ["serde"] } +radix-blueprint-schema-init = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9", features = ["serde"] } +radix-engine-toolkit = { git = "https://github.com/radixdlt/radixdlt-scrypto", tag = "bottlenose-e1f25ed9" } itertools = { version = "=0.10.5" } jni = { version = "=0.19.0" } diff --git a/core-rust/core-api-server/Cargo.toml b/core-rust/core-api-server/Cargo.toml index cebc7e2d8d..a6ff45abd3 100644 --- a/core-rust/core-api-server/Cargo.toml +++ b/core-rust/core-api-server/Cargo.toml @@ -17,6 +17,7 @@ radix-substate-store-interface = { workspace = true } radix-substate-store-queries = { workspace = true } radix-blueprint-schema-init = { workspace = true } radix-rust = { workspace = true } +radix-engine-toolkit = { workspace = true } # Non-Radix Engine Dependencies: jni = { workspace = true } diff --git a/core-rust/core-api-server/core-api-schema.yaml b/core-rust/core-api-server/core-api-schema.yaml index 026c573c67..d73fbf34ed 100644 --- a/core-rust/core-api-server/core-api-schema.yaml +++ b/core-rust/core-api-server/core-api-schema.yaml @@ -53,8 +53,8 @@ openapi: 3.1.0 # => Hex-encoded bytes/payload should end _hex and not include _bytes info: # Should be the release version, and the release display name - version: 'v1.2.1' - title: 'Radix Core API - Babylon (Bottlenose)' + version: 'v1.2.3' + title: 'Radix Core API' license: name: The Radix License, Version 1.0 url: https://www.radixfoundation.org/licenses/license-v1 @@ -7448,6 +7448,9 @@ components: message: description: An optional transaction message. Only affects the costing. $ref: "#/components/schemas/TransactionMessage" + options: + description: A set of flags to configure the response of the transaction preview. + $ref: "#/components/schemas/TransactionPreviewResponseOptions" flags: type: object required: @@ -7492,6 +7495,16 @@ components: 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. type: boolean + TransactionPreviewResponseOptions: + type: object + description: A set of flags to configure the response of the transaction preview. + properties: + radix_engine_toolkit_receipt: + type: boolean + description: | + 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. TransactionPreviewResponse: type: object required: @@ -7506,9 +7519,30 @@ components: description: A summarized state of the ledger on top of which the preview was performed. encoded_receipt: type: string - description: The hex-sbor-encoded receipt + description: | + 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. + deprecated: true receipt: $ref: "#/components/schemas/TransactionReceipt" + radix_engine_toolkit_receipt: + type: object + description: | + 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. instruction_resource_changes: type: array items: diff --git a/core-rust/core-api-server/src/core_api/generated/mod.rs b/core-rust/core-api-server/src/core_api/generated/mod.rs index 645a549a0c..e3ba6c7699 100644 --- a/core-rust/core-api-server/src/core_api/generated/mod.rs +++ b/core-rust/core-api-server/src/core_api/generated/mod.rs @@ -1,2 +1,2 @@ pub mod models; -pub const SCHEMA_VERSION: &str = "v1.2.1"; +pub const SCHEMA_VERSION: &str = "v1.2.3"; diff --git a/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_substate.rs index e578305464..bb9ca8e61c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_substate_all_of.rs index ba33bcad41..67d27d3af1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_value.rs b/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_value.rs index 7625f21863..b292d55531 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/access_controller_field_state_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/access_rule.rs b/core-rust/core-api-server/src/core_api/generated/models/access_rule.rs index 94b48b4fc5..814d1b82e3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/access_rule.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/access_rule.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/access_rule_node.rs b/core-rust/core-api-server/src/core_api/generated/models/access_rule_node.rs index 7588aa21c0..f36b88ca02 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/access_rule_node.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/access_rule_node.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/access_rule_node_type.rs b/core-rust/core-api-server/src/core_api/generated/models/access_rule_node_type.rs index 18516afa00..aca06305bd 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/access_rule_node_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/access_rule_node_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/access_rule_type.rs b/core-rust/core-api-server/src/core_api/generated/models/access_rule_type.rs index 93a18dbd38..b27795a610 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/access_rule_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/access_rule_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_address_key.rs b/core-rust/core-api-server/src/core_api/generated/models/account_address_key.rs index c55127059d..a304e0ef78 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_address_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_address_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_substate.rs index 3ead91d818..62e50caa79 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_substate_all_of.rs index 3efef82d81..18fbe0cb73 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_value.rs index 300128f818..da0e233829 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_authorized_depositor_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_field_state_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/account_field_state_substate.rs index bc83ec63e9..b2735d5094 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_field_state_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_field_state_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_field_state_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/account_field_state_substate_all_of.rs index 6e6b45b55b..ed4e5fba59 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_field_state_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_field_state_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_field_state_value.rs b/core-rust/core-api-server/src/core_api/generated/models/account_field_state_value.rs index 6c80f03218..9f377834fc 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_field_state_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_field_state_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_substate.rs index da252dbe3a..228ac3d5be 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_substate_all_of.rs index 270c5d8311..84e08802bb 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_value.rs index 2af2771769..1faa4358da 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_locker_account_claims_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_substate.rs index c25db56d45..75e572999e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_substate_all_of.rs index ec074f9c7f..d720876fc8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_value.rs index 35c571f3e3..4ac3795ba9 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_resource_preference_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_substate.rs index 9788c970d8..282a6f8c8a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_substate_all_of.rs index ee5c770f65..f87e200a51 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_value.rs index a43c1a3184..47e91cb133 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/account_vault_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/active_validator.rs b/core-rust/core-api-server/src/core_api/generated/models/active_validator.rs index 59eb531011..f7940c3d5d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/active_validator.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/active_validator.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/active_validator_index.rs b/core-rust/core-api-server/src/core_api/generated/models/active_validator_index.rs index 0a5a4e2bd8..23d1cc6ea4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/active_validator_index.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/active_validator_index.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/active_validator_key.rs b/core-rust/core-api-server/src/core_api/generated/models/active_validator_key.rs index 290611b975..26d625a4f9 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/active_validator_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/active_validator_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/address_type.rs b/core-rust/core-api-server/src/core_api/generated/models/address_type.rs index 240ede4245..0a74fdf59a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/address_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/address_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/all_of_access_rule_node.rs b/core-rust/core-api-server/src/core_api/generated/models/all_of_access_rule_node.rs index 038dd38741..dfe119d73d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/all_of_access_rule_node.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/all_of_access_rule_node.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/all_of_proof_rule.rs b/core-rust/core-api-server/src/core_api/generated/models/all_of_proof_rule.rs index 7d4f64f208..398c754296 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/all_of_proof_rule.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/all_of_proof_rule.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/all_of_proof_rule_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/all_of_proof_rule_all_of.rs index 6f818358d3..b36d35f2d4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/all_of_proof_rule_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/all_of_proof_rule_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/allow_all_access_rule.rs b/core-rust/core-api-server/src/core_api/generated/models/allow_all_access_rule.rs index c45fd2bf59..c0d515e62b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/allow_all_access_rule.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/allow_all_access_rule.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/amount_of_proof_rule.rs b/core-rust/core-api-server/src/core_api/generated/models/amount_of_proof_rule.rs index 0c6c022467..995db60b66 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/amount_of_proof_rule.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/amount_of_proof_rule.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/amount_of_proof_rule_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/amount_of_proof_rule_all_of.rs index 232101ad4e..7d4f06a060 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/amount_of_proof_rule_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/amount_of_proof_rule_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/any_of_access_rule_node.rs b/core-rust/core-api-server/src/core_api/generated/models/any_of_access_rule_node.rs index 3099defb63..bca8d1e606 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/any_of_access_rule_node.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/any_of_access_rule_node.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/any_of_access_rule_node_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/any_of_access_rule_node_all_of.rs index 5959ce86bf..11ab66f572 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/any_of_access_rule_node_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/any_of_access_rule_node_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/any_of_proof_rule.rs b/core-rust/core-api-server/src/core_api/generated/models/any_of_proof_rule.rs index a43d0e6129..0000b24825 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/any_of_proof_rule.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/any_of_proof_rule.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/attached_module_id.rs b/core-rust/core-api-server/src/core_api/generated/models/attached_module_id.rs index 9bcc58e7a7..6e8f98cf4a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/attached_module_id.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/attached_module_id.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/auth_config.rs b/core-rust/core-api-server/src/core_api/generated/models/auth_config.rs index 331cdb5a2d..09d3b57dc0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/auth_config.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/auth_config.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_badge.rs b/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_badge.rs index 91ad2bb406..d7ff8fc7cb 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_badge.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_badge.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_badge_type.rs b/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_badge_type.rs index 651dacb7b5..c537fd1f75 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_badge_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_badge_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_key.rs b/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_key.rs index bf8efa59b5..366338fbd6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/authorized_depositor_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/basic_error_response.rs b/core-rust/core-api-server/src/core_api/generated/models/basic_error_response.rs index d305ad07c5..f80b906ddb 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/basic_error_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/basic_error_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/binary_plaintext_message_content.rs b/core-rust/core-api-server/src/core_api/generated/models/binary_plaintext_message_content.rs index df0e9c92a3..9fcb064493 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/binary_plaintext_message_content.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/binary_plaintext_message_content.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/binary_plaintext_message_content_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/binary_plaintext_message_content_all_of.rs index c2e93318a8..9369db6d2b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/binary_plaintext_message_content_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/binary_plaintext_message_content_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_collection_schema.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_collection_schema.rs index 0fad3ada09..5b4c34137a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_collection_schema.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_collection_schema.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_collection_schema_type.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_collection_schema_type.rs index 192c60a44e..1668705bfb 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_collection_schema_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_collection_schema_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_definition.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_definition.rs index de229edb80..f9269bbeba 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_definition.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_definition.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_dependencies.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_dependencies.rs index cf3cfdf9ef..43ad40d0f3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_dependencies.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_dependencies.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_function_target_identifier.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_function_target_identifier.rs index a50305c844..ac2fe8118c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_function_target_identifier.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_function_target_identifier.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_function_target_identifier_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_function_target_identifier_all_of.rs index c0567fc69c..37d670e77a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_function_target_identifier_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_function_target_identifier_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_info.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_info.rs index 2832b1a0b9..d472fae202 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_info.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_info.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_interface.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_interface.rs index 90e115b3e7..6bc174283a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_interface.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_interface.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_method_royalty.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_method_royalty.rs index bf5fc28f01..7e6a519c1c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_method_royalty.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_method_royalty.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_payload_def.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_payload_def.rs index 8a3fa95c23..3be8495978 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_payload_def.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_payload_def.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_payload_def_type.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_payload_def_type.rs index 085936a900..dc8c6477d3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_payload_def_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_payload_def_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_royalty_config.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_royalty_config.rs index 0f520a2ee9..64eb153143 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_royalty_config.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_royalty_config.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_blueprint_type_reference.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_blueprint_type_reference.rs index dde3c89bbb..5e48823cd7 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_blueprint_type_reference.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_blueprint_type_reference.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_blueprint_type_reference_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_blueprint_type_reference_all_of.rs index c933945a4e..2dec781aa8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_blueprint_type_reference_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_blueprint_type_reference_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_collection_partition.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_collection_partition.rs index cc6a7d18ff..534f3621a2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_collection_partition.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_collection_partition.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_field_partition.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_field_partition.rs index bbb849dd94..d0bc25543f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_field_partition.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_schema_field_partition.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_identifier.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_identifier.rs index dacd25105a..5adda141f2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_identifier.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_identifier.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_reference.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_reference.rs index f02536cb67..0faf33624a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_reference.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_reference.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_reference_kind.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_reference_kind.rs index e290c4a14c..15158e96cc 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_reference_kind.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_type_reference_kind.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/blueprint_version_key.rs b/core-rust/core-api-server/src/core_api/generated/models/blueprint_version_key.rs index 9729f34797..aecc0f7773 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/blueprint_version_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/blueprint_version_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_kernel_boot_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_kernel_boot_substate.rs index 4717ac2544..7b17833597 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_kernel_boot_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_kernel_boot_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_kernel_boot_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_kernel_boot_substate_all_of.rs index a2b852aa80..18a8dc9ff4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_kernel_boot_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_kernel_boot_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_substate.rs index 29cfd12d7a..48e41fdfcc 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_substate_all_of.rs index d2aed57698..a47713d611 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_value.rs b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_value.rs index 3f8039557a..636da90a0b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_system_boot_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_substate.rs index d0c0a33419..6408fe702a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_substate_all_of.rs index 3b1463cc5d..62ddb15742 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_value.rs b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_value.rs index 3fd7fcd5e1..0d20348bb8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/boot_loader_module_field_vm_boot_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/committed_intent_metadata.rs b/core-rust/core-api-server/src/core_api/generated/models/committed_intent_metadata.rs index bd9a86d04a..de9b2788ce 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/committed_intent_metadata.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/committed_intent_metadata.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/committed_state_identifier.rs b/core-rust/core-api-server/src/core_api/generated/models/committed_state_identifier.rs index 032a99181f..fe4d88eeb8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/committed_state_identifier.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/committed_state_identifier.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/committed_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/committed_transaction.rs index 7a0a998958..80dbd0fef4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/committed_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/committed_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/committed_transaction_balance_changes.rs b/core-rust/core-api-server/src/core_api/generated/models/committed_transaction_balance_changes.rs index 3773924f76..3d91c2580b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/committed_transaction_balance_changes.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/committed_transaction_balance_changes.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/component_method_target_identifier.rs b/core-rust/core-api-server/src/core_api/generated/models/component_method_target_identifier.rs index 669027e099..8fbde725ee 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/component_method_target_identifier.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/component_method_target_identifier.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/component_method_target_identifier_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/component_method_target_identifier_all_of.rs index bbe03ecf13..7c6d319bc5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/component_method_target_identifier_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/component_method_target_identifier_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_ledger_proof_origin.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_ledger_proof_origin.rs index 7d9c6744a9..47c916b47b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_ledger_proof_origin.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_ledger_proof_origin.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_ledger_proof_origin_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_ledger_proof_origin_all_of.rs index 2c2f0801b6..2fbf1cd271 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_ledger_proof_origin_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_ledger_proof_origin_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_substate.rs index a5f9b18223..5905b44f22 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_substate_all_of.rs index fe9a10164a..5baca173de 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_value.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_value.rs index 105779b8ed..84906283a4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_config_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_substate.rs index 954cd1f05a..6d0365f003 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_substate_all_of.rs index 675fc13b11..d98a6df3fa 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_value.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_value.rs index 33a82ac364..9a79150441 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_proposal_statistic_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs index 2c09e417b1..10d3fbb935 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_substate_all_of.rs index be77533c58..052b323f81 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs index 18fe274ad4..d3cda927a6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_rounded_to_minutes_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_substate.rs index 557e773496..a80f290696 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_substate_all_of.rs index b3a9ecf837..ca366064cd 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_value.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_value.rs index e8061d82a3..9cd29b6161 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_time_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_substate.rs index 88168a5001..779d5d0d70 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_substate_all_of.rs index d21eabcb27..54d2b94c70 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_value.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_value.rs index bfda5aabf3..805387fd25 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_current_validator_set_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_substate.rs index 392da86153..91a9074923 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_substate_all_of.rs index d8f859fe8e..a61b807364 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_value.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_value.rs index faa9c1e7b2..00162426b2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_state_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_substate.rs index 1d686170d1..85b9d57ba2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_substate_all_of.rs index 84eb95e9a5..d35a612bcc 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_value.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_value.rs index d3a0fda5b5..903f558e44 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_field_validator_rewards_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs index fc02edb63c..571320b780 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_substate_all_of.rs index 467bd14469..9d339cf595 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs index b14d0f0229..085ed0ec75 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/consensus_manager_registered_validators_by_stake_index_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/costing_module_config.rs b/core-rust/core-api-server/src/core_api/generated/models/costing_module_config.rs index adeab80e00..3c8af41f56 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/costing_module_config.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/costing_module_config.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/costing_parameters.rs b/core-rust/core-api-server/src/core_api/generated/models/costing_parameters.rs index 0716d9d21b..a35330aa1a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/costing_parameters.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/costing_parameters.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/count_of_proof_rule.rs b/core-rust/core-api-server/src/core_api/generated/models/count_of_proof_rule.rs index bb1541496d..bc9935e533 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/count_of_proof_rule.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/count_of_proof_rule.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/count_of_proof_rule_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/count_of_proof_rule_all_of.rs index 2d4687f881..6a88b53743 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/count_of_proof_rule_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/count_of_proof_rule_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/created_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/created_substate.rs index b32f862fd7..c063d956a3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/created_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/created_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/data_struct.rs b/core-rust/core-api-server/src/core_api/generated/models/data_struct.rs index 2538903aff..033b06b26a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/data_struct.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/data_struct.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/default_deposit_rule.rs b/core-rust/core-api-server/src/core_api/generated/models/default_deposit_rule.rs index da1b3d2098..f8c1c196d2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/default_deposit_rule.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/default_deposit_rule.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/deleted_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/deleted_substate.rs index f083d09757..a5ea42eef3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/deleted_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/deleted_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/deny_all_access_rule.rs b/core-rust/core-api-server/src/core_api/generated/models/deny_all_access_rule.rs index 848f32bb45..cf37606249 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/deny_all_access_rule.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/deny_all_access_rule.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_public_key.rs b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_public_key.rs index 89dc43346e..40f5059ef1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_public_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_public_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_public_key_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_public_key_all_of.rs index e177e3a8c9..004d75e8d2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_public_key_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_public_key_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature.rs b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature.rs index 3d0425079e..281b424702 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_all_of.rs index 8ebca2f2af..8d78034f7d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_with_public_key.rs b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_with_public_key.rs index 1b40bcbfb6..1f86e93e06 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_with_public_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_with_public_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_with_public_key_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_with_public_key_all_of.rs index 81cb579506..ab5f734e51 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_with_public_key_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ecdsa_secp256k1_signature_with_public_key_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_public_key.rs b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_public_key.rs index d8cc1c3767..9b43ced351 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_public_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_public_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_public_key_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_public_key_all_of.rs index eb959d0c07..2315bb3ec6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_public_key_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_public_key_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature.rs b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature.rs index 806f93b084..28d68e8505 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_all_of.rs index f4163d2371..1102ee0ede 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_with_public_key.rs b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_with_public_key.rs index 6aa3d51fe8..2f89678342 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_with_public_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_with_public_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_with_public_key_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_with_public_key_all_of.rs index 45a0c03726..a4ba160e39 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_with_public_key_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/eddsa_ed25519_signature_with_public_key_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/encrypted_message_curve_decryptor_set.rs b/core-rust/core-api-server/src/core_api/generated/models/encrypted_message_curve_decryptor_set.rs index ca57317a09..8a8da8db91 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/encrypted_message_curve_decryptor_set.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/encrypted_message_curve_decryptor_set.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/encrypted_message_decryptor.rs b/core-rust/core-api-server/src/core_api/generated/models/encrypted_message_decryptor.rs index a70e2fa51f..5912ee673b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/encrypted_message_decryptor.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/encrypted_message_decryptor.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/encrypted_transaction_message.rs b/core-rust/core-api-server/src/core_api/generated/models/encrypted_transaction_message.rs index eaf28d1a49..e1246411c5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/encrypted_transaction_message.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/encrypted_transaction_message.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/encrypted_transaction_message_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/encrypted_transaction_message_all_of.rs index 74f5b53c65..1f65ff4348 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/encrypted_transaction_message_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/encrypted_transaction_message_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/entity_module.rs b/core-rust/core-api-server/src/core_api/generated/models/entity_module.rs index 4299f2b040..b9576052b0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/entity_module.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/entity_module.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/entity_reference.rs b/core-rust/core-api-server/src/core_api/generated/models/entity_reference.rs index 6a29fb0dcf..e364d3dd57 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/entity_reference.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/entity_reference.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/entity_type.rs b/core-rust/core-api-server/src/core_api/generated/models/entity_type.rs index 3fd89acc88..13c41a3d1f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/entity_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/entity_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/epoch_change_condition.rs b/core-rust/core-api-server/src/core_api/generated/models/epoch_change_condition.rs index 88ce11272d..ecc8f23eae 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/epoch_change_condition.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/epoch_change_condition.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/epoch_end_ledger_proof.rs b/core-rust/core-api-server/src/core_api/generated/models/epoch_end_ledger_proof.rs index 28166620f2..676b1f78a3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/epoch_end_ledger_proof.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/epoch_end_ledger_proof.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/epoch_round.rs b/core-rust/core-api-server/src/core_api/generated/models/epoch_round.rs index 8ff3e8c79d..49001b30c2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/epoch_round.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/epoch_round.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/error_response.rs b/core-rust/core-api-server/src/core_api/generated/models/error_response.rs index 5bb1dd6388..5c8167fe4b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/error_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/error_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/error_response_type.rs b/core-rust/core-api-server/src/core_api/generated/models/error_response_type.rs index 614397effa..bf51da18e4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/error_response_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/error_response_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/event.rs b/core-rust/core-api-server/src/core_api/generated/models/event.rs index e4d84d80f4..a42f41fe9b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/event.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/event.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/event_emitter_identifier.rs b/core-rust/core-api-server/src/core_api/generated/models/event_emitter_identifier.rs index 725d95b163..b2a6908a31 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/event_emitter_identifier.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/event_emitter_identifier.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/event_emitter_identifier_type.rs b/core-rust/core-api-server/src/core_api/generated/models/event_emitter_identifier_type.rs index 3d4b7be4f8..4cab64b32f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/event_emitter_identifier_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/event_emitter_identifier_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/event_type_identifier.rs b/core-rust/core-api-server/src/core_api/generated/models/event_type_identifier.rs index 42d75703ca..0e2b44d6c9 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/event_type_identifier.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/event_type_identifier.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/executed_scenario.rs b/core-rust/core-api-server/src/core_api/generated/models/executed_scenario.rs index 7af38cc9d9..da59450484 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/executed_scenario.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/executed_scenario.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/executed_scenario_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/executed_scenario_transaction.rs index 6d426fa942..3905399651 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/executed_scenario_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/executed_scenario_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fee_destination.rs b/core-rust/core-api-server/src/core_api/generated/models/fee_destination.rs index 187b91e9fa..b885fc6d0b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fee_destination.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fee_destination.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fee_source.rs b/core-rust/core-api-server/src/core_api/generated/models/fee_source.rs index 8c246b7a0b..f65917d6a8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fee_source.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fee_source.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fee_summary.rs b/core-rust/core-api-server/src/core_api/generated/models/fee_summary.rs index ba3d8b695b..c296626b56 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fee_summary.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fee_summary.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/field_schema.rs b/core-rust/core-api-server/src/core_api/generated/models/field_schema.rs index 567e15e058..e2cfd04aeb 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/field_schema.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/field_schema.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition.rs b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition.rs index b4f9ae2813..3ffaa4a57f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_always.rs b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_always.rs index 742daa42ab..3ba4035c63 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_always.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_always.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_outer_object_feature.rs b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_outer_object_feature.rs index 6a64e5360f..273f987bd3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_outer_object_feature.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_outer_object_feature.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_own_feature.rs b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_own_feature.rs index 81b11a5c43..5435eede38 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_own_feature.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_own_feature.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_own_feature_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_own_feature_all_of.rs index 1e9c342b43..d9defabe60 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_own_feature_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_if_own_feature_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_type.rs b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_type.rs index ae7cb15d07..52a1f0cb85 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/field_schema_feature_condition_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/field_substate_key.rs b/core-rust/core-api-server/src/core_api/generated/models/field_substate_key.rs index a2967c0201..9a5ef5bf1d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/field_substate_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/field_substate_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/field_substate_key_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/field_substate_key_all_of.rs index f4ad226d4e..e72b7cf28d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/field_substate_key_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/field_substate_key_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/flash_ledger_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/flash_ledger_transaction.rs index f616059dcb..240a405d82 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/flash_ledger_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/flash_ledger_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/flash_ledger_transaction_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/flash_ledger_transaction_all_of.rs index 770b9e59f1..669c0b5171 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/flash_ledger_transaction_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/flash_ledger_transaction_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/flash_set_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/flash_set_substate.rs index c4b76d0209..7aa6de37f4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/flash_set_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/flash_set_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/flashed_state_updates.rs b/core-rust/core-api-server/src/core_api/generated/models/flashed_state_updates.rs index 65bf3d3017..84e955704e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/flashed_state_updates.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/flashed_state_updates.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/frozen_status.rs b/core-rust/core-api-server/src/core_api/generated/models/frozen_status.rs index 81ca975092..fc34adffa0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/frozen_status.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/frozen_status.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fully_scoped_type_id.rs b/core-rust/core-api-server/src/core_api/generated/models/fully_scoped_type_id.rs index 3c97dab2ee..3af922763e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fully_scoped_type_id.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fully_scoped_type_id.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/function_auth_type.rs b/core-rust/core-api-server/src/core_api/generated/models/function_auth_type.rs index 2e9f153940..833ff80be1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/function_auth_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/function_auth_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/function_event_emitter_identifier.rs b/core-rust/core-api-server/src/core_api/generated/models/function_event_emitter_identifier.rs index 3082f8f658..4ad2f6e9ae 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/function_event_emitter_identifier.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/function_event_emitter_identifier.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/function_event_emitter_identifier_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/function_event_emitter_identifier_all_of.rs index 0f87345003..5a3e5e4b4b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/function_event_emitter_identifier_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/function_event_emitter_identifier_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/function_schema.rs b/core-rust/core-api-server/src/core_api/generated/models/function_schema.rs index fdee17696d..eebf289f36 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/function_schema.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/function_schema.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_amount.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_amount.rs index 2f1c1316db..a720a50149 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_amount.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_amount.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_amount_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_amount_all_of.rs index 3fe373abf8..033f857924 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_amount_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_amount_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_substate.rs index a9819db435..7c46954fe1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_substate_all_of.rs index f4c318904a..dd82bf6223 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_value.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_value.rs index fceb8b26a1..9f1c8b3846 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_divisibility_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_substate.rs index d733ac577f..f0299198e7 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_substate_all_of.rs index a34d019f86..ccc8fd59d8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_value.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_value.rs index f2f2da7a47..ec9e2e1458 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_resource_manager_field_total_supply_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_substate.rs index 0f80c2e0fd..03a323f981 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_substate_all_of.rs index 81817a8d4e..79d382638d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_value.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_value.rs index fa7509ad6d..9cd7761949 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_balance_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_substate.rs index a10fcecd29..139bfcae4d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_substate_all_of.rs index edd7da5c3f..04baff3f0b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_value.rs b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_value.rs index 07a2078ea3..69e998c201 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/fungible_vault_field_frozen_status_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_blueprint_payload_def.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_blueprint_payload_def.rs index 20d9142bca..2e13e6bddc 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_blueprint_payload_def.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_blueprint_payload_def.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_blueprint_payload_def_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_blueprint_payload_def_all_of.rs index 3df9f7852a..0bc35aabbd 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_blueprint_payload_def_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_blueprint_payload_def_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_key.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_key.rs index 63701611b1..e8170f0207 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_substate.rs index c824b8ce98..47b2326580 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_substate_all_of.rs index 9af689a0ee..7b0d718d5e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_value.rs index 0e8d36ce7d..e7734c7393 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_key_value_store_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_substate.rs index dcc125f2e8..56efc0f038 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_substate_all_of.rs index 72505fd713..c42450269f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_value.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_value.rs index bc996be514..f8257db61d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_scrypto_component_field_state_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_substitution.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_substitution.rs index 7e80761b80..09b6945962 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_substitution.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_substitution.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_substitution_type.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_substitution_type.rs index a1fc3310f3..9f3651e4c8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_substitution_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_substitution_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_type_parameter.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_type_parameter.rs index 6302bcb5bd..e736a8b3c6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_type_parameter.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_type_parameter.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/generic_type_parameter_constraints.rs b/core-rust/core-api-server/src/core_api/generated/models/generic_type_parameter_constraints.rs index d45e8c0771..7c03b7aa17 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/generic_type_parameter_constraints.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/generic_type_parameter_constraints.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_proof_origin.rs b/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_proof_origin.rs index c341463f05..92db249097 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_proof_origin.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_proof_origin.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_proof_origin_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_proof_origin_all_of.rs index a9db347944..0e9c891e92 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_proof_origin_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_proof_origin_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_transaction.rs index 490ad5d128..4a2cec739a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_transaction_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_transaction_all_of.rs index 4d2e6d857a..28d06a56f9 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_transaction_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/genesis_ledger_transaction_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/hook_export.rs b/core-rust/core-api-server/src/core_api/generated/models/hook_export.rs index 1329bac3ba..ac0a60fd32 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/hook_export.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/hook_export.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/index_blueprint_collection_schema.rs b/core-rust/core-api-server/src/core_api/generated/models/index_blueprint_collection_schema.rs index 0e53a17f26..832e15f52a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/index_blueprint_collection_schema.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/index_blueprint_collection_schema.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/index_blueprint_collection_schema_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/index_blueprint_collection_schema_all_of.rs index adcf995ee3..ae8f42fd97 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/index_blueprint_collection_schema_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/index_blueprint_collection_schema_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/indexed_state_schema.rs b/core-rust/core-api-server/src/core_api/generated/models/indexed_state_schema.rs index 29cf3024f4..a9aa72dc4e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/indexed_state_schema.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/indexed_state_schema.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/instance_schema_blueprint_type_reference.rs b/core-rust/core-api-server/src/core_api/generated/models/instance_schema_blueprint_type_reference.rs index 5a3a20b885..9266386199 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/instance_schema_blueprint_type_reference.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/instance_schema_blueprint_type_reference.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/instance_schema_blueprint_type_reference_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/instance_schema_blueprint_type_reference_all_of.rs index 77c68f019a..972e4d54bf 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/instance_schema_blueprint_type_reference_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/instance_schema_blueprint_type_reference_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/instant_ms.rs b/core-rust/core-api-server/src/core_api/generated/models/instant_ms.rs index 96900a3720..f660af684b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/instant_ms.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/instant_ms.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/instruction_resource_changes.rs b/core-rust/core-api-server/src/core_api/generated/models/instruction_resource_changes.rs index b4cda40b7e..7e6789f6d4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/instruction_resource_changes.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/instruction_resource_changes.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/key_value_based_structure.rs b/core-rust/core-api-server/src/core_api/generated/models/key_value_based_structure.rs index 093f14f89a..4c2920b48f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/key_value_based_structure.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/key_value_based_structure.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/key_value_blueprint_collection_schema.rs b/core-rust/core-api-server/src/core_api/generated/models/key_value_blueprint_collection_schema.rs index 4cce02b199..4fb6264ef1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/key_value_blueprint_collection_schema.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/key_value_blueprint_collection_schema.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/key_value_blueprint_collection_schema_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/key_value_blueprint_collection_schema_all_of.rs index 186231ad1b..9b6c66f8c9 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/key_value_blueprint_collection_schema_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/key_value_blueprint_collection_schema_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/key_value_store_entry_structure.rs b/core-rust/core-api-server/src/core_api/generated/models/key_value_store_entry_structure.rs index 8cc3fff305..a359498a6e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/key_value_store_entry_structure.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/key_value_store_entry_structure.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/key_value_store_entry_structure_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/key_value_store_entry_structure_all_of.rs index 2222168cd0..c0d9b6138c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/key_value_store_entry_structure_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/key_value_store_entry_structure_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/key_value_store_info.rs b/core-rust/core-api-server/src/core_api/generated/models/key_value_store_info.rs index 51b927a30b..2c0879a5a0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/key_value_store_info.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/key_value_store_info.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/key_value_store_type_info_details.rs b/core-rust/core-api-server/src/core_api/generated/models/key_value_store_type_info_details.rs index a1d74a697c..e2f935f47f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/key_value_store_type_info_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/key_value_store_type_info_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/key_value_store_type_info_details_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/key_value_store_type_info_details_all_of.rs index f50a8aed33..8870bc3f29 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/key_value_store_type_info_details_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/key_value_store_type_info_details_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/leader_proposal_history.rs b/core-rust/core-api-server/src/core_api/generated/models/leader_proposal_history.rs index 7790f8ecf7..b9755945c2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/leader_proposal_history.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/leader_proposal_history.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ledger_hashes.rs b/core-rust/core-api-server/src/core_api/generated/models/ledger_hashes.rs index 2756d3fd60..5dc86546ff 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ledger_hashes.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ledger_hashes.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ledger_header.rs b/core-rust/core-api-server/src/core_api/generated/models/ledger_header.rs index 4494b8ec13..87fa07a7dd 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ledger_header.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ledger_header.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ledger_header_summary.rs b/core-rust/core-api-server/src/core_api/generated/models/ledger_header_summary.rs index 52aa0a401a..f7aaff7614 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ledger_header_summary.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ledger_header_summary.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ledger_proof.rs b/core-rust/core-api-server/src/core_api/generated/models/ledger_proof.rs index 766356eb48..115bf5b335 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ledger_proof.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ledger_proof.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ledger_proof_origin.rs b/core-rust/core-api-server/src/core_api/generated/models/ledger_proof_origin.rs index a0fd0316f2..742cc252d4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ledger_proof_origin.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ledger_proof_origin.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ledger_proof_origin_type.rs b/core-rust/core-api-server/src/core_api/generated/models/ledger_proof_origin_type.rs index 1c3e165bcd..3ebfcb4bfe 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ledger_proof_origin_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ledger_proof_origin_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ledger_state_selector.rs b/core-rust/core-api-server/src/core_api/generated/models/ledger_state_selector.rs index 00ceed0cfe..8e6f29a3ce 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ledger_state_selector.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ledger_state_selector.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ledger_state_selector_type.rs b/core-rust/core-api-server/src/core_api/generated/models/ledger_state_selector_type.rs index c13a6c6ae8..2764e801b5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ledger_state_selector_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ledger_state_selector_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ledger_state_summary.rs b/core-rust/core-api-server/src/core_api/generated/models/ledger_state_summary.rs index 3f9d899027..5bb1eb1f05 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ledger_state_summary.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ledger_state_summary.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ledger_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/ledger_transaction.rs index e445a9151c..8fdf39a251 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ledger_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ledger_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/ledger_transaction_type.rs b/core-rust/core-api-server/src/core_api/generated/models/ledger_transaction_type.rs index ce838bb405..f0d04d08e6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/ledger_transaction_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/ledger_transaction_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/limit_parameters.rs b/core-rust/core-api-server/src/core_api/generated/models/limit_parameters.rs index 68064ceda2..e8d7a18b73 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/limit_parameters.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/limit_parameters.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/local_generic_substitution.rs b/core-rust/core-api-server/src/core_api/generated/models/local_generic_substitution.rs index c6b02a8c16..9713f87d14 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/local_generic_substitution.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/local_generic_substitution.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/local_generic_substitution_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/local_generic_substitution_all_of.rs index c0240e96b8..c0a5bdd182 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/local_generic_substitution_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/local_generic_substitution_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/local_non_fungible_key.rs b/core-rust/core-api-server/src/core_api/generated/models/local_non_fungible_key.rs index a91455b83b..47d5b0d54c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/local_non_fungible_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/local_non_fungible_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/local_type_id.rs b/core-rust/core-api-server/src/core_api/generated/models/local_type_id.rs index 586190dc39..c812a29c4e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/local_type_id.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/local_type_id.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_committed_transaction_outcome.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_committed_transaction_outcome.rs index 1f2447760a..340fac0202 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_committed_transaction_outcome.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_committed_transaction_outcome.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_committed_transaction_status.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_committed_transaction_status.rs index 53943f7990..938d109d25 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_committed_transaction_status.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_committed_transaction_status.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_entity_fungible_balance_changes.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_entity_fungible_balance_changes.rs index 3de031d2c8..57b3e7f3c0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_entity_fungible_balance_changes.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_entity_fungible_balance_changes.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_entity_non_fungible_balance_changes.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_entity_non_fungible_balance_changes.rs index 2dc47d0417..18c48a5b29 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_entity_non_fungible_balance_changes.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_entity_non_fungible_balance_changes.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_fee_fungible_resource_balance_change.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_fee_fungible_resource_balance_change.rs index 0b3bd37ead..85b492da26 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_fee_fungible_resource_balance_change.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_fee_fungible_resource_balance_change.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_fee_fungible_resource_balance_change_type.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_fee_fungible_resource_balance_change_type.rs index 347e814ebf..2684a76c23 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_fee_fungible_resource_balance_change_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_fee_fungible_resource_balance_change_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_fungible_resource_balance.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_fungible_resource_balance.rs index 7d03256039..3dfbba4b96 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_fungible_resource_balance.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_fungible_resource_balance.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_fungible_resource_balance_change.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_fungible_resource_balance_change.rs index 660187b7f5..0a35761680 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_fungible_resource_balance_change.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_fungible_resource_balance_change.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_resultant_account_fungible_balances.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_resultant_account_fungible_balances.rs index edff904254..98ccfd6271 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_resultant_account_fungible_balances.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_resultant_account_fungible_balances.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_resultant_fungible_balance.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_resultant_fungible_balance.rs index 83aa5cc83e..b4c3e8024f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_resultant_fungible_balance.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_resultant_fungible_balance.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_all_fungible_resource_balances_request.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_all_fungible_resource_balances_request.rs index 3491652cc3..38467205bb 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_all_fungible_resource_balances_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_all_fungible_resource_balances_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_all_fungible_resource_balances_response.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_all_fungible_resource_balances_response.rs index f03d8716e6..e4a8fed443 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_all_fungible_resource_balances_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_all_fungible_resource_balances_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_deposit_behaviour_request.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_deposit_behaviour_request.rs index fdeab47399..f8266db5f2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_deposit_behaviour_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_deposit_behaviour_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_deposit_behaviour_response.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_deposit_behaviour_response.rs index fe2e3e32f8..de9d1a150c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_deposit_behaviour_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_deposit_behaviour_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_fungible_resource_balance_request.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_fungible_resource_balance_request.rs index 8d9b8f3b54..12216ebdd6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_fungible_resource_balance_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_fungible_resource_balance_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_fungible_resource_balance_response.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_fungible_resource_balance_response.rs index 4e2dd0b9be..43343ab09a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_fungible_resource_balance_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_state_account_fungible_resource_balance_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_stream_account_transaction_outcomes_request.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_stream_account_transaction_outcomes_request.rs index 68f821e86f..82a7cb6da8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_stream_account_transaction_outcomes_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_stream_account_transaction_outcomes_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_stream_account_transaction_outcomes_response.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_stream_account_transaction_outcomes_response.rs index 26b322c26c..654a561b8a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_stream_account_transaction_outcomes_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_stream_account_transaction_outcomes_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_stream_transaction_outcomes_request.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_stream_transaction_outcomes_request.rs index 9961b6279c..237a7b94c2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_stream_transaction_outcomes_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_stream_transaction_outcomes_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_stream_transaction_outcomes_response.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_stream_transaction_outcomes_response.rs index 0b8d263be3..aec68bbfc0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_stream_transaction_outcomes_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_stream_transaction_outcomes_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_construction_request.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_construction_request.rs index 9698deab8b..0c5964e2dc 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_construction_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_construction_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_construction_response.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_construction_response.rs index 105e1c6585..902f2fd94b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_construction_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_construction_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_intent_status.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_intent_status.rs index 086049d444..b434a69b9d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_intent_status.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_intent_status.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_payload_details.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_payload_details.rs index 53982b3c3d..db06374160 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_payload_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_payload_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_payload_status.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_payload_status.rs index b15c46c632..80e9638628 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_payload_status.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_payload_status.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_status_request.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_status_request.rs index 9f6fb4898c..82c1597000 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_status_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_status_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_status_response.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_status_response.rs index 3e4f1aaa57..d43a825cf3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_status_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_status_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_details.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_details.rs index b677fe327e..2e2c4da6f4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_details_type.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_details_type.rs index 8459e11ca3..a0069d035c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_details_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_details_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_response.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_response.rs index 22d2a8b185..e6f04f7800 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_response_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_response_all_of.rs index 854c286b40..6dfa2a05aa 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_response_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_error_response_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_intent_already_committed.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_intent_already_committed.rs index 5c269dd760..e82687c73f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_intent_already_committed.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_intent_already_committed.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_intent_already_committed_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_intent_already_committed_all_of.rs index 2c2ef42eaf..a9ee89b72c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_intent_already_committed_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_intent_already_committed_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs index 261c457b59..07e2ed7979 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_priority_threshold_not_met_error_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_priority_threshold_not_met_error_details_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_priority_threshold_not_met_error_details_all_of.rs index 4b2ee0a209..d87f1af982 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_priority_threshold_not_met_error_details_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_priority_threshold_not_met_error_details_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_rejected_error_details.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_rejected_error_details.rs index 9bca7ae3fd..8ec57196b0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_rejected_error_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_rejected_error_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_rejected_error_details_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_rejected_error_details_all_of.rs index 40d37a4c33..6507e8ce3e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_rejected_error_details_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_rejected_error_details_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_request.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_request.rs index 6978d3ccfe..d4e9e6db85 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_response.rs b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_response.rs index 77e9f966d1..67d5f0b9bd 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/lts_transaction_submit_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/main_method_key.rs b/core-rust/core-api-server/src/core_api/generated/models/main_method_key.rs index e8b8f45d9c..e2edfe3b8a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/main_method_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/main_method_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/map_substate_key.rs b/core-rust/core-api-server/src/core_api/generated/models/map_substate_key.rs index 19aac0cc9b..982281d611 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/map_substate_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/map_substate_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/map_substate_key_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/map_substate_key_all_of.rs index 1e89144407..bd6a84e036 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/map_substate_key_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/map_substate_key_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/mempool_list_request.rs b/core-rust/core-api-server/src/core_api/generated/models/mempool_list_request.rs index dcb40d3841..2b80b6b098 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/mempool_list_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/mempool_list_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/mempool_list_response.rs b/core-rust/core-api-server/src/core_api/generated/models/mempool_list_response.rs index 65491c40d7..c7cb1b7184 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/mempool_list_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/mempool_list_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_hashes.rs b/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_hashes.rs index 91f5ff2729..bf323aeea0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_hashes.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_hashes.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_request.rs b/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_request.rs index c2c9658224..f942ac545c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_response.rs b/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_response.rs index aa7ce9c5d9..48eb002387 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_response_payloads_inner.rs b/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_response_payloads_inner.rs index 5f8fce933c..b909a31c4b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_response_payloads_inner.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/mempool_transaction_response_payloads_inner.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/metadata_key.rs b/core-rust/core-api-server/src/core_api/generated/models/metadata_key.rs index e2e89bfca1..6cdbe53eaf 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/metadata_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/metadata_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_substate.rs index ad07155683..92837c448b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_substate_all_of.rs index 3637c14d1e..883b634bdf 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_value.rs index a337fcd29a..03d51e1b8d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/metadata_module_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/method_accessibility.rs b/core-rust/core-api-server/src/core_api/generated/models/method_accessibility.rs index 536c7bd886..a41583e57e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/method_accessibility.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/method_accessibility.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/method_accessibility_type.rs b/core-rust/core-api-server/src/core_api/generated/models/method_accessibility_type.rs index c1667b2a2e..231c05d99c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/method_accessibility_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/method_accessibility_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/method_auth_type.rs b/core-rust/core-api-server/src/core_api/generated/models/method_auth_type.rs index 94b58b8f5a..971f4f5265 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/method_auth_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/method_auth_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/method_event_emitter_identifier.rs b/core-rust/core-api-server/src/core_api/generated/models/method_event_emitter_identifier.rs index 6011bd599b..c220fde3ad 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/method_event_emitter_identifier.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/method_event_emitter_identifier.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/method_event_emitter_identifier_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/method_event_emitter_identifier_all_of.rs index ce92592425..c7025096c1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/method_event_emitter_identifier_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/method_event_emitter_identifier_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/mod.rs b/core-rust/core-api-server/src/core_api/generated/models/mod.rs index 67504dd846..d64fa66925 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/mod.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/mod.rs @@ -1150,6 +1150,8 @@ 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_receipt; pub use self::transaction_receipt::TransactionReceipt; pub mod transaction_receipt_request; diff --git a/core-rust/core-api-server/src/core_api/generated/models/module_id.rs b/core-rust/core-api-server/src/core_api/generated/models/module_id.rs index 29093de2f9..f02d2d73d3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/module_id.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/module_id.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/module_version.rs b/core-rust/core-api-server/src/core_api/generated/models/module_version.rs index 9d433d84cb..1563fd60d1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/module_version.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/module_version.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_substate.rs index 58939e729e..a355f2c77c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_substate_all_of.rs index 29975642f1..2cbbe6ff5c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_value.rs b/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_value.rs index 8f7f9f43fd..37860e75d8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/multi_resource_pool_field_state_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/mutable_field.rs b/core-rust/core-api-server/src/core_api/generated/models/mutable_field.rs index a88be6c79f..050bd58f56 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/mutable_field.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/mutable_field.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response.rs b/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response.rs index 6e4f22eafb..178a8ce11e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response_version.rs b/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response_version.rs index deee2ddd6a..b243745454 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response_version.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response_version.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response_well_known_addresses.rs b/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response_well_known_addresses.rs index b0ae7e25de..c3da220d3b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response_well_known_addresses.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/network_configuration_response_well_known_addresses.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/network_definition.rs b/core-rust/core-api-server/src/core_api/generated/models/network_definition.rs index 4b6ec6640a..737b4c7b95 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/network_definition.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/network_definition.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/network_status_request.rs b/core-rust/core-api-server/src/core_api/generated/models/network_status_request.rs index 95f9ab503c..e6f7406262 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/network_status_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/network_status_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/network_status_response.rs b/core-rust/core-api-server/src/core_api/generated/models/network_status_response.rs index 395f31c187..b8324b605f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/network_status_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/network_status_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/next_epoch.rs b/core-rust/core-api-server/src/core_api/generated/models/next_epoch.rs index 5a9d6eba26..fd30ff9331 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/next_epoch.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/next_epoch.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_authorized_depositor_badge.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_authorized_depositor_badge.rs index 7e7748b53d..1d3d3688a5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_authorized_depositor_badge.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_authorized_depositor_badge.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_authorized_depositor_badge_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_authorized_depositor_badge_all_of.rs index 5a8f8da04c..43032bfeae 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_authorized_depositor_badge_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_authorized_depositor_badge_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_global_id.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_global_id.rs index 8f2115c922..8decc443c1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_global_id.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_global_id.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_id_type.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_id_type.rs index e71fc478c5..54a6cccc32 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_id_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_id_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_local_id.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_local_id.rs index 3f132a0755..3170abeacf 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_local_id.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_local_id.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_presented_badge.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_presented_badge.rs index 48ebed4a31..704ee08493 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_presented_badge.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_presented_badge.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_presented_badge_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_presented_badge_all_of.rs index eb0e93da0d..9567a4954d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_presented_badge_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_presented_badge_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_requirement.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_requirement.rs index 7e0481064b..fd8f641b8d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_requirement.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_requirement.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_requirement_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_requirement_all_of.rs index dc5ed6b929..de3d3bfa5e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_requirement_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_requirement_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_amount.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_amount.rs index c76aed6a5c..a73da2c490 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_amount.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_amount.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_amount_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_amount_all_of.rs index f312269a75..6e3f3d87d9 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_amount_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_amount_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_substate.rs index bf698961ef..0dcaa8429c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_substate_all_of.rs index 0fc09d3932..3a550a8bf1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_value.rs index f0b57a53a0..fc52b07541 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_data_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_substate.rs index e507089569..2dcc9b5ae4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_substate_all_of.rs index f5b555de13..3864249f39 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_value.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_value.rs index 16981ba7a3..8b1849f0c0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_id_type_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_substate.rs index 7a004ff71a..6fdefb7bd0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_substate_all_of.rs index 4d2996b2a1..1d1369a793 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_value.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_value.rs index 3d4f080c0f..8840ee890e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_mutable_fields_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_substate.rs index e6592c91af..58380b18bd 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_substate_all_of.rs index 5b48afbcc1..6f29911e14 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_value.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_value.rs index b74ec1377b..fe028b12e9 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_resource_manager_field_total_supply_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_substate.rs index 14d4698e31..752fa3717f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_substate_all_of.rs index c9e7d63669..761e7b8b04 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_value.rs index 9a45c4257a..97e3f2b2cc 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_contents_index_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_substate.rs index 32d5dac11b..16351d08be 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_substate_all_of.rs index 3ba2bc001b..4b58135c79 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_value.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_value.rs index ac58bece7f..e98d9371d7 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_balance_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_substate.rs index a2967ee01c..063a0c4637 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_substate_all_of.rs index a10566eeab..498be01e44 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_value.rs b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_value.rs index 721b04536f..5884d694aa 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/non_fungible_vault_field_frozen_status_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/notarized_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/notarized_transaction.rs index 9eaa06af15..85736677f8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/notarized_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/notarized_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_field_structure.rs b/core-rust/core-api-server/src/core_api/generated/models/object_field_structure.rs index d8d94dce21..1238aa9b7a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_field_structure.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_field_structure.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_field_structure_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/object_field_structure_all_of.rs index dbd9c5f2bc..d60c1b5b65 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_field_structure_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_field_structure_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_hook.rs b/core-rust/core-api-server/src/core_api/generated/models/object_hook.rs index 5067173103..86e2117869 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_hook.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_hook.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_index_partition_entry_structure.rs b/core-rust/core-api-server/src/core_api/generated/models/object_index_partition_entry_structure.rs index 1dde31bd5d..7662aac3bf 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_index_partition_entry_structure.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_index_partition_entry_structure.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_instance_type_reference.rs b/core-rust/core-api-server/src/core_api/generated/models/object_instance_type_reference.rs index 5e5a5fd841..1bdafabd19 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_instance_type_reference.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_instance_type_reference.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_instance_type_reference_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/object_instance_type_reference_all_of.rs index e2752df106..c1861daa3c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_instance_type_reference_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_instance_type_reference_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_key_value_partition_entry_structure.rs b/core-rust/core-api-server/src/core_api/generated/models/object_key_value_partition_entry_structure.rs index eca7015e83..d52293a8ff 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_key_value_partition_entry_structure.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_key_value_partition_entry_structure.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_role_key.rs b/core-rust/core-api-server/src/core_api/generated/models/object_role_key.rs index 34ba389a93..b5635d0084 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_role_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_role_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_sorted_index_partition_entry_structure.rs b/core-rust/core-api-server/src/core_api/generated/models/object_sorted_index_partition_entry_structure.rs index 056e9a29a8..a92f329d59 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_sorted_index_partition_entry_structure.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_sorted_index_partition_entry_structure.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_substate_type_reference.rs b/core-rust/core-api-server/src/core_api/generated/models/object_substate_type_reference.rs index e4abb54c5f..45a526709f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_substate_type_reference.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_substate_type_reference.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_substate_type_reference_type.rs b/core-rust/core-api-server/src/core_api/generated/models/object_substate_type_reference_type.rs index a9f6c424d9..1285b22483 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_substate_type_reference_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_substate_type_reference_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_type_info_details.rs b/core-rust/core-api-server/src/core_api/generated/models/object_type_info_details.rs index 2e57f9a042..1a3156fc4d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_type_info_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_type_info_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/object_type_info_details_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/object_type_info_details_all_of.rs index 32a76d1c44..41290d506f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/object_type_info_details_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/object_type_info_details_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_substate.rs index c48f84622d..eedbc9df8b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_substate_all_of.rs index 460e7696a9..d274d49760 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_value.rs b/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_value.rs index 8ed4e50298..9c5b14fd3e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/one_resource_pool_field_state_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/outer_object_only_method_accessibility.rs b/core-rust/core-api-server/src/core_api/generated/models/outer_object_only_method_accessibility.rs index 0bb6307b24..693b715a5f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/outer_object_only_method_accessibility.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/outer_object_only_method_accessibility.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/own_package_only_method_accessibility.rs b/core-rust/core-api-server/src/core_api/generated/models/own_package_only_method_accessibility.rs index c015181628..a40d33c613 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/own_package_only_method_accessibility.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/own_package_only_method_accessibility.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/owner_role.rs b/core-rust/core-api-server/src/core_api/generated/models/owner_role.rs index 0fd6de66de..ca25a02923 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/owner_role.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/owner_role.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/owner_role_updater.rs b/core-rust/core-api-server/src/core_api/generated/models/owner_role_updater.rs index 4e2315dd20..5cd0a13ee2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/owner_role_updater.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/owner_role_updater.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_substate.rs index 28ebbe2458..55ae5d4395 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_substate_all_of.rs index 5c5fd70e38..c4bf50b1b3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_value.rs index 18756e3504..d071ec6d20 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_auth_template_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_substate.rs index c7414e6406..4a0c61c9fc 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_substate_all_of.rs index d4c17b0396..6d3ff85b11 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_value.rs index 3ef9389ded..08e1e0c55b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_definition_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_substate.rs index 6998b77063..34cfcc41ed 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_substate_all_of.rs index 1fe8beda65..b5f297c2e4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_value.rs index 9fbffe6f1b..3de07a7cb3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_dependencies_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_substate.rs index a19ee87ad1..87398cc2a6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_substate_all_of.rs index 58b69f8778..8de93f4a05 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_value.rs index e036b00b71..f5d8d88b72 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_blueprint_royalty_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_substate.rs index 833326a653..dbb4ff9f1e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_substate_all_of.rs index 40cfb184fa..81f85565a1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_value.rs index 45a27e181a..7566162c64 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_code_instrumented_code_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_code_key.rs b/core-rust/core-api-server/src/core_api/generated/models/package_code_key.rs index 80549fd4d1..c13e998f07 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_code_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_code_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_substate.rs index 776ec1b899..f3176f9b9c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_substate_all_of.rs index 0a051db472..d3c55a9246 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_value.rs index f02ddbc921..b83a3bd450 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_code_original_code_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_substate.rs index 825e0478f9..13ca0d0cd1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_substate_all_of.rs index ddf788e392..e1db153c1d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_value.rs index 617ef0a040..bbbb76760f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_code_vm_type_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_export.rs b/core-rust/core-api-server/src/core_api/generated/models/package_export.rs index 41dbf542a1..4f18516f76 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_export.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_export.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_substate.rs index 3f19b515f6..d331e08be6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_substate_all_of.rs index 1004416f92..f6a0d66e37 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_value.rs b/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_value.rs index 330aa558ac..34ca64e946 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_field_royalty_accumulator_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_object_substate_type_reference.rs b/core-rust/core-api-server/src/core_api/generated/models/package_object_substate_type_reference.rs index c4a75c5112..5197c000fa 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_object_substate_type_reference.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_object_substate_type_reference.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/package_type_reference.rs b/core-rust/core-api-server/src/core_api/generated/models/package_type_reference.rs index f6a377582c..2e95c1faa5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/package_type_reference.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/package_type_reference.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction.rs index e43db2dcc7..b54ea4d903 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction_all_of.rs index 1f554239c4..4d53f92837 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction_identifiers.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction_identifiers.rs index ff072f6db5..91283865ae 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction_identifiers.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_ledger_transaction_identifiers.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction.rs index 1406cc34db..75623d4250 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_all_of.rs index eb51708809..95755fc347 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_all_of_validation_error.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_all_of_validation_error.rs index 316bc9f5fa..f47cda2488 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_all_of_validation_error.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_all_of_validation_error.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_identifiers.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_identifiers.rs index ea24993215..20bc7fe56d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_identifiers.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_notarized_transaction_identifiers.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent.rs index 2fa8d069c6..a0841f2479 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent_all_of.rs index 3265e8e76b..c7a5bf8546 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent_identifiers.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent_identifiers.rs index d1cc438dc3..60ed465b48 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent_identifiers.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_signed_transaction_intent_identifiers.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction.rs index f9996d9b64..b233a4027b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent.rs index 7cca579644..87088559f5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent_all_of.rs index 69b6cadb47..4f2e0daa47 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent_identifiers.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent_identifiers.rs index e354f596fb..297b521b41 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent_identifiers.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_intent_identifiers.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_type.rs b/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_type.rs index 455cd5a94b..e7fd3cb98c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/parsed_transaction_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/partition_description.rs b/core-rust/core-api-server/src/core_api/generated/models/partition_description.rs index f04c98fad6..b3cf300e94 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/partition_description.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/partition_description.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/partition_description_type.rs b/core-rust/core-api-server/src/core_api/generated/models/partition_description_type.rs index 1f7dba101d..ee94ec5a07 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/partition_description_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/partition_description_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/partition_id.rs b/core-rust/core-api-server/src/core_api/generated/models/partition_id.rs index ddc4f2c831..253f8a0266 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/partition_id.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/partition_id.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/partition_kind.rs b/core-rust/core-api-server/src/core_api/generated/models/partition_kind.rs index a60e6f6dbe..3f0577e56d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/partition_kind.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/partition_kind.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/payment_from_vault.rs b/core-rust/core-api-server/src/core_api/generated/models/payment_from_vault.rs index 8c524b1641..d3623feb94 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/payment_from_vault.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/payment_from_vault.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/payment_to_royalty_recipient.rs b/core-rust/core-api-server/src/core_api/generated/models/payment_to_royalty_recipient.rs index 65ee26f0f3..5dea17b7bb 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/payment_to_royalty_recipient.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/payment_to_royalty_recipient.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/pending_owner_stake_withdrawal.rs b/core-rust/core-api-server/src/core_api/generated/models/pending_owner_stake_withdrawal.rs index e5f1c2b04c..0b4e8ec246 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/pending_owner_stake_withdrawal.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/pending_owner_stake_withdrawal.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/plaintext_message_content.rs b/core-rust/core-api-server/src/core_api/generated/models/plaintext_message_content.rs index 7d1501e3e6..24a8ab7eed 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/plaintext_message_content.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/plaintext_message_content.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/plaintext_message_content_type.rs b/core-rust/core-api-server/src/core_api/generated/models/plaintext_message_content_type.rs index c4222daf17..d2b0f15d79 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/plaintext_message_content_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/plaintext_message_content_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/plaintext_transaction_message.rs b/core-rust/core-api-server/src/core_api/generated/models/plaintext_transaction_message.rs index d2052a1ad2..56d05ec471 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/plaintext_transaction_message.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/plaintext_transaction_message.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/plaintext_transaction_message_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/plaintext_transaction_message_all_of.rs index dfa8ffed83..7a074e58e5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/plaintext_transaction_message_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/plaintext_transaction_message_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/pool_vault.rs b/core-rust/core-api-server/src/core_api/generated/models/pool_vault.rs index 7066811ba4..ff270b1530 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/pool_vault.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/pool_vault.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/presented_badge.rs b/core-rust/core-api-server/src/core_api/generated/models/presented_badge.rs index fa6b3eb722..638d6be212 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/presented_badge.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/presented_badge.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/presented_badge_type.rs b/core-rust/core-api-server/src/core_api/generated/models/presented_badge_type.rs index a58abc42d3..5f376c43f9 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/presented_badge_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/presented_badge_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/primary_role_recovery_attempt.rs b/core-rust/core-api-server/src/core_api/generated/models/primary_role_recovery_attempt.rs index 5c8097562f..f1a46c07d4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/primary_role_recovery_attempt.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/primary_role_recovery_attempt.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/proof_access_rule_node.rs b/core-rust/core-api-server/src/core_api/generated/models/proof_access_rule_node.rs index 23f9bce5e7..0727822918 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/proof_access_rule_node.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/proof_access_rule_node.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/proof_access_rule_node_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/proof_access_rule_node_all_of.rs index eede4ce7cb..0b959286d6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/proof_access_rule_node_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/proof_access_rule_node_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/proof_rule.rs b/core-rust/core-api-server/src/core_api/generated/models/proof_rule.rs index ba59979525..96670f57bf 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/proof_rule.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/proof_rule.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/proof_rule_type.rs b/core-rust/core-api-server/src/core_api/generated/models/proof_rule_type.rs index 63e6fb6342..24f77afa2a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/proof_rule_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/proof_rule_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/proposer_reward.rs b/core-rust/core-api-server/src/core_api/generated/models/proposer_reward.rs index 7efe260b28..29f572d622 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/proposer_reward.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/proposer_reward.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/protected_access_rule.rs b/core-rust/core-api-server/src/core_api/generated/models/protected_access_rule.rs index c1ce44e566..0c0b28099f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/protected_access_rule.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/protected_access_rule.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/protected_access_rule_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/protected_access_rule_all_of.rs index db9465c805..5d99d023e0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/protected_access_rule_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/protected_access_rule_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/protocol_update_ledger_proof_origin.rs b/core-rust/core-api-server/src/core_api/generated/models/protocol_update_ledger_proof_origin.rs index ed31a08d47..c2407fbe63 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/protocol_update_ledger_proof_origin.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/protocol_update_ledger_proof_origin.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/protocol_update_ledger_proof_origin_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/protocol_update_ledger_proof_origin_all_of.rs index 3bb81f93f3..4593a8d512 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/protocol_update_ledger_proof_origin_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/protocol_update_ledger_proof_origin_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/protocol_version_readiness.rs b/core-rust/core-api-server/src/core_api/generated/models/protocol_version_readiness.rs index 4f63085139..138e4eae39 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/protocol_version_readiness.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/protocol_version_readiness.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/public_key.rs b/core-rust/core-api-server/src/core_api/generated/models/public_key.rs index 7b94e5d143..b6cd551248 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/public_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/public_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/public_key_type.rs b/core-rust/core-api-server/src/core_api/generated/models/public_key_type.rs index a23d992286..0076bd810d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/public_key_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/public_key_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/public_method_accessibility.rs b/core-rust/core-api-server/src/core_api/generated/models/public_method_accessibility.rs index 877ed9c0e6..98c612445d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/public_method_accessibility.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/public_method_accessibility.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/receiver_info.rs b/core-rust/core-api-server/src/core_api/generated/models/receiver_info.rs index 0234c9a36f..0b1b1e3dc3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/receiver_info.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/receiver_info.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/recovery_proposal.rs b/core-rust/core-api-server/src/core_api/generated/models/recovery_proposal.rs index 2634535f18..02c5ec5825 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/recovery_proposal.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/recovery_proposal.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/recovery_role_recovery_attempt.rs b/core-rust/core-api-server/src/core_api/generated/models/recovery_role_recovery_attempt.rs index 1cc0c4fbd9..b37f396a2f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/recovery_role_recovery_attempt.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/recovery_role_recovery_attempt.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/reference_type.rs b/core-rust/core-api-server/src/core_api/generated/models/reference_type.rs index 3bbaf06a19..aa57618e07 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/reference_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/reference_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/remote_generic_substitution.rs b/core-rust/core-api-server/src/core_api/generated/models/remote_generic_substitution.rs index 30e2e6fc23..2bb8f466bb 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/remote_generic_substitution.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/remote_generic_substitution.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/remote_generic_substitution_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/remote_generic_substitution_all_of.rs index b309af25a3..aa9b487aef 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/remote_generic_substitution_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/remote_generic_substitution_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/requested_state_version_out_of_bounds_error_details.rs b/core-rust/core-api-server/src/core_api/generated/models/requested_state_version_out_of_bounds_error_details.rs index 0df6dc7f9d..4de5f4fabc 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/requested_state_version_out_of_bounds_error_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/requested_state_version_out_of_bounds_error_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/require_proof_rule.rs b/core-rust/core-api-server/src/core_api/generated/models/require_proof_rule.rs index eda9d776c7..131eec477e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/require_proof_rule.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/require_proof_rule.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/require_proof_rule_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/require_proof_rule_all_of.rs index d50f2b02ab..e61458c82b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/require_proof_rule_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/require_proof_rule_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/requirement.rs b/core-rust/core-api-server/src/core_api/generated/models/requirement.rs index ac7b4000ca..63694df48d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/requirement.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/requirement.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/requirement_type.rs b/core-rust/core-api-server/src/core_api/generated/models/requirement_type.rs index d88bb5cf3a..893c088e90 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/requirement_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/requirement_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/resource_amount.rs b/core-rust/core-api-server/src/core_api/generated/models/resource_amount.rs index 8b8a3bc13f..fd4e0d5b25 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/resource_amount.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/resource_amount.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/resource_authorized_depositor_badge.rs b/core-rust/core-api-server/src/core_api/generated/models/resource_authorized_depositor_badge.rs index 1f11f4d33c..843cbee2b8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/resource_authorized_depositor_badge.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/resource_authorized_depositor_badge.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/resource_authorized_depositor_badge_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/resource_authorized_depositor_badge_all_of.rs index c60eebb295..ca752d8095 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/resource_authorized_depositor_badge_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/resource_authorized_depositor_badge_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/resource_change.rs b/core-rust/core-api-server/src/core_api/generated/models/resource_change.rs index 43b2aa16b5..b07f17829a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/resource_change.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/resource_change.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/resource_key.rs b/core-rust/core-api-server/src/core_api/generated/models/resource_key.rs index b66e7844ab..7841164b60 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/resource_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/resource_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/resource_preference.rs b/core-rust/core-api-server/src/core_api/generated/models/resource_preference.rs index f112063b76..f7666d69de 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/resource_preference.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/resource_preference.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/resource_presented_badge.rs b/core-rust/core-api-server/src/core_api/generated/models/resource_presented_badge.rs index 3e6d930517..4a69edbc7a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/resource_presented_badge.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/resource_presented_badge.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/resource_requirement.rs b/core-rust/core-api-server/src/core_api/generated/models/resource_requirement.rs index 037be95bca..327ca26136 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/resource_requirement.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/resource_requirement.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/resource_requirement_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/resource_requirement_all_of.rs index 37c9da6e9d..7bd7f96b3d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/resource_requirement_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/resource_requirement_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/resource_specific_deposit_behaviour.rs b/core-rust/core-api-server/src/core_api/generated/models/resource_specific_deposit_behaviour.rs index 55dab0fd3a..f2fe646acc 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/resource_specific_deposit_behaviour.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/resource_specific_deposit_behaviour.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/resource_type.rs b/core-rust/core-api-server/src/core_api/generated/models/resource_type.rs index 85e3cac2aa..09501acbd6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/resource_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/resource_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_substate.rs index c5785d1c55..3a4c0c0644 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_substate_all_of.rs index c4358e4ce3..ed98ba035c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_value.rs b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_value.rs index 956e6cdd08..9b54745c22 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_field_owner_role_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_substate.rs index b69a52daa0..d68d908989 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_substate_all_of.rs index 887b216238..66c88eb3f1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_value.rs index e5c0361e34..e3666d9b4b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/role_assignment_module_rule_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/role_details.rs b/core-rust/core-api-server/src/core_api/generated/models/role_details.rs index fff94649e9..d7c497d393 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/role_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/role_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/role_protected_method_accessibility.rs b/core-rust/core-api-server/src/core_api/generated/models/role_protected_method_accessibility.rs index d4976ee368..05730821ce 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/role_protected_method_accessibility.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/role_protected_method_accessibility.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/role_protected_method_accessibility_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/role_protected_method_accessibility_all_of.rs index a19930816f..ca88e63050 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/role_protected_method_accessibility_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/role_protected_method_accessibility_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/role_specification.rs b/core-rust/core-api-server/src/core_api/generated/models/role_specification.rs index 1ab4c581e7..f6953873e1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/role_specification.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/role_specification.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/round_update_ledger_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/round_update_ledger_transaction.rs index ee1d27b542..ef643686ba 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/round_update_ledger_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/round_update_ledger_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/round_update_ledger_transaction_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/round_update_ledger_transaction_all_of.rs index c784217e0b..3cda34b6e0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/round_update_ledger_transaction_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/round_update_ledger_transaction_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/round_update_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/round_update_transaction.rs index f14f8c5e96..d56529f99e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/round_update_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/round_update_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/royalty_amount.rs b/core-rust/core-api-server/src/core_api/generated/models/royalty_amount.rs index ccae731b05..fc7fc073f7 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/royalty_amount.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/royalty_amount.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_substate.rs index 2a62c8b4a1..763dd2b942 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_substate_all_of.rs index 0bb6d2e26a..f1260cfea0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_value.rs b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_value.rs index 6bc2e34c3e..9da7b6e56f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_field_state_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_substate.rs index 00ac8c9d6f..5a8b993ce3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_substate_all_of.rs index 16aa7b9eee..7a0f1eb796 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_value.rs index 65a1e50c9e..405f8bde57 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/royalty_module_method_royalty_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/sbor_data.rs b/core-rust/core-api-server/src/core_api/generated/models/sbor_data.rs index ac24e10c90..7d31857cdc 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/sbor_data.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/sbor_data.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/sbor_format_options.rs b/core-rust/core-api-server/src/core_api/generated/models/sbor_format_options.rs index 47b8024891..776b0821ab 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/sbor_format_options.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/sbor_format_options.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/scenarios_request.rs b/core-rust/core-api-server/src/core_api/generated/models/scenarios_request.rs index be9b86d373..0d8231499f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/scenarios_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/scenarios_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/scenarios_response.rs b/core-rust/core-api-server/src/core_api/generated/models/scenarios_response.rs index 3d34c506c6..8095b72490 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/scenarios_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/scenarios_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/schema_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/schema_entry_substate.rs index 7e18f1cd15..bcfe2c7442 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/schema_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/schema_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/schema_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/schema_entry_substate_all_of.rs index 3d5b7fab28..e1e96e04e1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/schema_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/schema_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/schema_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/schema_entry_value.rs index eed15e53b9..673059a6c8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/schema_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/schema_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/schema_key.rs b/core-rust/core-api-server/src/core_api/generated/models/schema_key.rs index 0afc4cdcad..4ab6dd2078 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/schema_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/schema_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/scoped_type_id.rs b/core-rust/core-api-server/src/core_api/generated/models/scoped_type_id.rs index 93ef4493a2..2eb18304bf 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/scoped_type_id.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/scoped_type_id.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/scrypto_instant.rs b/core-rust/core-api-server/src/core_api/generated/models/scrypto_instant.rs index 7c5e6c4865..ac38afec83 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/scrypto_instant.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/scrypto_instant.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/scrypto_schema.rs b/core-rust/core-api-server/src/core_api/generated/models/scrypto_schema.rs index 3a8ea59ac8..628bfde400 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/scrypto_schema.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/scrypto_schema.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/signalling_validator.rs b/core-rust/core-api-server/src/core_api/generated/models/signalling_validator.rs index 465ba1f626..cde33efa06 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/signalling_validator.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/signalling_validator.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/signature.rs b/core-rust/core-api-server/src/core_api/generated/models/signature.rs index 2deab1907a..ea56a366ab 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/signature.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/signature.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/signature_with_public_key.rs b/core-rust/core-api-server/src/core_api/generated/models/signature_with_public_key.rs index b5d652e98a..7b8bc5b771 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/signature_with_public_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/signature_with_public_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/signed_transaction_intent.rs b/core-rust/core-api-server/src/core_api/generated/models/signed_transaction_intent.rs index 6f086b05b7..17ff877c4a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/signed_transaction_intent.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/signed_transaction_intent.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/significant_protocol_update_readiness_entry.rs b/core-rust/core-api-server/src/core_api/generated/models/significant_protocol_update_readiness_entry.rs index 3ceb7decd9..f3252c6591 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/significant_protocol_update_readiness_entry.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/significant_protocol_update_readiness_entry.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/sorted_index_blueprint_collection_schema.rs b/core-rust/core-api-server/src/core_api/generated/models/sorted_index_blueprint_collection_schema.rs index e98ec38d56..2477d48577 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/sorted_index_blueprint_collection_schema.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/sorted_index_blueprint_collection_schema.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/sorted_index_blueprint_collection_schema_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/sorted_index_blueprint_collection_schema_all_of.rs index aae3de4d32..9da762de4e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/sorted_index_blueprint_collection_schema_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/sorted_index_blueprint_collection_schema_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/sorted_substate_key.rs b/core-rust/core-api-server/src/core_api/generated/models/sorted_substate_key.rs index aabb6ff9d8..a7aea9269a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/sorted_substate_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/sorted_substate_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/sorted_substate_key_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/sorted_substate_key_all_of.rs index 0e6ade87c2..0f116d12aa 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/sorted_substate_key_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/sorted_substate_key_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_access_controller_request.rs b/core-rust/core-api-server/src/core_api/generated/models/state_access_controller_request.rs index d4da45db8d..9db11878af 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_access_controller_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_access_controller_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_access_controller_response.rs b/core-rust/core-api-server/src/core_api/generated/models/state_access_controller_response.rs index 5b2c6b3fe3..c17ed1bec7 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_access_controller_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_access_controller_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_account_request.rs b/core-rust/core-api-server/src/core_api/generated/models/state_account_request.rs index 0b8119312c..3feaeaf246 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_account_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_account_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_account_response.rs b/core-rust/core-api-server/src/core_api/generated/models/state_account_response.rs index db053e5ecb..fc4a3f6eb2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_account_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_account_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_component_descendent_node.rs b/core-rust/core-api-server/src/core_api/generated/models/state_component_descendent_node.rs index b1efca7e8b..735c72b14a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_component_descendent_node.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_component_descendent_node.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_component_request.rs b/core-rust/core-api-server/src/core_api/generated/models/state_component_request.rs index ea81cdd5ba..fa655b0bae 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_component_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_component_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_component_response.rs b/core-rust/core-api-server/src/core_api/generated/models/state_component_response.rs index 037b7ce770..f7fba8bb2b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_component_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_component_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_consensus_manager_request.rs b/core-rust/core-api-server/src/core_api/generated/models/state_consensus_manager_request.rs index 92461678ec..83965ea508 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_consensus_manager_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_consensus_manager_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_consensus_manager_response.rs b/core-rust/core-api-server/src/core_api/generated/models/state_consensus_manager_response.rs index 2e78442d01..27b2c955b1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_consensus_manager_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_consensus_manager_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_fungible_resource_manager.rs b/core-rust/core-api-server/src/core_api/generated/models/state_fungible_resource_manager.rs index 73efa54aba..d720605fcf 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_fungible_resource_manager.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_fungible_resource_manager.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_fungible_resource_manager_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/state_fungible_resource_manager_all_of.rs index 220eaaa8c6..28ae26526f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_fungible_resource_manager_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_fungible_resource_manager_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_request.rs b/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_request.rs index 886aae2293..512fa04a33 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_resource_manager.rs b/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_resource_manager.rs index 13bb823454..3aa01d92d0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_resource_manager.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_resource_manager.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_resource_manager_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_resource_manager_all_of.rs index b6feb1843c..5ddd124273 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_resource_manager_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_resource_manager_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_response.rs b/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_response.rs index 484da67219..d87354255d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_non_fungible_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_package_request.rs b/core-rust/core-api-server/src/core_api/generated/models/state_package_request.rs index 2ba8514a0e..56fa6af194 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_package_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_package_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_package_response.rs b/core-rust/core-api-server/src/core_api/generated/models/state_package_response.rs index be44e78d3c..5b1525af74 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_package_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_package_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_resource_manager.rs b/core-rust/core-api-server/src/core_api/generated/models/state_resource_manager.rs index 918f876afe..9af1480d02 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_resource_manager.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_resource_manager.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_resource_request.rs b/core-rust/core-api-server/src/core_api/generated/models/state_resource_request.rs index 8c0fd43d52..d4d649f482 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_resource_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_resource_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_resource_response.rs b/core-rust/core-api-server/src/core_api/generated/models/state_resource_response.rs index 332f3fd83b..43da3bbe28 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_resource_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_resource_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_updates.rs b/core-rust/core-api-server/src/core_api/generated/models/state_updates.rs index 5aaac8b60d..22aaacb42d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_updates.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_updates.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_validator_request.rs b/core-rust/core-api-server/src/core_api/generated/models/state_validator_request.rs index 85979550ac..9c7783f457 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_validator_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_validator_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/state_validator_response.rs b/core-rust/core-api-server/src/core_api/generated/models/state_validator_response.rs index fab98cb13b..eb07b784f3 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/state_validator_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/state_validator_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/static_blueprint_payload_def.rs b/core-rust/core-api-server/src/core_api/generated/models/static_blueprint_payload_def.rs index 700da55a82..874fc537d0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/static_blueprint_payload_def.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/static_blueprint_payload_def.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/static_blueprint_payload_def_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/static_blueprint_payload_def_all_of.rs index 1f8af36f3a..0827551e2c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/static_blueprint_payload_def_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/static_blueprint_payload_def_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/static_role_definition_auth_template.rs b/core-rust/core-api-server/src/core_api/generated/models/static_role_definition_auth_template.rs index b8c38ed60c..722c308926 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/static_role_definition_auth_template.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/static_role_definition_auth_template.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details.rs index 078b96723c..9e28605285 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs index 73e4e5b8c4..17ce0f5b17 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_epoch_out_of_bounds.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_epoch_out_of_bounds_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_epoch_out_of_bounds_all_of.rs index 792285169f..45f2ecb090 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_epoch_out_of_bounds_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_epoch_out_of_bounds_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs index d14c0e22a0..4c9c65f41f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_state_version_out_of_bounds.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_state_version_out_of_bounds_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_state_version_out_of_bounds_all_of.rs index 69ef3734b7..b91ed54071 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_state_version_out_of_bounds_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_requested_state_version_out_of_bounds_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_type.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_type.rs index 840ea7d5cf..de579b9868 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_details_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_response.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_response.rs index 5ac922e497..af2785fad5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_response_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_response_all_of.rs index 99ab6cb5fa..4fa1b01fcf 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_response_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_error_response_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter.rs index 7684d10a25..d791664728 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_any.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_any.rs index 6d06ccba6b..7a816940c6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_any.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_any.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_any_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_any_all_of.rs index 0d217dda93..f3ce454de5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_any_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_any_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_new_epochs.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_new_epochs.rs index 14a1e84e15..6fc856e66b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_new_epochs.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_new_epochs.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_new_epochs_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_new_epochs_all_of.rs index b7f43b52ba..133302505d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_new_epochs_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_new_epochs_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_execution.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_execution.rs index 0348491354..2c8108b58e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_execution.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_execution.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_execution_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_execution_all_of.rs index 8e80ed5238..45992cc367 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_execution_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_execution_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_initializations.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_initializations.rs index 385f2fbaf5..23a93859f9 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_initializations.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_protocol_update_initializations.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_type.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_type.rs index 8c2f9e19a0..a0f6c2bec8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_filter_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_request.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_request.rs index a3eed7017d..2ce8698f33 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_response.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_response.rs index 1b4592bdc3..54ccea327d 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_proofs_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_details.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_details.rs index 0cd0d3d5ac..5ed26ae38e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_details_type.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_details_type.rs index 64c06c27d6..0da0f06024 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_details_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_details_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_response.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_response.rs index fc3cdb95e7..2441e78bf1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_response_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_response_all_of.rs index d5f8371eab..934896e0f4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_response_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_error_response_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_request.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_request.rs index a39aab1386..5d96c2b61c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_response.rs b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_response.rs index 4aafe2a27c..3a62a03598 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/stream_transactions_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/string_plaintext_message_content.rs b/core-rust/core-api-server/src/core_api/generated/models/string_plaintext_message_content.rs index 57fedbd25a..d6125ec491 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/string_plaintext_message_content.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/string_plaintext_message_content.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/string_plaintext_message_content_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/string_plaintext_message_content_all_of.rs index 358e46c69e..5fd25547e2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/string_plaintext_message_content_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/string_plaintext_message_content_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/substate.rs b/core-rust/core-api-server/src/core_api/generated/models/substate.rs index 74ab45003d..bac09fa3ee 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/substate_format_options.rs b/core-rust/core-api-server/src/core_api/generated/models/substate_format_options.rs index e0225cad4a..ddd9f05865 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/substate_format_options.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/substate_format_options.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/substate_id.rs b/core-rust/core-api-server/src/core_api/generated/models/substate_id.rs index f9d980cfb8..d96ab13c65 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/substate_id.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/substate_id.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/substate_id_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/substate_id_all_of.rs index f6a3e4a625..9494e3c350 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/substate_id_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/substate_id_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/substate_key.rs b/core-rust/core-api-server/src/core_api/generated/models/substate_key.rs index 44d9ae1653..002c6bb5c0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/substate_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/substate_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/substate_key_type.rs b/core-rust/core-api-server/src/core_api/generated/models/substate_key_type.rs index 865c75434e..8911af5fd1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/substate_key_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/substate_key_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/substate_system_structure.rs b/core-rust/core-api-server/src/core_api/generated/models/substate_system_structure.rs index 81fd5fab04..4587d61408 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/substate_system_structure.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/substate_system_structure.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/substate_system_structure_type.rs b/core-rust/core-api-server/src/core_api/generated/models/substate_system_structure_type.rs index 501e4bcf8a..2933b70342 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/substate_system_structure_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/substate_system_structure_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/substate_type.rs b/core-rust/core-api-server/src/core_api/generated/models/substate_type.rs index 3ba36423cb..bc079e6020 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/substate_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/substate_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/substate_value.rs b/core-rust/core-api-server/src/core_api/generated/models/substate_value.rs index 75a6e1f9a9..4e647cff7a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/substate_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/substate_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/system_costing_parameters.rs b/core-rust/core-api-server/src/core_api/generated/models/system_costing_parameters.rs index 4da3bb7858..bd7a510174 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/system_costing_parameters.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/system_costing_parameters.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/system_field_kind.rs b/core-rust/core-api-server/src/core_api/generated/models/system_field_kind.rs index 04651b7659..6ad487d612 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/system_field_kind.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/system_field_kind.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/system_field_structure.rs b/core-rust/core-api-server/src/core_api/generated/models/system_field_structure.rs index 0b80bb0bd0..67bbe15002 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/system_field_structure.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/system_field_structure.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/system_field_structure_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/system_field_structure_all_of.rs index 1dc00bc6ec..a23324a7c2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/system_field_structure_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/system_field_structure_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/system_parameters.rs b/core-rust/core-api-server/src/core_api/generated/models/system_parameters.rs index bd8627c768..da8d148ff9 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/system_parameters.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/system_parameters.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/system_schema_structure.rs b/core-rust/core-api-server/src/core_api/generated/models/system_schema_structure.rs index a223df45fa..7d62355a2a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/system_schema_structure.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/system_schema_structure.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/system_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/system_transaction.rs index 0effc38deb..6361b670d2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/system_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/system_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/target_identifier.rs b/core-rust/core-api-server/src/core_api/generated/models/target_identifier.rs index e4440fcccf..6fc1bd8fc1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/target_identifier.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/target_identifier.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/target_identifier_type.rs b/core-rust/core-api-server/src/core_api/generated/models/target_identifier_type.rs index e882b948f7..626c04c1f0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/target_identifier_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/target_identifier_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/timestamped_validator_signature.rs b/core-rust/core-api-server/src/core_api/generated/models/timestamped_validator_signature.rs index acbc0db5e7..ea30339848 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/timestamped_validator_signature.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/timestamped_validator_signature.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_call_preview_request.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_call_preview_request.rs index 8589263a91..f223998c52 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_call_preview_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_call_preview_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_call_preview_response.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_call_preview_response.rs index 1a346175a9..f0added8b4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_call_preview_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_call_preview_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_format_options.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_format_options.rs index 511f552189..4e3d36b767 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_format_options.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_format_options.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_header.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_header.rs index 1c82baae05..0c202f4f48 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_header.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_header.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_id_key.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_id_key.rs index 5f7855af86..ade7a58fae 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_id_key.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_id_key.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_identifiers.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_identifiers.rs index 9acb2cfcee..854a23b9f0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_identifiers.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_identifiers.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_intent.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_intent.rs index 8c49b479ae..6228cf5577 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_intent.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_intent.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_intent_status.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_intent_status.rs index 6a65bb8ab6..33fb7e9f99 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_intent_status.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_intent_status.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_message.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_message.rs index 1abdbcac6b..1c1bdaac20 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_message.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_message.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_message_type.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_message_type.rs index 493a0e1721..3b5d14b157 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_message_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_message_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_parse_request.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_parse_request.rs index 4ad73b4f55..8099e08f43 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_parse_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_parse_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_parse_response.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_parse_response.rs index 83f0ebf3a2..67c0938866 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_parse_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_parse_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_payload_details.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_payload_details.rs index d3001208d2..0b4138d291 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_payload_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_payload_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_payload_status.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_payload_status.rs index db55ec7b82..55e87879fd 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_payload_status.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_payload_status.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_request.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_request.rs index 3deb7152bc..0698443b5f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ @@ -46,6 +46,8 @@ pub struct TransactionPreviewRequest { pub signer_public_keys: Vec, #[serde(rename = "message", skip_serializing_if = "Option::is_none")] pub message: Option>, + #[serde(rename = "options", skip_serializing_if = "Option::is_none")] + pub options: Option>, #[serde(rename = "flags")] pub flags: Box, } @@ -65,6 +67,7 @@ impl TransactionPreviewRequest { nonce, signer_public_keys, message: None, + options: None, flags: Box::new(flags), } } diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_request_flags.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_request_flags.rs index 70b3140746..adb31e32d4 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_request_flags.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_request_flags.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_response.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_response.rs index 9f0658ebf4..19afee1de6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ @@ -15,11 +15,14 @@ pub struct TransactionPreviewResponse { #[serde(rename = "at_ledger_state")] pub at_ledger_state: Box, - /// The hex-sbor-encoded receipt + /// 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. #[serde(rename = "encoded_receipt")] pub encoded_receipt: String, #[serde(rename = "receipt")] pub receipt: Box, + /// 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. + #[serde(rename = "radix_engine_toolkit_receipt", skip_serializing_if = "Option::is_none")] + pub radix_engine_toolkit_receipt: Option, #[serde(rename = "instruction_resource_changes")] pub instruction_resource_changes: Vec, #[serde(rename = "logs")] @@ -32,6 +35,7 @@ impl TransactionPreviewResponse { at_ledger_state: Box::new(at_ledger_state), encoded_receipt, receipt: Box::new(receipt), + radix_engine_toolkit_receipt: None, instruction_resource_changes, logs, } diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_response_logs_inner.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_response_logs_inner.rs index edbbcf166e..57b755a9f8 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_response_logs_inner.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_response_logs_inner.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_response_options.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_response_options.rs new file mode 100644 index 0000000000..a538663617 --- /dev/null +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_preview_response_options.rs @@ -0,0 +1,31 @@ +/* + * 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 + */ + +/// TransactionPreviewResponseOptions : A set of flags to configure the response of the transaction preview. + + + +#[derive(Clone, Debug, PartialEq, Default, serde::Serialize, serde::Deserialize)] +pub struct TransactionPreviewResponseOptions { + /// 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 TransactionPreviewResponseOptions { + /// A set of flags to configure the response of the transaction preview. + pub fn new() -> TransactionPreviewResponseOptions { + TransactionPreviewResponseOptions { + radix_engine_toolkit_receipt: None, + } + } +} + + diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt.rs index bd9c245533..e23ec7c4e5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt_request.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt_request.rs index 1129e65d11..ba7c16c161 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt_response.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt_response.rs index 148db39bb1..486a7d6e06 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_receipt_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_status.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_status.rs index 3508da3e5a..fe0c6ec2be 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_status.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_status.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_status_request.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_status_request.rs index 56175f2dbd..9227969e4e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_status_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_status_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_status_response.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_status_response.rs index 78a6f40453..ad7e7c7505 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_status_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_status_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_details.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_details.rs index f79bb4ad95..d15da3ccd2 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_details_type.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_details_type.rs index 282a2d7bdd..0ec6ee8a50 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_details_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_details_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_response.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_response.rs index d507a66a27..69876f8895 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_response_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_response_all_of.rs index d051f10336..f65d22b570 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_response_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_error_response_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_intent_already_committed.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_intent_already_committed.rs index 1a72bee6d8..23d7a9863a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_intent_already_committed.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_intent_already_committed.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_priority_threshold_not_met_error_details.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_priority_threshold_not_met_error_details.rs index 70ee86f3cd..70491d000a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_priority_threshold_not_met_error_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_priority_threshold_not_met_error_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_rejected_error_details.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_rejected_error_details.rs index c0552f9d1b..c03928e569 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_rejected_error_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_rejected_error_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_request.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_request.rs index 78867c803f..284725a040 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_response.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_response.rs index c711a11ca7..48c6febe78 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_response.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_submit_response.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_substate.rs index e354e8d1d3..312c992369 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_substate_all_of.rs index 68f4599c9c..92524a2af0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_value.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_value.rs index 566f8d3516..99680726d6 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_collection_entry_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_substate.rs index eb5ad808c0..8ba8db0514 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_substate_all_of.rs index c09df4b0e9..6dd55374ce 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_value.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_value.rs index 5a373569ab..162ae1a887 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_field_state_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_transaction_status.rs b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_transaction_status.rs index f246925898..f9097fcfa7 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_transaction_status.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/transaction_tracker_transaction_status.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_substate.rs index 01356635ff..f6e5e2a04f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_substate_all_of.rs index abac20e9ed..9a9409dc4b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_value.rs b/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_value.rs index 7f022b0d64..7b5b3cc1ca 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/two_resource_pool_field_state_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/type_info_details.rs b/core-rust/core-api-server/src/core_api/generated/models/type_info_details.rs index c3a07d2a44..d3200fcf0b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/type_info_details.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/type_info_details.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_substate.rs index 63451fdb95..cbd6eb0cfb 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_substate_all_of.rs index 0667c6c1dd..0e560a54d1 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_value.rs b/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_value.rs index d3eda31606..6ff21e0ac5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/type_info_module_field_type_info_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/type_info_type.rs b/core-rust/core-api-server/src/core_api/generated/models/type_info_type.rs index e59d6405f0..9884019122 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/type_info_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/type_info_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/updated_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/updated_substate.rs index 280dbb17e2..6de4fdb9c5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/updated_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/updated_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/user_ledger_transaction.rs b/core-rust/core-api-server/src/core_api/generated/models/user_ledger_transaction.rs index a153039ca3..9ff4a4081e 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/user_ledger_transaction.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/user_ledger_transaction.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/user_ledger_transaction_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/user_ledger_transaction_all_of.rs index 917b36c147..864d1000e5 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/user_ledger_transaction_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/user_ledger_transaction_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/validator_fee_change_request.rs b/core-rust/core-api-server/src/core_api/generated/models/validator_fee_change_request.rs index cdd155a254..1097b5f15c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/validator_fee_change_request.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/validator_fee_change_request.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_substate.rs index a74297702b..1167bbb37a 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_substate_all_of.rs index 7a4ee70d00..8a14ead650 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_value.rs b/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_value.rs index 583877432d..0b70876c1c 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/validator_field_protocol_update_readiness_signal_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_substate.rs b/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_substate.rs index 11e517e2dd..5494f35516 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_substate.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_substate.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_substate_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_substate_all_of.rs index 81771abb8b..903f35d31b 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_substate_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_substate_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_value.rs b/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_value.rs index ecf288afce..b969e0ef7f 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_value.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/validator_field_state_value.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/vault_balance.rs b/core-rust/core-api-server/src/core_api/generated/models/vault_balance.rs index 4c2f39bb40..8da233c0b0 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/vault_balance.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/vault_balance.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/version_ledger_state_selector.rs b/core-rust/core-api-server/src/core_api/generated/models/version_ledger_state_selector.rs index 65d1f92ec0..1129c09842 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/version_ledger_state_selector.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/version_ledger_state_selector.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/version_ledger_state_selector_all_of.rs b/core-rust/core-api-server/src/core_api/generated/models/version_ledger_state_selector_all_of.rs index 649e9029b3..7abdf65058 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/version_ledger_state_selector_all_of.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/version_ledger_state_selector_all_of.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/virtual_lazy_load_schema.rs b/core-rust/core-api-server/src/core_api/generated/models/virtual_lazy_load_schema.rs index 4298c60a10..786f86c1e9 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/virtual_lazy_load_schema.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/virtual_lazy_load_schema.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/generated/models/vm_type.rs b/core-rust/core-api-server/src/core_api/generated/models/vm_type.rs index c104ed1282..e1392ecbab 100644 --- a/core-rust/core-api-server/src/core_api/generated/models/vm_type.rs +++ b/core-rust/core-api-server/src/core_api/generated/models/vm_type.rs @@ -1,9 +1,9 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/core-api-server/src/core_api/handlers/transaction_preview.rs b/core-rust/core-api-server/src/core_api/handlers/transaction_preview.rs index 0d8608ad7c..e6b2e23a19 100644 --- a/core-rust/core-api-server/src/core_api/handlers/transaction_preview.rs +++ b/core-rust/core-api-server/src/core_api/handlers/transaction_preview.rs @@ -1,7 +1,8 @@ use crate::core_api::*; use crate::engine_prelude::*; -use state_manager::store::rocks_db::ActualStateManagerDatabase; +use radix_engine_toolkit::receipt::RuntimeToolkitTransactionReceipt; +use state_manager::rocks_db::ActualStateManagerDatabase; use state_manager::transaction::ProcessedPreviewResult; use state_manager::{ExecutionFeeData, LocalTransactionReceipt, PreviewRequest}; @@ -19,6 +20,11 @@ pub(crate) async fn handle_transaction_preview( .transpose() .map_err(|err| err.into_response_error("at_ledger_state"))?; + let should_produce_toolkit_receipt = request + .options + .as_ref() + .and_then(|opt_ins| opt_ins.radix_engine_toolkit_receipt) + .unwrap_or(false); let preview_request = extract_preview_request(&state.network, request)?; let result = state @@ -26,7 +32,7 @@ pub(crate) async fn handle_transaction_preview( .transaction_previewer .preview(preview_request, at_state_version)?; - to_api_response(&mapping_context, result).map(Json) + to_api_response(&mapping_context, result, should_produce_toolkit_receipt).map(Json) } fn extract_preview_request( @@ -41,11 +47,9 @@ fn extract_preview_request( .collect::>() .map_err(|err| err.into_response_error("blobs"))?; let manifest_blob_provider = BlobProvider::new_with_blobs(manifest_blobs); - let manifest = compile(&request.manifest, network, manifest_blob_provider) + let manifest = manifest::compile(&request.manifest, network, manifest_blob_provider) .map_err(|err| client_error(format!("Invalid manifest - {err:?}")))?; - let honor_requested_epoch_range = !request.flags.skip_epoch_check; - let signer_public_keys: Vec<_> = request .signer_public_keys .into_iter() @@ -55,21 +59,20 @@ fn extract_preview_request( Ok(PreviewRequest { manifest, - start_epoch_inclusive: request - .start_epoch_inclusive - .filter(|_| honor_requested_epoch_range) - .map(|number| { - extract_epoch(number) - .map_err(|err| err.into_response_error("start_epoch_inclusive")) - }) - .transpose()?, - end_epoch_exclusive: request - .end_epoch_exclusive - .filter(|_| honor_requested_epoch_range) - .map(|number| { - extract_epoch(number).map_err(|err| err.into_response_error("end_epoch_exclusive")) - }) - .transpose()?, + start_epoch_inclusive: match request.start_epoch_inclusive { + Some(start_epoch_inclusive) => Some( + extract_epoch(start_epoch_inclusive) + .map_err(|err| err.into_response_error("start_epoch_inclusive"))?, + ), + None => None, + }, + end_epoch_exclusive: match request.end_epoch_exclusive { + Some(end_epoch_exclusive) => Some( + extract_epoch(end_epoch_exclusive) + .map_err(|err| err.into_response_error("start_epoch_inclusive"))?, + ), + None => None, + }, notary_public_key: request .notary_public_key .map(|pk| { @@ -101,13 +104,33 @@ fn extract_preview_request( fn to_api_response( context: &MappingContext, result: ProcessedPreviewResult, + should_include_toolkit_receipt: bool, ) -> Result> { let engine_receipt = result.receipt; let versioned_engine_receipt = engine_receipt.clone().into_versioned(); - // This is interpreted by the toolkit in the wallet + // This is interpreted by the toolkit in the wallet. This will be removed with the release of + // the cuttlefish protocol update. let encoded_receipt = to_hex(scrypto_encode(&versioned_engine_receipt).unwrap()); + // Produce a toolkit transaction receipt for the transaction preview if it was requested in the + // request opt-ins. + let toolkit_receipt = if should_include_toolkit_receipt { + Some( + RuntimeToolkitTransactionReceipt::try_from(versioned_engine_receipt.clone()) + .ok() + .and_then(|value| { + value + .into_serializable_receipt(&context.address_encoder) + .ok() + }) + .and_then(|value| serde_json::to_value(&value).ok()) + .ok_or(server_error("Can't produce toolkit transaction receipt."))?, + ) + } else { + None + }; + let at_ledger_state = Box::new(to_api_ledger_state_summary( context, &result.base_ledger_state, @@ -180,6 +203,7 @@ fn to_api_response( context, local_receipt, )?), + radix_engine_toolkit_receipt: toolkit_receipt, instruction_resource_changes, logs, } @@ -206,6 +230,7 @@ fn to_api_response( next_epoch: None, error_message: Some(format!("{reject_result:?}")), }), + radix_engine_toolkit_receipt: toolkit_receipt, instruction_resource_changes: vec![], logs: vec![], }, diff --git a/core-rust/engine-state-api-server/engine-state-api-schema.yaml b/core-rust/engine-state-api-server/engine-state-api-schema.yaml index 433908360f..06d2d0bd0c 100644 --- a/core-rust/engine-state-api-server/engine-state-api-schema.yaml +++ b/core-rust/engine-state-api-server/engine-state-api-schema.yaml @@ -1,8 +1,8 @@ openapi: 3.1.0 info: - version: 'v1.2.1-beta' - title: 'Engine State API - Babylon (Anemone)' + version: 'v1.2.3' + title: 'Engine State API (Beta)' license: name: The Radix License, Version 1.0 url: https://www.radixfoundation.org/licenses/license-v1 diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/mod.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/mod.rs index aafba43e32..e3ba6c7699 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/mod.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/mod.rs @@ -1,2 +1,2 @@ pub mod models; -pub const SCHEMA_VERSION: &str = "v0.1-beta"; +pub const SCHEMA_VERSION: &str = "v1.2.3"; diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule.rs index 996df6c79b..23bc554e31 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_node.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_node.rs index c0b6719f4e..48ff0942b0 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_node.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_node.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_node_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_node_type.rs index 69e4bc91a5..4b07fc0b6d 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_node_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_node_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_type.rs index 4097a590b0..73c14aae79 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/access_rule_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_access_rule_node.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_access_rule_node.rs index 02cadeffd5..b80ecca484 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_access_rule_node.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_access_rule_node.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_proof_rule.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_proof_rule.rs index cd8396a97b..3513fbab39 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_proof_rule.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_proof_rule.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_proof_rule_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_proof_rule_all_of.rs index 3b75740571..d8b120550a 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_proof_rule_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/all_of_proof_rule_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/allow_all_access_rule.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/allow_all_access_rule.rs index 4d21226802..4a94398398 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/allow_all_access_rule.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/allow_all_access_rule.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/amount_of_proof_rule.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/amount_of_proof_rule.rs index c4d659bb95..d4574b35ab 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/amount_of_proof_rule.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/amount_of_proof_rule.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/amount_of_proof_rule_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/amount_of_proof_rule_all_of.rs index 39d43e302e..c6e7fa3a37 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/amount_of_proof_rule_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/amount_of_proof_rule_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_generic_type_parameter.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_generic_type_parameter.rs index 938534a770..6bebecf7ea 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_generic_type_parameter.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_generic_type_parameter.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_access_rule_node.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_access_rule_node.rs index 9031bb8e71..cc890ae9ad 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_access_rule_node.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_access_rule_node.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_access_rule_node_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_access_rule_node_all_of.rs index 0a86946194..daa4aa8826 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_access_rule_node_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_access_rule_node_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_proof_rule.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_proof_rule.rs index aff4c6cf85..a1f47596bf 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_proof_rule.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/any_of_proof_rule.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/assignment.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/assignment.rs index ad7b4c7af9..7d32da8c62 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/assignment.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/assignment.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/assignment_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/assignment_type.rs index f5902231ce..8e837089bb 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/assignment_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/assignment_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/attached_module_id.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/attached_module_id.rs index 5d6af17b47..b846b37737 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/attached_module_id.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/attached_module_id.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_collection_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_collection_info.rs index 1f8b192753..206a8329b2 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_collection_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_collection_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_event_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_event_info.rs index 9e14979c98..ff546ce613 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_event_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_event_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_condition.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_condition.rs index a0e49baf18..a3fbd7b6a7 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_condition.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_condition.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_condition_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_condition_type.rs index d0c0af8a1d..ec4ff6478f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_condition_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_condition_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_info.rs index f5b35dcd3e..d9c069c674 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_transience.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_transience.rs index 4e28afd9d9..d1ba67447b 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_transience.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_field_transience.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_filter.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_filter.rs index b129b98e00..ffa79b7a35 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_filter.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_filter.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_filter_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_filter_all_of.rs index 45099a8170..1f8ee9ce47 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_filter_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_filter_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_authorization.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_authorization.rs index 9dd99cc0a3..f115001781 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_authorization.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_authorization.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_authorization_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_authorization_type.rs index 8180723b7a..16e486006b 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_authorization_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_authorization_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_info.rs index e5416bcb27..716881a792 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_function_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_generic_type_reference.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_generic_type_reference.rs index aa7d76b5fa..31b121e49a 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_generic_type_reference.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_generic_type_reference.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_generic_type_reference_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_generic_type_reference_all_of.rs index 68140783da..6b13efd84c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_generic_type_reference_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_generic_type_reference_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_info_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_info_request.rs index bdafeaa818..c7b43dbb23 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_info_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_info_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_info_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_info_response.rs index f205b64b5f..42cc2dc78e 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_info_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_info_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_authorization.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_authorization.rs index 55b0eba409..9da17d2e6d 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_authorization.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_authorization.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_authorization_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_authorization_type.rs index b0302c4cf9..110d2afa55 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_authorization_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_authorization_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_info.rs index a8a7c791c8..eeb558ea20 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_receiver_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_receiver_info.rs index 4404883a55..1777aa497d 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_receiver_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_method_receiver_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_named_type_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_named_type_info.rs index 078fa0c11d..533940b2ef 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_named_type_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_named_type_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_reference.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_reference.rs index db1dc0e621..2e822dfa8b 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_reference.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_reference.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_resolved_type_reference.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_resolved_type_reference.rs index 8ed25cfc5d..49517d6d15 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_resolved_type_reference.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_resolved_type_reference.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_resolved_type_reference_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_resolved_type_reference_type.rs index 7b8bca807a..9646564028 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_resolved_type_reference_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_resolved_type_reference_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_role_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_role_info.rs index 2ce1df5c09..41b1a01f99 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_role_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_role_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_roles_definition.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_roles_definition.rs index 88da7e7490..aa1892a88d 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_roles_definition.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_roles_definition.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_roles_definition_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_roles_definition_type.rs index a703263fd8..4449a6a64c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_roles_definition_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_roles_definition_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_static_type_reference.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_static_type_reference.rs index a60d2cf88c..6ec7b726e6 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_static_type_reference.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_static_type_reference.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_static_type_reference_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_static_type_reference_all_of.rs index 9da10445db..a6ff584102 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_static_type_reference_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/blueprint_static_type_reference_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_array_metadata_value.rs index 6dc8d99c07..5738dd3151 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_array_metadata_value_all_of.rs index ec1a31da52..65448ede18 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_metadata_value.rs index 825d66709e..681b91cbb1 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_metadata_value_all_of.rs index 1be2117837..60c487fd77 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/bool_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_access_rule_blueprint_function_authorization.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_access_rule_blueprint_function_authorization.rs index 275a038675..c0e6e2ac93 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_access_rule_blueprint_function_authorization.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_access_rule_blueprint_function_authorization.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_access_rule_blueprint_function_authorization_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_access_rule_blueprint_function_authorization_all_of.rs index df0573f513..cefc9b6a66 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_access_rule_blueprint_function_authorization_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_access_rule_blueprint_function_authorization_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_roles_blueprint_method_authorization.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_roles_blueprint_method_authorization.rs index a63810a4c7..5893b4f75c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_roles_blueprint_method_authorization.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_roles_blueprint_method_authorization.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_roles_blueprint_method_authorization_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_roles_blueprint_method_authorization_all_of.rs index 545422e914..86a6639e76 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_roles_blueprint_method_authorization_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/by_roles_blueprint_method_authorization_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/collection_entry_key.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/collection_entry_key.rs index 5ec040bd08..c6c6211470 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/collection_entry_key.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/collection_entry_key.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/consensus_instant.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/consensus_instant.rs index f0c6ba6ecc..96ed22e6f5 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/consensus_instant.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/consensus_instant.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/count_of_proof_rule.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/count_of_proof_rule.rs index e0ebdd6034..1bb0dd3bc4 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/count_of_proof_rule.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/count_of_proof_rule.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/count_of_proof_rule_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/count_of_proof_rule_all_of.rs index 0ac8cd7b88..b6a4ed3173 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/count_of_proof_rule_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/count_of_proof_rule_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_array_metadata_value.rs index 3af8ff2bd3..2e57516826 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_array_metadata_value_all_of.rs index e82d91dc30..a1b61a3200 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_metadata_value.rs index 5db6d383a6..75f760e28b 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_metadata_value_all_of.rs index 253df11386..3279046319 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/decimal_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/deny_all_access_rule.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/deny_all_access_rule.rs index b808980963..9e8c70a4cb 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/deny_all_access_rule.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/deny_all_access_rule.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/detailed_blueprint_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/detailed_blueprint_info.rs index d43b09a0b6..ca6b0da204 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/detailed_blueprint_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/detailed_blueprint_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ecdsa_secp256k1_public_key.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ecdsa_secp256k1_public_key.rs index 4c46595de3..615457ef05 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ecdsa_secp256k1_public_key.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ecdsa_secp256k1_public_key.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ecdsa_secp256k1_public_key_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ecdsa_secp256k1_public_key_all_of.rs index 9dba13324e..c516cb6bf6 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ecdsa_secp256k1_public_key_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ecdsa_secp256k1_public_key_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/eddsa_ed25519_public_key.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/eddsa_ed25519_public_key.rs index f10ac4ab5f..4e2e3464a2 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/eddsa_ed25519_public_key.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/eddsa_ed25519_public_key.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/eddsa_ed25519_public_key_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/eddsa_ed25519_public_key_all_of.rs index ef2590ebc0..f835b74a7c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/eddsa_ed25519_public_key_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/eddsa_ed25519_public_key_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_ancestry_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_ancestry_info.rs index 61344018ba..06557e7b86 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_ancestry_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_ancestry_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info.rs index d812fd0c1c..745e2805ce 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info_request.rs index de82ff885a..4d9e62d5b8 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info_response.rs index a7f7a1da3c..2e6955ff8f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_info_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_schema_entry_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_schema_entry_request.rs index c8fd37a5c7..e70b587f3f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_schema_entry_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_schema_entry_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_schema_entry_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_schema_entry_response.rs index e3ac177e6e..235101363c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_schema_entry_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_schema_entry_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_search_filter.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_search_filter.rs index 982defeee9..9f71803ecf 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_search_filter.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_search_filter.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_search_filter_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_search_filter_type.rs index 429e7e7638..7ccdfe584d 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_search_filter_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_search_filter_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type.rs index f62d8ab86c..3046684f5c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type_filter.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type_filter.rs index d00f12404e..37cb1f210d 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type_filter.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type_filter.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type_filter_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type_filter_all_of.rs index 3c13c0176f..6ce06178d1 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type_filter_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/entity_type_filter_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/epoch_round.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/epoch_round.rs index cdd4f6b245..eb1a644f68 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/epoch_round.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/epoch_round.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_details.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_details.rs index cf49ca3bdb..37f047939b 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_details.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_details.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_response.rs index 569e2cf61f..3a537cf318 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_type.rs index 5cb1908cd9..f26df57fc4 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/error_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/explicit_assignment.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/explicit_assignment.rs index 129bed78f1..ce4532645e 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/explicit_assignment.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/explicit_assignment.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/extra_entity_search_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/extra_entity_search_request.rs index 30d6dd406d..0168b3500f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/extra_entity_search_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/extra_entity_search_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/extra_entity_search_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/extra_entity_search_response.rs index c309ca6345..1be8a829bf 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/extra_entity_search_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/extra_entity_search_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/generic_type_parameter.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/generic_type_parameter.rs index 03c1d4600f..ccab742a04 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/generic_type_parameter.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/generic_type_parameter.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/generic_type_parameter_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/generic_type_parameter_type.rs index 2d9172c0cd..913aeacd70 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/generic_type_parameter_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/generic_type_parameter_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_array_metadata_value.rs index 7511d73ba5..1037637576 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_array_metadata_value_all_of.rs index 8fde146b0e..989c2f3c7d 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_metadata_value.rs index a95be3906a..f3a4061fc1 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_metadata_value_all_of.rs index 5f7bf60de3..d655e23fc5 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/global_address_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_array_metadata_value.rs index 552f44d81f..76c913a2b5 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_array_metadata_value_all_of.rs index bc0f8862c8..af58ef8048 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_metadata_value.rs index cb34424e8a..116c4c74a7 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_metadata_value_all_of.rs index 9ce3b5eb7e..7d8b4cf035 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i32_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_array_metadata_value.rs index 06405474d1..115e647d91 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_array_metadata_value_all_of.rs index 9df8e98a3a..fc13d36b9e 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_metadata_value.rs index 68a8a38206..4ea5c88172 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_metadata_value_all_of.rs index 59b3024fac..d05ebf886e 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/i64_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_outer_object_feature_field_condition.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_outer_object_feature_field_condition.rs index ff11a7d8c8..be7c939329 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_outer_object_feature_field_condition.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_outer_object_feature_field_condition.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_own_feature_field_condition.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_own_feature_field_condition.rs index e2a179634e..2c55a2a879 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_own_feature_field_condition.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_own_feature_field_condition.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_own_feature_field_condition_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_own_feature_field_condition_all_of.rs index 05cb3411a5..e16592ac06 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_own_feature_field_condition_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/if_own_feature_field_condition_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/index_entry_key.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/index_entry_key.rs index df089fb074..bebec7e2ba 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/index_entry_key.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/index_entry_key.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_array_metadata_value.rs index ae266573fc..ad339b755b 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_array_metadata_value_all_of.rs index 85615df2e7..58151fbbf9 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_metadata_value.rs index e3ee88fa45..d3875a961f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_metadata_value_all_of.rs index 1270d5db89..848baf68ce 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/instant_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entity_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entity_info.rs index a3c08fb97f..5d6ba44ade 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entity_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entity_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entity_info_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entity_info_all_of.rs index 41c381337b..ebeb9700fa 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entity_info_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entity_info_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_key.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_key.rs index e4e2967962..9cc34e56a3 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_key.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_key.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_key_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_key_all_of.rs index 4028b56134..db2cdd5a08 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_key_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_key_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_request.rs index ff053e9d6c..4822b5e054 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_response.rs index 62a3f9fab5..7ffe512a93 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_entry_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_iterator_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_iterator_request.rs index 15e70fcc2a..5a23e0eb3d 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_iterator_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_iterator_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_iterator_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_iterator_response.rs index 5381036f7a..332ec6cef9 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_iterator_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_iterator_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_map_key.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_map_key.rs index 7b092613a4..2531aef7d3 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_map_key.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/key_value_store_map_key.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_hashes.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_hashes.rs index 28ef78eb73..8e62542fd7 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_hashes.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_hashes.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_header_summary.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_header_summary.rs index b978fe16ef..6f58b5eaef 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_header_summary.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_header_summary.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_selector.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_selector.rs index 63feb0f0d7..e2a44e241c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_selector.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_selector.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_selector_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_selector_type.rs index be2f4bc95e..df16de6bdd 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_selector_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_selector_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_summary.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_summary.rs index dd155fadc9..1d59da1c83 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_summary.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/ledger_state_summary.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/listed_entity_item.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/listed_entity_item.rs index 716e0364b3..2b464db0fa 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/listed_entity_item.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/listed_entity_item.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/local_blueprint_roles_definition.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/local_blueprint_roles_definition.rs index bd77ddaf3e..4bb2e60f4f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/local_blueprint_roles_definition.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/local_blueprint_roles_definition.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/local_blueprint_roles_definition_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/local_blueprint_roles_definition_all_of.rs index a2f455293a..0803346879 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/local_blueprint_roles_definition_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/local_blueprint_roles_definition_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_entry_key.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_entry_key.rs index 1ebb2c236c..6ece539b66 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_entry_key.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_entry_key.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_value.rs index 9cb6775765..43f8dbe576 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_value_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_value_type.rs index 8447b3984d..f46e88a02a 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_value_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/metadata_value_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/method_receiver_reference_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/method_receiver_reference_type.rs index 234727db29..ec47fbbf01 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/method_receiver_reference_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/method_receiver_reference_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/method_receiver_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/method_receiver_type.rs index 8fd27fe1c3..9983daa1bc 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/method_receiver_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/method_receiver_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id.rs index c8dbc65fcc..9d1fc72a3c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_array_metadata_value.rs index 9960906cae..9bd7510348 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_array_metadata_value_all_of.rs index 1bbb9f5ce8..09b256d172 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_metadata_value.rs index b081719787..a044a04206 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_metadata_value_all_of.rs index 0289beb7b9..25939fe437 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_global_id_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_array_metadata_value.rs index ee07a5da66..5652da4a53 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_array_metadata_value_all_of.rs index d8ef350f64..f79d883bde 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_metadata_value.rs index 278eb51ed9..c403641b8e 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_metadata_value_all_of.rs index b2a1c5910d..042f6575e7 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_local_id_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_requirement.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_requirement.rs index 22ca3b0209..171bfe09ab 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_requirement.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_requirement.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_requirement_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_requirement_all_of.rs index 407f6bab32..9c97bf3824 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_requirement_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/non_fungible_requirement_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_entry_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_entry_request.rs index 9b5219f3d5..348a126dde 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_entry_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_entry_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_entry_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_entry_response.rs index c8f91e1c7b..d619c287fb 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_entry_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_entry_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_info.rs index ca2133f133..60e8341391 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_iterator_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_iterator_request.rs index deb98f2501..b94c4fa54c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_iterator_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_iterator_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_iterator_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_iterator_response.rs index b0f6c5e48e..5b671a6533 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_iterator_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_iterator_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_kind.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_kind.rs index 9b4224e062..f3683487d4 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_kind.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_collection_kind.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info.rs index a351dd8f38..5595080d7f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info_all_of.rs index 9d07ff7541..c7b2ade2b2 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info_all_of_attached_modules.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info_all_of_attached_modules.rs index 827314a966..7df039159e 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info_all_of_attached_modules.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_entity_info_all_of_attached_modules.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_info.rs index 17c1693ce0..e0dca633e5 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_request.rs index ffc54f37b3..02a2830c16 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_response.rs index 97d8fba5ed..04e79e972c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_field_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_instance_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_instance_info.rs index 5a442de382..cd3d4a6c82 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_instance_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_instance_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_entry_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_entry_request.rs index 02baca1c5e..97e76a1222 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_entry_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_entry_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_entry_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_entry_response.rs index 1ad212bc11..aa3163d0ee 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_entry_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_entry_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_iterator_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_iterator_request.rs index b87cf3c63d..492ee0029f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_iterator_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_iterator_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_iterator_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_iterator_response.rs index 28e676d72f..a847540d2f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_iterator_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_metadata_iterator_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_method_royalty.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_method_royalty.rs index 9dc53a5eff..d94783452d 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_method_royalty.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_method_royalty.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_module_state_info.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_module_state_info.rs index 6dedf93f6f..34a2a12395 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_module_state_info.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_module_state_info.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_request.rs index a89720be2a..7f9b0da1c1 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_response.rs index 63c5654aea..51f2d125ba 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_response_attached_modules_inner.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_response_attached_modules_inner.rs index a5a9f11c5c..f19e57bab1 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_response_attached_modules_inner.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_role_assignment_response_attached_modules_inner.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_royalty_request.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_royalty_request.rs index f9f1fb077b..1bd057f9bd 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_royalty_request.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_royalty_request.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_royalty_response.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_royalty_response.rs index ac5bdb7fe9..1a6598301d 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_royalty_response.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/object_royalty_response.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/origin_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/origin_array_metadata_value.rs index 50f1edb10d..a3184caec2 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/origin_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/origin_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/origin_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/origin_metadata_value.rs index 3402187507..4f4ec2c456 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/origin_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/origin_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/outer_blueprint_roles_definition.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/outer_blueprint_roles_definition.rs index b6358a217c..50313d352a 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/outer_blueprint_roles_definition.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/outer_blueprint_roles_definition.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/outer_object_only_blueprint_method_authorization.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/outer_object_only_blueprint_method_authorization.rs index ecc31e363f..466c45c7a1 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/outer_object_only_blueprint_method_authorization.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/outer_object_only_blueprint_method_authorization.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/own_package_only_blueprint_method_authorization.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/own_package_only_blueprint_method_authorization.rs index 65d2a6c17d..278c7ce852 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/own_package_only_blueprint_method_authorization.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/own_package_only_blueprint_method_authorization.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_assignment.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_assignment.rs index 77a84a84e3..f1d8ff486f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_assignment.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_assignment.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_role_entry.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_role_entry.rs index 5646275469..09497118d9 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_role_entry.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_role_entry.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_role_updater.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_role_updater.rs index e79e2a797f..bc7ce94249 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_role_updater.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/owner_role_updater.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_access_rule_node.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_access_rule_node.rs index 2657f1479d..460f116ec2 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_access_rule_node.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_access_rule_node.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_access_rule_node_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_access_rule_node_all_of.rs index 49d6bcc886..bd58a26943 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_access_rule_node_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_access_rule_node_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_rule.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_rule.rs index 4348842641..290db6336f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_rule.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_rule.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_rule_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_rule_type.rs index 359cf5ab94..a5ff980587 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_rule_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/proof_rule_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/protected_access_rule.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/protected_access_rule.rs index ea1cdcab30..833fec5da3 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/protected_access_rule.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/protected_access_rule.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/protected_access_rule_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/protected_access_rule_all_of.rs index d3f541fe4a..450a10b300 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/protected_access_rule_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/protected_access_rule_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_blueprint_function_authorization.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_blueprint_function_authorization.rs index 1eb3116a6f..68d90a479f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_blueprint_function_authorization.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_blueprint_function_authorization.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_blueprint_method_authorization.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_blueprint_method_authorization.rs index 080fd6c79e..869cee5b37 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_blueprint_method_authorization.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_blueprint_method_authorization.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key.rs index eff0a72973..15d153254a 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_array_metadata_value.rs index 821689ca43..89497ac3cc 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_array_metadata_value_all_of.rs index e176ef1059..9c60ae241b 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash.rs index 897a181dfd..c7b86a9ea8 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_array_metadata_value.rs index 35c5a58e25..5036179541 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_array_metadata_value_all_of.rs index feac47fbfc..225cd81f21 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_metadata_value.rs index dfb471984d..ae4dfb069f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_metadata_value_all_of.rs index 3cb563e59f..1b26b7ed1c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_hash_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_metadata_value.rs index f7ec067421..0f1e20e9c1 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_metadata_value_all_of.rs index c78580e865..173dbc910c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_type.rs index f04024d321..0a79c4b1aa 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/public_key_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_invalid_details.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_invalid_details.rs index bf3e830a49..04ff7f0a9b 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_invalid_details.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_invalid_details.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_not_found_details.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_not_found_details.rs index 95dbad69f9..c3022ed2a8 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_not_found_details.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_not_found_details.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_not_found_details_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_not_found_details_all_of.rs index 9a332975e4..0d79db379f 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_not_found_details_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_not_found_details_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_type.rs index 5ed8547745..674913fef6 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requested_item_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/require_proof_rule.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/require_proof_rule.rs index e6d6e4ab0c..bbcf187128 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/require_proof_rule.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/require_proof_rule.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/require_proof_rule_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/require_proof_rule_all_of.rs index dcbe452264..da754e74de 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/require_proof_rule_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/require_proof_rule_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requirement.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requirement.rs index 92a52c3240..e538ce2cb1 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requirement.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requirement.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requirement_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requirement_type.rs index 1afa9f97c1..f73e2a565e 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requirement_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/requirement_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resolved_type_reference.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resolved_type_reference.rs index 49323e3963..58a32dfcf7 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resolved_type_reference.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resolved_type_reference.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resolved_type_reference_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resolved_type_reference_type.rs index 7c2ecca431..57e2ae0df1 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resolved_type_reference_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resolved_type_reference_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resource_requirement.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resource_requirement.rs index ab6a883601..005c9feda5 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resource_requirement.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resource_requirement.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resource_requirement_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resource_requirement_all_of.rs index 369c2cc65d..b6a2141759 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resource_requirement_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/resource_requirement_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/role_assignment_entry.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/role_assignment_entry.rs index 3641d9932b..a8690e56a4 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/role_assignment_entry.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/role_assignment_entry.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/root_only_blueprint_function_authorization.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/root_only_blueprint_function_authorization.rs index acdbff0749..bb0d0d02de 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/root_only_blueprint_function_authorization.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/root_only_blueprint_function_authorization.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/royalty_amount.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/royalty_amount.rs index 5b3205789e..e7d01dda5e 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/royalty_amount.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/royalty_amount.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sbor_data.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sbor_data.rs index 5761bffa93..7bb35c9d2c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sbor_data.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sbor_data.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sbor_format_options.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sbor_format_options.rs index 7d5e1ea15a..453291fde6 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sbor_format_options.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sbor_format_options.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_defined_type_reference.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_defined_type_reference.rs index 5666429ecc..360da69eb0 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_defined_type_reference.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_defined_type_reference.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_defined_type_reference_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_defined_type_reference_all_of.rs index d958b8c4b4..1f55de8550 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_defined_type_reference_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_defined_type_reference_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_reference.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_reference.rs index 81b584b1ee..296461be0c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_reference.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/schema_reference.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/scrypto_instant.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/scrypto_instant.rs index 85a3a0396c..131bcf78a4 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/scrypto_instant.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/scrypto_instant.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sorted_index_entry_key.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sorted_index_entry_key.rs index 423d7f623d..5033fff23c 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sorted_index_entry_key.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sorted_index_entry_key.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sorted_index_entry_key_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sorted_index_entry_key_all_of.rs index 5737b84836..e5e744e65e 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sorted_index_entry_key_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/sorted_index_entry_key_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_future_details.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_future_details.rs index c113b6f8f0..c4db4454a5 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_future_details.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_future_details.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_future_details_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_future_details_all_of.rs index a6a169da29..c00f3571cb 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_future_details_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_future_details_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_too_distant_past_details.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_too_distant_past_details.rs index 12b2b674b4..0c8f2ac6fb 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_too_distant_past_details.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_too_distant_past_details.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_too_distant_past_details_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_too_distant_past_details_all_of.rs index 801bf4d27c..48e17cc951 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_too_distant_past_details_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/state_version_in_too_distant_past_details_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_array_metadata_value.rs index 75b385d59f..ffe956e005 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_array_metadata_value_all_of.rs index 189f427f2c..a320269f49 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_metadata_value.rs index eaa4f6c882..5a4fc7aee9 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_metadata_value_all_of.rs index 44c68a6857..b213d17128 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/string_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type.rs index cccb8775a8..c015771417 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type_filter.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type_filter.rs index 5f59095d6d..7b6e7ec9dd 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type_filter.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type_filter.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type_filter_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type_filter_all_of.rs index 821623abee..c12b9063b2 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type_filter_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/system_type_filter_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_array_metadata_value.rs index c57db398be..bdb31510a3 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_array_metadata_value_all_of.rs index a27b56b41a..83aacb2324 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_metadata_value.rs index 34d490e1d3..99c1190318 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_metadata_value_all_of.rs index ec99807c7c..8656facfa1 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u32_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_array_metadata_value.rs index 4f76986335..a870cf1dc2 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_array_metadata_value_all_of.rs index 01fd4b0159..a99e6bcfaa 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_metadata_value.rs index 32e0f37bd8..fc695a8d45 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_metadata_value_all_of.rs index 517b1c23c0..0caba5c0f0 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u64_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_array_metadata_value.rs index 22a16e87fb..43aea56853 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_array_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_array_metadata_value_all_of.rs index ec1bd0ef03..bd66213716 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_array_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_array_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_metadata_value.rs index b7ab80603f..b2a6c5041e 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_metadata_value_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_metadata_value_all_of.rs index 6fe09c77ee..b4a49c9144 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_metadata_value_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/u8_metadata_value_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/unversioned_blueprint_reference.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/unversioned_blueprint_reference.rs index f2352456c5..42dcd09413 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/unversioned_blueprint_reference.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/unversioned_blueprint_reference.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/url_array_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/url_array_metadata_value.rs index 4a79978ac1..2c20dbb7f4 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/url_array_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/url_array_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/url_metadata_value.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/url_metadata_value.rs index 1b275e7163..88642b69d6 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/url_metadata_value.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/url_metadata_value.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/version_ledger_state_selector.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/version_ledger_state_selector.rs index ec6436996a..db0d390b1d 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/version_ledger_state_selector.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/version_ledger_state_selector.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/version_ledger_state_selector_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/version_ledger_state_selector_all_of.rs index 0d8116f8a6..0521935ca8 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/version_ledger_state_selector_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/version_ledger_state_selector_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/well_known_type_reference.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/well_known_type_reference.rs index e75420bcfa..156f10f066 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/well_known_type_reference.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/well_known_type_reference.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/well_known_type_reference_all_of.rs b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/well_known_type_reference_all_of.rs index 6bb6b0f158..a95cbb92f8 100644 --- a/core-rust/engine-state-api-server/src/engine_state_api/generated/models/well_known_type_reference_all_of.rs +++ b/core-rust/engine-state-api-server/src/engine_state_api/generated/models/well_known_type_reference_all_of.rs @@ -1,9 +1,9 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * Generated by: https://openapi-generator.tech */ diff --git a/core-rust/state-manager/src/transaction/preparation.rs b/core-rust/state-manager/src/transaction/preparation.rs index f6facf6d00..3cc449375f 100644 --- a/core-rust/state-manager/src/transaction/preparation.rs +++ b/core-rust/state-manager/src/transaction/preparation.rs @@ -278,7 +278,7 @@ impl Preparator { for raw_ancestor in prepare_request.ancestor_transactions { // TODO(optimization-only): We could avoid the hashing, decoding, signature verification - // and executable creation) by accessing the execution cache in a more clever way. + // and executable creation by accessing the execution cache in a more clever way. let validated = self .ledger_transaction_validator .validate_user_or_round_update_from_raw(&raw_ancestor) diff --git a/core-rust/state-manager/src/transaction/validation.rs b/core-rust/state-manager/src/transaction/validation.rs index 21b8b7e6d1..298c5b1b7e 100644 --- a/core-rust/state-manager/src/transaction/validation.rs +++ b/core-rust/state-manager/src/transaction/validation.rs @@ -106,8 +106,8 @@ impl LedgerTransactionValidator { PreparedLedgerTransactionInner::RoundUpdateV1(prepared) => { ValidatedLedgerTransactionInner::RoundUpdateV1(prepared) } - PreparedLedgerTransactionInner::FlashV1(prepared) => { - ValidatedLedgerTransactionInner::FlashV1(prepared) + PreparedLedgerTransactionInner::FlashV1(_) => { + return Err(LedgerTransactionValidationError::FlashTransactionProvided); } }; Ok(ValidatedLedgerTransaction { @@ -147,6 +147,7 @@ impl LedgerTransactionValidator { pub enum LedgerTransactionValidationError { ValidationError(TransactionValidationError), GenesisTransactionProvided, + FlashTransactionProvided, } impl LedgerTransactionValidationError { @@ -157,6 +158,9 @@ impl LedgerTransactionValidationError { LedgerTransactionValidationError::GenesisTransactionProvided => { panic!("into_user_validation_error called on a genesis transaction payload") } + LedgerTransactionValidationError::FlashTransactionProvided => { + panic!("into_user_validation_error called on a flash transaction payload") + } } } } diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/Address.java b/core/src/main/java/com/radixdlt/api/system/generated/models/Address.java index 3e1e0e57db..42cf722aee 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/Address.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/Address.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/AddressBookEntry.java b/core/src/main/java/com/radixdlt/api/system/generated/models/AddressBookEntry.java index e723d397d6..0d4be7d434 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/AddressBookEntry.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/AddressBookEntry.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/BFTConfiguration.java b/core/src/main/java/com/radixdlt/api/system/generated/models/BFTConfiguration.java index 297680ea83..435560c73b 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/BFTConfiguration.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/BFTConfiguration.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/CreateDbCheckpointResponse.java b/core/src/main/java/com/radixdlt/api/system/generated/models/CreateDbCheckpointResponse.java index 61bf44126d..f426c4a786 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/CreateDbCheckpointResponse.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/CreateDbCheckpointResponse.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/EmptyPendingProtocolUpdateState.java b/core/src/main/java/com/radixdlt/api/system/generated/models/EmptyPendingProtocolUpdateState.java index ea12b63b17..1c568128cf 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/EmptyPendingProtocolUpdateState.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/EmptyPendingProtocolUpdateState.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochIfValidatorsReadyCondition.java b/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochIfValidatorsReadyCondition.java index 7862409ba4..aae0b6b036 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochIfValidatorsReadyCondition.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochIfValidatorsReadyCondition.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochIfValidatorsReadyConditionAllOf.java b/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochIfValidatorsReadyConditionAllOf.java index 2e5b0e8fed..fe39f6102d 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochIfValidatorsReadyConditionAllOf.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochIfValidatorsReadyConditionAllOf.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochUnconditionallyCondition.java b/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochUnconditionallyCondition.java index aaf1cb1883..2f8ca46b46 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochUnconditionallyCondition.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochUnconditionallyCondition.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochUnconditionallyConditionAllOf.java b/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochUnconditionallyConditionAllOf.java index 14c763a35c..4a02ff93d1 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochUnconditionallyConditionAllOf.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/EnactAtStartOfEpochUnconditionallyConditionAllOf.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/EnactedProtocolUpdate.java b/core/src/main/java/com/radixdlt/api/system/generated/models/EnactedProtocolUpdate.java index 0e25800d2a..2d2521a915 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/EnactedProtocolUpdate.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/EnactedProtocolUpdate.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/Error.java b/core/src/main/java/com/radixdlt/api/system/generated/models/Error.java index d53d2589b9..bc765a5923 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/Error.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/Error.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/HealthResponse.java b/core/src/main/java/com/radixdlt/api/system/generated/models/HealthResponse.java index 0f318019af..4899ee2359 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/HealthResponse.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/HealthResponse.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/IdentityResponse.java b/core/src/main/java/com/radixdlt/api/system/generated/models/IdentityResponse.java index a5bcd26663..1b1a5b992f 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/IdentityResponse.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/IdentityResponse.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/MempoolConfiguration.java b/core/src/main/java/com/radixdlt/api/system/generated/models/MempoolConfiguration.java index 05298ea22a..92de64d43c 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/MempoolConfiguration.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/MempoolConfiguration.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/NetworkSyncStatusResponse.java b/core/src/main/java/com/radixdlt/api/system/generated/models/NetworkSyncStatusResponse.java index 7d10966b76..e4567f0dc1 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/NetworkSyncStatusResponse.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/NetworkSyncStatusResponse.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/NetworkingConfiguration.java b/core/src/main/java/com/radixdlt/api/system/generated/models/NetworkingConfiguration.java index 49f748d085..5b3982bba7 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/NetworkingConfiguration.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/NetworkingConfiguration.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/Peer.java b/core/src/main/java/com/radixdlt/api/system/generated/models/Peer.java index ce9f97dd76..cc11b2d58e 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/Peer.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/Peer.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/PeerApplicationVersion.java b/core/src/main/java/com/radixdlt/api/system/generated/models/PeerApplicationVersion.java index e2b4b28f40..1107a9db9a 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/PeerApplicationVersion.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/PeerApplicationVersion.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/PeerChannel.java b/core/src/main/java/com/radixdlt/api/system/generated/models/PeerChannel.java index e361303ae7..38d4526281 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/PeerChannel.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/PeerChannel.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdate.java b/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdate.java index 7807ea9e1b..da8fb72659 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdate.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdate.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdateState.java b/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdateState.java index 065b6c0a00..e8ed84f8a9 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdateState.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdateState.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdateStateType.java b/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdateStateType.java index 323f9daea6..51292c767a 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdateStateType.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/PendingProtocolUpdateStateType.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolConfiguration.java b/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolConfiguration.java index 8af8d8f16b..07d720eaf0 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolConfiguration.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolConfiguration.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateEnactmentCondition.java b/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateEnactmentCondition.java index d8cdb6d97c..756df8c9bb 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateEnactmentCondition.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateEnactmentCondition.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateEnactmentConditionType.java b/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateEnactmentConditionType.java index ebe2148ff3..3fa72dd6ea 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateEnactmentConditionType.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateEnactmentConditionType.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateTrigger.java b/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateTrigger.java index ba1595ca4f..fcc976018a 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateTrigger.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/ProtocolUpdateTrigger.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/RecentSelfProposalMissStatistic.java b/core/src/main/java/com/radixdlt/api/system/generated/models/RecentSelfProposalMissStatistic.java index 67e653b4cd..f4ffb26b52 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/RecentSelfProposalMissStatistic.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/RecentSelfProposalMissStatistic.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateState.java b/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateState.java index 33b4244b5f..40877440d3 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateState.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateState.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateStateAllOf.java b/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateStateAllOf.java index 227ac34fc6..a46debc2bd 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateStateAllOf.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateStateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateStateAllOfThresholdsState.java b/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateStateAllOfThresholdsState.java index c5dc51b78c..7daede2c3f 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateStateAllOfThresholdsState.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessPendingProtocolUpdateStateAllOfThresholdsState.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessThreshold.java b/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessThreshold.java index 7e0a8848d7..15b02e7331 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessThreshold.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessThreshold.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessThresholdState.java b/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessThresholdState.java index f89ef0b27f..77912198ec 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessThresholdState.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/SignalledReadinessThresholdState.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/SyncConfiguration.java b/core/src/main/java/com/radixdlt/api/system/generated/models/SyncConfiguration.java index 04a22f05a2..b584576ca3 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/SyncConfiguration.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/SyncConfiguration.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/SyncStatus.java b/core/src/main/java/com/radixdlt/api/system/generated/models/SyncStatus.java index 912eae8e72..f49ae46fc7 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/SyncStatus.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/SyncStatus.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/SystemAddressBookResponse.java b/core/src/main/java/com/radixdlt/api/system/generated/models/SystemAddressBookResponse.java index f84a5dd672..aa389fc6fe 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/SystemAddressBookResponse.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/SystemAddressBookResponse.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/SystemConfigurationResponse.java b/core/src/main/java/com/radixdlt/api/system/generated/models/SystemConfigurationResponse.java index 3d47dc73f1..cc97acf3ff 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/SystemConfigurationResponse.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/SystemConfigurationResponse.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/SystemPeersResponse.java b/core/src/main/java/com/radixdlt/api/system/generated/models/SystemPeersResponse.java index 007e164cd0..14183b2d86 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/SystemPeersResponse.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/SystemPeersResponse.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/UnknownReportedPendingProtocolUpdate.java b/core/src/main/java/com/radixdlt/api/system/generated/models/UnknownReportedPendingProtocolUpdate.java index 25bd2cb002..20d9631082 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/UnknownReportedPendingProtocolUpdate.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/UnknownReportedPendingProtocolUpdate.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/generated/models/VersionResponse.java b/core/src/main/java/com/radixdlt/api/system/generated/models/VersionResponse.java index 43fe4a73dd..abffebbbec 100644 --- a/core/src/main/java/com/radixdlt/api/system/generated/models/VersionResponse.java +++ b/core/src/main/java/com/radixdlt/api/system/generated/models/VersionResponse.java @@ -1,8 +1,8 @@ /* - * Radix System API - Babylon (Anemone) + * Radix System API * This API is exposed by the Babylon Radix node to give clients access to information about the node itself, its configuration, status and subsystems. It is intended for use by node-runners on a private network, and is not intended to be exposed publicly. Heavy load may impact the node's function. If you require queries against ledger state, you may also wish to consider using the [Core API or Gateway API instead](https://docs-babylon.radixdlt.com/main/apis/api-specification.html). * - * The version of the OpenAPI document: v1.2.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/main/java/com/radixdlt/api/system/system-api-schema.yaml b/core/src/main/java/com/radixdlt/api/system/system-api-schema.yaml index 9ea1a0ad3a..24e0bdf5d2 100644 --- a/core/src/main/java/com/radixdlt/api/system/system-api-schema.yaml +++ b/core/src/main/java/com/radixdlt/api/system/system-api-schema.yaml @@ -1,8 +1,8 @@ openapi: 3.0.0 info: # Should be the release version, and the release display name - version: 'v1.2.1' - title: 'Radix System API - Babylon (Anemone)' + version: 'v1.2.3' + title: 'Radix System API' license: name: The Radix License, Version 1.0 url: https://www.radixfoundation.org/licenses/license-v1 diff --git a/core/src/main/java/com/radixdlt/p2p/hostip/NetworkQueryHostIp.java b/core/src/main/java/com/radixdlt/p2p/hostip/NetworkQueryHostIp.java index 1eb455310d..879a9255e3 100644 --- a/core/src/main/java/com/radixdlt/p2p/hostip/NetworkQueryHostIp.java +++ b/core/src/main/java/com/radixdlt/p2p/hostip/NetworkQueryHostIp.java @@ -67,9 +67,11 @@ import com.google.common.annotations.VisibleForTesting; import com.google.common.base.Suppliers; import com.google.common.collect.ImmutableList; +import com.google.common.collect.ImmutableMap; import com.google.common.collect.Maps; -import com.google.common.net.HostAndPort; +import com.radixdlt.lang.Result; import com.radixdlt.utils.properties.RuntimeProperties; +import java.io.IOException; import java.net.MalformedURLException; import java.net.URL; import java.util.ArrayList; @@ -92,7 +94,9 @@ final class NetworkQueryHostIp { private static final Logger log = LogManager.getLogger(); - public record Result(Optional maybeHostIp, ImmutableList hostsQueried) {} + public record VotedResult( + Optional conclusiveHostIp, + ImmutableMap> individualQueryResults) {} @VisibleForTesting static final String QUERY_URLS_PROPERTY = "network.host_ip_query_urls"; @@ -125,7 +129,7 @@ static NetworkQueryHostIp create(RuntimeProperties properties) { private final List hosts; private final OkHttpClient okHttpClient; - private final Supplier result = Suppliers.memoize(this::get); + private final Supplier result = Suppliers.memoize(this::get); NetworkQueryHostIp(Collection urls) { if (urls.isEmpty()) { @@ -139,54 +143,61 @@ int count() { return this.hosts.size(); } - public Result queryNetworkHosts() { + public VotedResult queryNetworkHosts() { return result.get(); } - Result get() { + VotedResult get() { return publicIp((count() + 1) / 2); // Round up } - Result publicIp(int threshold) { + VotedResult publicIp(int threshold) { // Make sure we don't DoS the first one on the list Collections.shuffle(this.hosts); log.debug("Using hosts {}", this.hosts); - final Map ips = Maps.newHashMap(); - final ImmutableList.Builder hostsQueried = ImmutableList.builder(); + final Map successCounts = Maps.newHashMap(); + final ImmutableMap.Builder> queryResults = + ImmutableMap.builder(); for (URL url : this.hosts) { - HostAndPort q = query(url); - if (q != null) { - hostsQueried.add(url); - int newValue = ips.computeIfAbsent(q, k -> new AtomicInteger()).incrementAndGet(); - if (newValue >= threshold) { - log.debug("Found address {}", q); - return new Result(Optional.of(new HostIp(q.getHost())), hostsQueried.build()); + final Result result = query(url); + queryResults.put(url, result); + final Optional success = result.toOptional(); + if (success.isPresent()) { + int newCount = + successCounts + .computeIfAbsent(success.get(), k -> new AtomicInteger()) + .incrementAndGet(); + if (newCount >= threshold) { + log.debug("Found address {}", success.get()); + return new VotedResult(success, queryResults.build()); } } } log.debug("No suitable address found"); - return new Result(Optional.empty(), hostsQueried.build()); + return new VotedResult(Optional.empty(), queryResults.build()); } - HostAndPort query(URL url) { + Result query(URL url) { try { - final var response = - okHttpClient - .newCall( - new Request.Builder() - .url(url) - .header( - "User-Agent", "curl/7.58.0") // User agent is required by some services - .header( - "Accept", "*/*") // Similarly, this seems to be required by some services - .get() - .build()) - .execute(); - return HostAndPort.fromHost(response.body().string().trim()); - } catch (Exception ex) { - // We don't want any single query to throw an uncaught exception - // (e.g. if they return an invalid response), so we're just catching all here. - return null; + // Some services simply require the headers we set here: + final var request = + new Request.Builder() + .url(url) + .header("User-Agent", "Mozilla/5.0") + .header("Accept", "text/plain,text/html") + .header("Accept-Encoding", "deflate,gzip,identity") + .header("Accept-Language", "en-GB,en-US") + .get() + .build(); + final var call = okHttpClient.newCall(request); + try (var response = call.execute()) { + if (!response.isSuccessful()) { + return Result.error(new IOException("Not a success: %s".formatted(response))); + } + return Result.success(new HostIp(response.body().string().trim())); + } + } catch (IOException ex) { + return Result.error(ex); } } diff --git a/core/src/main/java/com/radixdlt/p2p/hostip/StandardHostIp.java b/core/src/main/java/com/radixdlt/p2p/hostip/StandardHostIp.java index e1a03f4866..5acfdc63aa 100644 --- a/core/src/main/java/com/radixdlt/p2p/hostip/StandardHostIp.java +++ b/core/src/main/java/com/radixdlt/p2p/hostip/StandardHostIp.java @@ -98,14 +98,14 @@ public static HostIp defaultHostIp(RuntimeProperties properties) { } else if (configuredHostIps.size() == 0) { final var networkQueryResult = NetworkQueryHostIp.create(properties).queryNetworkHosts(); - if (networkQueryResult.maybeHostIp().isPresent()) { + if (networkQueryResult.conclusiveHostIp().isPresent()) { // All good, we have an IP address from network query log.info( "Host's public IP address has been acquired from an external oracle (services queried:" + " {}). Consider setting a `network.host_ip` property instead to lessen reliance" + " on external services.", - networkQueryResult.hostsQueried()); - return networkQueryResult.maybeHostIp().orElseThrow(); + networkQueryResult.individualQueryResults()); + return networkQueryResult.conclusiveHostIp().orElseThrow(); } else { throw new RuntimeException( String.format( @@ -113,7 +113,7 @@ public static HostIp defaultHostIp(RuntimeProperties properties) { + "Make sure you set your `network.host_ip` property. " + "An attempt was made to acquire it from an external oracle, " + "but that also failed (services queried: %s).", - networkQueryResult.hostsQueried())); + networkQueryResult.individualQueryResults())); } } else { // We've got a configured IP and possibly also an IP address from an external oracle @@ -134,7 +134,7 @@ public static HostIp defaultHostIp(RuntimeProperties properties) { } else { // Non-local address was configured, so let's query the oracle and see if it matches final var networkQueryResult = NetworkQueryHostIp.create(properties).queryNetworkHosts(); - if (networkQueryResult.maybeHostIp().stream() + if (networkQueryResult.conclusiveHostIp().stream() .anyMatch(hostIpFromNetwork -> !hostIpFromNetwork.equals(configuredHostIp))) { log.warn( "An IP address that was configured for this node ({}) differs from a public IP " @@ -143,8 +143,8 @@ public static HostIp defaultHostIp(RuntimeProperties properties) { + "Make sure your `network.host_ip` property or " + "`RADIXDLT_HOST_IP_ADDRESS` environment variable are set correctly.", configuredHostIp, - networkQueryResult.maybeHostIp().orElseThrow(), - networkQueryResult.hostsQueried()); + networkQueryResult.conclusiveHostIp().orElseThrow(), + networkQueryResult.individualQueryResults()); } log.info("Using a configured host IP address: {}", configuredHostIp); diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/api/LtsApi.java b/core/src/test-core/java/com/radixdlt/api/core/generated/api/LtsApi.java index a603e05dc9..f7267a827b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/api/LtsApi.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/api/LtsApi.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/api/MempoolApi.java b/core/src/test-core/java/com/radixdlt/api/core/generated/api/MempoolApi.java index aa805db612..67dc22bbf5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/api/MempoolApi.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/api/MempoolApi.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/api/StateApi.java b/core/src/test-core/java/com/radixdlt/api/core/generated/api/StateApi.java index 7b7e1d741a..f36e9897a6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/api/StateApi.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/api/StateApi.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/api/StatusApi.java b/core/src/test-core/java/com/radixdlt/api/core/generated/api/StatusApi.java index ca7d6184fc..c7c2b08297 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/api/StatusApi.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/api/StatusApi.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/api/StreamApi.java b/core/src/test-core/java/com/radixdlt/api/core/generated/api/StreamApi.java index f2cef876c0..0bd88cfe69 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/api/StreamApi.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/api/StreamApi.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/api/TransactionApi.java b/core/src/test-core/java/com/radixdlt/api/core/generated/api/TransactionApi.java index 7ed646e8ce..65ed145c26 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/api/TransactionApi.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/api/TransactionApi.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiClient.java b/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiClient.java index 9a16cb89ef..ab19e00a9e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiClient.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiClient.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiException.java b/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiException.java index 8f763de879..baf3ceff74 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiException.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiException.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiResponse.java index f729421eae..cbf35b1662 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/client/ApiResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/client/Configuration.java b/core/src/test-core/java/com/radixdlt/api/core/generated/client/Configuration.java index c80c6ebc55..08769d41c2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/client/Configuration.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/client/Configuration.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/client/Pair.java b/core/src/test-core/java/com/radixdlt/api/core/generated/client/Pair.java index 96f2126ec2..f095098e37 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/client/Pair.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/client/Pair.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/client/RFC3339DateFormat.java b/core/src/test-core/java/com/radixdlt/api/core/generated/client/RFC3339DateFormat.java index aa36495225..8652d6ede6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/client/RFC3339DateFormat.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/client/RFC3339DateFormat.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AbstractOpenApiSchema.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AbstractOpenApiSchema.java index 1f65cd4029..8048471fb6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AbstractOpenApiSchema.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AbstractOpenApiSchema.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateSubstate.java index 00a94f63f7..678006aafb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateSubstateAllOf.java index 61115b3c92..a21b67ec6f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateValue.java index 98b3ae1f95..49574acbbc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessControllerFieldStateValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRule.java index b00a10f9d3..13e3e25928 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleNode.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleNode.java index 085a4d3022..60783cbfbb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleNode.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleNode.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleNodeType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleNodeType.java index e9b8565679..76917543f0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleNodeType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleNodeType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleType.java index da53d4584c..c0c40d93a9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccessRuleType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAddressKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAddressKey.java index 991ae8e3a4..782488c05b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAddressKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAddressKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntrySubstate.java index 7c5a8102a4..f598068d52 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntrySubstateAllOf.java index b221c16850..e707265bd3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntryValue.java index 819da2d35f..9ff667c996 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountAuthorizedDepositorEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateSubstate.java index da3b94d231..a481215bef 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateSubstateAllOf.java index 4baeebd074..eb130d304b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateValue.java index fabb1734ae..6a43e7cac0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountFieldStateValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntrySubstate.java index 68cbc3812d..7d20c2c4bb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntrySubstateAllOf.java index 0e3d38a7b3..d19f9ce53f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntryValue.java index 8a3068d547..dcf1b4685a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountLockerAccountClaimsEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntrySubstate.java index ba0a251bdd..5cc69dfdda 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntrySubstateAllOf.java index fa79802a37..dba325adc3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntryValue.java index ebdfae33d3..70040702b4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountResourcePreferenceEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntrySubstate.java index 67245731ab..b4af741969 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntrySubstateAllOf.java index 3379aaf9cb..9f3d8babd9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntryValue.java index 9b86d905b6..7b6f7d6746 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AccountVaultEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidator.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidator.java index 4cbda5dfbd..a7e554f1ec 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidator.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidator.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidatorIndex.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidatorIndex.java index 1533deabc5..afbff413c4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidatorIndex.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidatorIndex.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidatorKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidatorKey.java index fd06ff7bb0..4c6b8a946c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidatorKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ActiveValidatorKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AddressType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AddressType.java index cd31880a4b..17656c2d80 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AddressType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AddressType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfAccessRuleNode.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfAccessRuleNode.java index b2a0518c32..07aa7c2a73 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfAccessRuleNode.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfAccessRuleNode.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfProofRule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfProofRule.java index f8b1b9a96f..4cc06da5df 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfProofRule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfProofRuleAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfProofRuleAllOf.java index 883ab679ac..81391ae3d5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfProofRuleAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllOfProofRuleAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllowAllAccessRule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllowAllAccessRule.java index 827e286b71..cd8875cbfb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllowAllAccessRule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AllowAllAccessRule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AmountOfProofRule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AmountOfProofRule.java index 7f2154d678..ca53809314 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AmountOfProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AmountOfProofRule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AmountOfProofRuleAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AmountOfProofRuleAllOf.java index 76e65adc4b..aa7128d00e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AmountOfProofRuleAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AmountOfProofRuleAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfAccessRuleNode.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfAccessRuleNode.java index c810a3ecae..7795822a87 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfAccessRuleNode.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfAccessRuleNode.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfAccessRuleNodeAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfAccessRuleNodeAllOf.java index af900192a8..2a6362cbbd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfAccessRuleNodeAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfAccessRuleNodeAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfProofRule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfProofRule.java index cdfe22816f..d810e8d789 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AnyOfProofRule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AttachedModuleId.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AttachedModuleId.java index 4470981f72..5b6c22549e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AttachedModuleId.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AttachedModuleId.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthConfig.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthConfig.java index b8015d07ad..4321cab939 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthConfig.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthConfig.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorBadge.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorBadge.java index 8b51474ce1..224b91e348 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorBadge.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorBadge.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorBadgeType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorBadgeType.java index afc47483c7..8392bd4ce2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorBadgeType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorBadgeType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorKey.java index 6e12996766..729b4ce418 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/AuthorizedDepositorKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BasicErrorResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BasicErrorResponse.java index d8514f45b9..e0e84f3e22 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BasicErrorResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BasicErrorResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BinaryPlaintextMessageContent.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BinaryPlaintextMessageContent.java index 7fc238feb1..d57207817b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BinaryPlaintextMessageContent.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BinaryPlaintextMessageContent.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BinaryPlaintextMessageContentAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BinaryPlaintextMessageContentAllOf.java index 6e39dbe9eb..d7e6c69ae7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BinaryPlaintextMessageContentAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BinaryPlaintextMessageContentAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintCollectionSchema.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintCollectionSchema.java index 4e6a09e60d..397ebbc7fa 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintCollectionSchema.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintCollectionSchema.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintCollectionSchemaType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintCollectionSchemaType.java index f2252be1ee..dd4a8c7d21 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintCollectionSchemaType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintCollectionSchemaType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintDefinition.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintDefinition.java index 10e86cec59..83fe375c06 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintDefinition.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintDefinition.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintDependencies.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintDependencies.java index a79e27bf88..c54ed8323b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintDependencies.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintDependencies.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintFunctionTargetIdentifier.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintFunctionTargetIdentifier.java index 86684b0665..7331dbc49a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintFunctionTargetIdentifier.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintFunctionTargetIdentifier.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintFunctionTargetIdentifierAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintFunctionTargetIdentifierAllOf.java index b30c1a3326..e2e202ca57 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintFunctionTargetIdentifierAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintFunctionTargetIdentifierAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintInfo.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintInfo.java index eabbd2b1e0..a3ee711e61 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintInfo.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintInterface.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintInterface.java index 8e7548193b..2379c478ef 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintInterface.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintInterface.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintMethodRoyalty.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintMethodRoyalty.java index 66f241331c..b16bb98a84 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintMethodRoyalty.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintMethodRoyalty.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintPayloadDef.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintPayloadDef.java index bfa59091c4..408e8e6d43 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintPayloadDef.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintPayloadDef.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintPayloadDefType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintPayloadDefType.java index eece46b273..e6f5ba0b5b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintPayloadDefType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintPayloadDefType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintRoyaltyConfig.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintRoyaltyConfig.java index f767e9a47e..acf9b4b30a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintRoyaltyConfig.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintRoyaltyConfig.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaBlueprintTypeReference.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaBlueprintTypeReference.java index 6f1678a20e..58b8a00ec2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaBlueprintTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaBlueprintTypeReference.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaBlueprintTypeReferenceAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaBlueprintTypeReferenceAllOf.java index 64dd856504..fdbb904327 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaBlueprintTypeReferenceAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaBlueprintTypeReferenceAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaCollectionPartition.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaCollectionPartition.java index 0898a284fc..4a94b33223 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaCollectionPartition.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaCollectionPartition.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaFieldPartition.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaFieldPartition.java index b25e55f515..bd038b2412 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaFieldPartition.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintSchemaFieldPartition.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeIdentifier.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeIdentifier.java index 46c6e6dcce..1bc50577d9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeIdentifier.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeIdentifier.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeReference.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeReference.java index edffabc5f1..e6a8c19e4e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeReference.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeReferenceKind.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeReferenceKind.java index b483c91658..b0f52444c6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeReferenceKind.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintTypeReferenceKind.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintVersionKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintVersionKey.java index 548a10b0bb..d17212bcc0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintVersionKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BlueprintVersionKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldKernelBootSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldKernelBootSubstate.java index f10ad2fab1..b1cd897eaf 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldKernelBootSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldKernelBootSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldKernelBootSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldKernelBootSubstateAllOf.java index 636c953497..dac20804ed 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldKernelBootSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldKernelBootSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootSubstate.java index 6769b90493..0e833866c8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootSubstateAllOf.java index 4fbaf93a6a..83aeba3ec7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootValue.java index 5b2d77f616..f37435bc62 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldSystemBootValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootSubstate.java index 0580f45110..08b676d281 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootSubstateAllOf.java index 23f2bbb4cb..5850c82cfc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootValue.java index 2c86928e3b..b75e1c7f64 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/BootLoaderModuleFieldVmBootValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedIntentMetadata.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedIntentMetadata.java index 56b45d4db2..37d403be60 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedIntentMetadata.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedIntentMetadata.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedStateIdentifier.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedStateIdentifier.java index aba02cc296..483a37e2eb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedStateIdentifier.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedStateIdentifier.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedTransaction.java index 0fb4231c41..6d27f53f13 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedTransactionBalanceChanges.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedTransactionBalanceChanges.java index c89b7583fb..25e36a09d1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedTransactionBalanceChanges.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CommittedTransactionBalanceChanges.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ComponentMethodTargetIdentifier.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ComponentMethodTargetIdentifier.java index 2062018dbb..067b9de4c0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ComponentMethodTargetIdentifier.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ComponentMethodTargetIdentifier.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ComponentMethodTargetIdentifierAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ComponentMethodTargetIdentifierAllOf.java index 960f7de373..fcf886218f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ComponentMethodTargetIdentifierAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ComponentMethodTargetIdentifierAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusLedgerProofOrigin.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusLedgerProofOrigin.java index c2a61d8324..ac8614c4ce 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusLedgerProofOrigin.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusLedgerProofOrigin.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusLedgerProofOriginAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusLedgerProofOriginAllOf.java index c1b7583e47..54e544f1bd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusLedgerProofOriginAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusLedgerProofOriginAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigSubstate.java index b300bdc0fa..b1663b19ff 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigSubstateAllOf.java index 1a81b74f3d..b30bb2d5a7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigValue.java index 8fee1bd731..c26e59c310 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldConfigValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstate.java index 2f92d4225d..19e1b4bb9a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstateAllOf.java index dafcbfb799..b95f40605e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticValue.java index 1852d2ced9..39409cfb36 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentProposalStatisticValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstate.java index 8a0fc57a2d..2e79ba701c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstateAllOf.java index e6851199b7..cf2541ba26 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesValue.java index 44102e82f6..cb64dbaa17 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeSubstate.java index 89cb404767..b3ed7de127 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeSubstateAllOf.java index 0788ac0a2a..e6730c1885 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeValue.java index 3ed7ffb0a2..e16d7640ef 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentTimeValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstate.java index 18c643775c..fadd5b7e2f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstateAllOf.java index 987ac7ae98..9628ee7651 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetValue.java index bf4e88c7ae..b993a109f9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldCurrentValidatorSetValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateSubstate.java index e90091fd7e..ee892a868f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateSubstateAllOf.java index ed775903ea..4edf010503 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateValue.java index ad0ab6fa99..511df41cbe 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldStateValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsSubstate.java index 2e65296917..b463329b57 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsSubstateAllOf.java index f25d0a70d4..c01659fc23 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsValue.java index 72935dc186..ae04f4d13b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerFieldValidatorRewardsValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstate.java index c69a363fea..0f45335c53 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstateAllOf.java index e14a18aa58..e242484c3f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.java index 6d9c024e70..8ebe79176e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CostingModuleConfig.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CostingModuleConfig.java index 925a6c9d07..cf0ecd18d7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CostingModuleConfig.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CostingModuleConfig.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CostingParameters.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CostingParameters.java index f5686be236..d02da839ea 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CostingParameters.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CostingParameters.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CountOfProofRule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CountOfProofRule.java index 561bcbe7c6..c8981ffd89 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CountOfProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CountOfProofRule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CountOfProofRuleAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CountOfProofRuleAllOf.java index 98f2667d93..47275f12cc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CountOfProofRuleAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CountOfProofRuleAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CreatedSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CreatedSubstate.java index 26cbb9ae5c..e85f0354d7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/CreatedSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/CreatedSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/DataStruct.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/DataStruct.java index 61e57a6a3f..ca44a4bdcf 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/DataStruct.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/DataStruct.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/DefaultDepositRule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/DefaultDepositRule.java index 5c55462600..f9138e51e8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/DefaultDepositRule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/DefaultDepositRule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/DeletedSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/DeletedSubstate.java index f6f88c4075..f8eba51320 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/DeletedSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/DeletedSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/DenyAllAccessRule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/DenyAllAccessRule.java index 4e48f9ebbc..7984af20bf 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/DenyAllAccessRule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/DenyAllAccessRule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1PublicKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1PublicKey.java index 8cb6aa26c4..5ba43d53a3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1PublicKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1PublicKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1PublicKeyAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1PublicKeyAllOf.java index b9bedfc5ae..d99491f615 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1PublicKeyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1PublicKeyAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1Signature.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1Signature.java index 108c357c1b..9dfa264ae4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1Signature.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1Signature.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureAllOf.java index 9f95be1d2c..3a7a6ee105 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureWithPublicKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureWithPublicKey.java index 6a5bf48a72..c5cf7b09d1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureWithPublicKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureWithPublicKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureWithPublicKeyAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureWithPublicKeyAllOf.java index e0624b698b..6727284123 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureWithPublicKeyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EcdsaSecp256k1SignatureWithPublicKeyAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519PublicKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519PublicKey.java index 4b75e8868b..c7cc5932e0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519PublicKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519PublicKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519PublicKeyAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519PublicKeyAllOf.java index 6938b53076..d084fe1ea3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519PublicKeyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519PublicKeyAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519Signature.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519Signature.java index 8b07e61ba3..bb93f3e628 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519Signature.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519Signature.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureAllOf.java index c76505adb4..f637d5fb90 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureWithPublicKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureWithPublicKey.java index 81c687da3e..a8e13af26b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureWithPublicKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureWithPublicKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureWithPublicKeyAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureWithPublicKeyAllOf.java index 8814d7a352..5ec4206ec5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureWithPublicKeyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EddsaEd25519SignatureWithPublicKeyAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedMessageCurveDecryptorSet.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedMessageCurveDecryptorSet.java index cc4eacdd32..d9fdd0f8ae 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedMessageCurveDecryptorSet.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedMessageCurveDecryptorSet.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedMessageDecryptor.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedMessageDecryptor.java index b1800bc094..4052bf1b51 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedMessageDecryptor.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedMessageDecryptor.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedTransactionMessage.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedTransactionMessage.java index 946b68edc8..656f9e7bef 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedTransactionMessage.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedTransactionMessage.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedTransactionMessageAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedTransactionMessageAllOf.java index 4722422bd9..d5bcd68221 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedTransactionMessageAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EncryptedTransactionMessageAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityModule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityModule.java index 5d3eeb9895..45aeabc968 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityModule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityModule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityReference.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityReference.java index eb526d00f8..316718eeb0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityReference.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityReference.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityType.java index 98477620a6..a993a1e3ea 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EntityType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochChangeCondition.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochChangeCondition.java index b92e1803a4..4f682e2a5e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochChangeCondition.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochChangeCondition.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochEndLedgerProof.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochEndLedgerProof.java index 8737656eca..f619a8927f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochEndLedgerProof.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochEndLedgerProof.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochRound.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochRound.java index 85da4e65d0..2f52e9f09c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochRound.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EpochRound.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ErrorResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ErrorResponse.java index 7eaadb3376..bc5f880b49 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ErrorResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ErrorResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ErrorResponseType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ErrorResponseType.java index 6d6cc6bcc4..8b2ae10b20 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ErrorResponseType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ErrorResponseType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/Event.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/Event.java index 16692f6694..f55ca1a3b2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/Event.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/Event.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventEmitterIdentifier.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventEmitterIdentifier.java index 32d883d16f..6a7a51ea2f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventEmitterIdentifier.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventEmitterIdentifier.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventEmitterIdentifierType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventEmitterIdentifierType.java index 3e69a5c9ab..f8954eb5fe 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventEmitterIdentifierType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventEmitterIdentifierType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventTypeIdentifier.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventTypeIdentifier.java index 0f71e798c4..4ec0d45abf 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventTypeIdentifier.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/EventTypeIdentifier.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ExecutedScenario.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ExecutedScenario.java index 7aeed2be24..af88141f92 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ExecutedScenario.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ExecutedScenario.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ExecutedScenarioTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ExecutedScenarioTransaction.java index fa5161c6c8..c49026f8e6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ExecutedScenarioTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ExecutedScenarioTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeDestination.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeDestination.java index f80e02d82a..36ef82a6c8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeDestination.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeDestination.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeSource.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeSource.java index dc9b6f3b32..94be2af839 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeSource.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeSource.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeSummary.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeSummary.java index 61e79c1bbe..54330cbbbd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeSummary.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FeeSummary.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchema.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchema.java index 4a91f5d099..6353db807e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchema.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchema.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureCondition.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureCondition.java index 7abe545f75..9d7f229f56 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureCondition.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureCondition.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionAlways.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionAlways.java index 316fcae6cf..baa3624fd4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionAlways.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionAlways.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeature.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeature.java index feea057a77..3f827f544b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeature.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeature.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOwnFeature.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOwnFeature.java index a00b804bce..e6a01c76d1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOwnFeature.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOwnFeature.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOwnFeatureAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOwnFeatureAllOf.java index 3c7705099c..c56c12330e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOwnFeatureAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionIfOwnFeatureAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionType.java index e08a7ef46b..4f1fabbab9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSchemaFeatureConditionType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSubstateKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSubstateKey.java index f89960242e..0536ec080f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSubstateKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSubstateKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSubstateKeyAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSubstateKeyAllOf.java index 45cca88678..a5365a908e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSubstateKeyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FieldSubstateKeyAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashLedgerTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashLedgerTransaction.java index 9c3cf99161..3fd45eb2da 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashLedgerTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashLedgerTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashLedgerTransactionAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashLedgerTransactionAllOf.java index 1a23883883..fbabc6b5b9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashLedgerTransactionAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashLedgerTransactionAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashSetSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashSetSubstate.java index 6d64794801..8378cf59ad 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashSetSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashSetSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashedStateUpdates.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashedStateUpdates.java index 2e994557cf..2ad2e9ed2c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashedStateUpdates.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FlashedStateUpdates.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FrozenStatus.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FrozenStatus.java index 5c06d710fd..d261797bf0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FrozenStatus.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FrozenStatus.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FullyScopedTypeId.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FullyScopedTypeId.java index 6779c6c8d2..511a146320 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FullyScopedTypeId.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FullyScopedTypeId.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionAuthType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionAuthType.java index 3957106f81..dbde71654b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionAuthType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionAuthType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionEventEmitterIdentifier.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionEventEmitterIdentifier.java index 389dbbea97..ca39c90ff0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionEventEmitterIdentifier.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionEventEmitterIdentifier.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionEventEmitterIdentifierAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionEventEmitterIdentifierAllOf.java index e3e58ab758..c39e338cb6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionEventEmitterIdentifierAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionEventEmitterIdentifierAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionSchema.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionSchema.java index 3dba664fa1..9766fd789f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionSchema.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FunctionSchema.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceAmount.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceAmount.java index 838374e815..d938a048a8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceAmount.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceAmount.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceAmountAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceAmountAllOf.java index a438ae2f02..23e0f52c4e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceAmountAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceAmountAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilitySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilitySubstate.java index b5290b918c..629b96de94 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilitySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilitySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilitySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilitySubstateAllOf.java index 62039bf186..1711028e1e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilitySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilitySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilityValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilityValue.java index 4bb22b9ac1..e98e13525d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilityValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldDivisibilityValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplySubstate.java index 95183126d7..1dc7876389 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplySubstateAllOf.java index 72c0fed01d..605fc101e3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplyValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplyValue.java index bfdb37db5c..cfee157fee 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplyValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleResourceManagerFieldTotalSupplyValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceSubstate.java index ea6738e6ff..57b2c4fc22 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceSubstateAllOf.java index b7f09bb760..9c24f94eed 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceValue.java index 7f1c62eb92..fe5138b1fc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldBalanceValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusSubstate.java index c2dc76c2e6..de706c5567 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusSubstateAllOf.java index c0cc4768ff..fb35e2fa7f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusValue.java index 2633f402ad..141c7f8429 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/FungibleVaultFieldFrozenStatusValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericBlueprintPayloadDef.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericBlueprintPayloadDef.java index f4793740b5..1b329070ac 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericBlueprintPayloadDef.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericBlueprintPayloadDef.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericBlueprintPayloadDefAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericBlueprintPayloadDefAllOf.java index 6abc5b7164..2b27ded002 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericBlueprintPayloadDefAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericBlueprintPayloadDefAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKey.java index e2427026af..ab7c004414 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntrySubstate.java index 629bcd8c04..41669e9377 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntrySubstateAllOf.java index 7b0629cabd..92745139c6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntryValue.java index a40791ecbd..6854e9ea10 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericKeyValueStoreEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateSubstate.java index 8ee8cd5cb4..ed7ea3bfe9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateSubstateAllOf.java index ca5d87eca4..fafb0881a1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateValue.java index 82b6f06db0..0a2645fb67 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericScryptoComponentFieldStateValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericSubstitution.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericSubstitution.java index 0a806ed1ab..78ae698a7e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericSubstitution.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericSubstitution.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericSubstitutionType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericSubstitutionType.java index fe5f7d9b64..0405fdfe9b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericSubstitutionType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericSubstitutionType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericTypeParameter.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericTypeParameter.java index 517d084a45..4e477d0d81 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericTypeParameter.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericTypeParameter.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericTypeParameterConstraints.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericTypeParameterConstraints.java index 3435651c90..c4ef977d67 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericTypeParameterConstraints.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenericTypeParameterConstraints.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerProofOrigin.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerProofOrigin.java index c06e49a2b5..7ce4c8b520 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerProofOrigin.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerProofOrigin.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerProofOriginAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerProofOriginAllOf.java index 6c029616f0..55ddd99379 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerProofOriginAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerProofOriginAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerTransaction.java index ab1db96842..ddca8a86bf 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerTransactionAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerTransactionAllOf.java index 5e3aa02853..36f1697c2e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerTransactionAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/GenesisLedgerTransactionAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/HookExport.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/HookExport.java index a4be12eaec..41ae9747dd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/HookExport.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/HookExport.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexBlueprintCollectionSchema.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexBlueprintCollectionSchema.java index 38056512fa..80fa4978fd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexBlueprintCollectionSchema.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexBlueprintCollectionSchema.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexBlueprintCollectionSchemaAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexBlueprintCollectionSchemaAllOf.java index 6239050823..35185d2d09 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexBlueprintCollectionSchemaAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexBlueprintCollectionSchemaAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexedStateSchema.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexedStateSchema.java index 996a8af9fb..4d95b1cafa 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexedStateSchema.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/IndexedStateSchema.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstanceSchemaBlueprintTypeReference.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstanceSchemaBlueprintTypeReference.java index c823771717..a75b2a938d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstanceSchemaBlueprintTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstanceSchemaBlueprintTypeReference.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstanceSchemaBlueprintTypeReferenceAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstanceSchemaBlueprintTypeReferenceAllOf.java index cbbf7a7810..5e4a5cea35 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstanceSchemaBlueprintTypeReferenceAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstanceSchemaBlueprintTypeReferenceAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstantMs.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstantMs.java index 9c5076c3bc..b1e277ecce 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstantMs.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstantMs.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstructionResourceChanges.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstructionResourceChanges.java index aa77cdf4a2..36d0df814a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstructionResourceChanges.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/InstructionResourceChanges.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBasedStructure.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBasedStructure.java index 711b35d05f..785d3fc954 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBasedStructure.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBasedStructure.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBlueprintCollectionSchema.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBlueprintCollectionSchema.java index f1127e9345..642185c61a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBlueprintCollectionSchema.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBlueprintCollectionSchema.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBlueprintCollectionSchemaAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBlueprintCollectionSchemaAllOf.java index 09296f951c..c96c038295 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBlueprintCollectionSchemaAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueBlueprintCollectionSchemaAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreEntryStructure.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreEntryStructure.java index 10a4446407..f123abcb4d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreEntryStructure.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreEntryStructure.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreEntryStructureAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreEntryStructureAllOf.java index 643ccbdda5..0f33ddff2e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreEntryStructureAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreEntryStructureAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreInfo.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreInfo.java index ebff507ab9..16184667f0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreInfo.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreTypeInfoDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreTypeInfoDetails.java index e4e9e18510..90b2e0f2e3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreTypeInfoDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreTypeInfoDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreTypeInfoDetailsAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreTypeInfoDetailsAllOf.java index b1f4e5335b..f45bf1557a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreTypeInfoDetailsAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/KeyValueStoreTypeInfoDetailsAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LeaderProposalHistory.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LeaderProposalHistory.java index 4528f2e589..bfe57b0221 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LeaderProposalHistory.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LeaderProposalHistory.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHashes.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHashes.java index c28462b4cd..92307172bd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHashes.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHashes.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHeader.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHeader.java index fbe58b067f..b9fc2bbce5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHeader.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHeader.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHeaderSummary.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHeaderSummary.java index 4e3099fcb7..709a589679 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHeaderSummary.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerHeaderSummary.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProof.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProof.java index f8771f2c0d..a90e4cd2a8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProof.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProof.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProofOrigin.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProofOrigin.java index 1b41a386a7..6f1aefcbe2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProofOrigin.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProofOrigin.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProofOriginType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProofOriginType.java index d5a348443c..3cc8fbee55 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProofOriginType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerProofOriginType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSelector.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSelector.java index bbab3e6e29..9b66d79bb7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSelector.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSelector.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSelectorType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSelectorType.java index 3cfe47eea5..bf2c873e06 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSelectorType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSelectorType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSummary.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSummary.java index 6eb6da24fa..af324de9da 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSummary.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerStateSummary.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerTransaction.java index 4c37f7d6ae..7478c8366e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerTransactionType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerTransactionType.java index e80cf9b6ae..6feca3e29e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerTransactionType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LedgerTransactionType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LimitParameters.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LimitParameters.java index 6515a1eef3..368313b54c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LimitParameters.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LimitParameters.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalGenericSubstitution.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalGenericSubstitution.java index e5cf727a21..e4b2814fc2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalGenericSubstitution.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalGenericSubstitution.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalGenericSubstitutionAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalGenericSubstitutionAllOf.java index c4c2ba267c..b4e91ce4f1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalGenericSubstitutionAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalGenericSubstitutionAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalNonFungibleKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalNonFungibleKey.java index 8cde1ba598..da8f1efeec 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalNonFungibleKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalNonFungibleKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalTypeId.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalTypeId.java index bc69083a7b..4fb0fe2dc4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalTypeId.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LocalTypeId.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsCommittedTransactionOutcome.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsCommittedTransactionOutcome.java index 2d17b4882c..ac2301dedb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsCommittedTransactionOutcome.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsCommittedTransactionOutcome.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsCommittedTransactionStatus.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsCommittedTransactionStatus.java index b62d8eb7a7..c5e6615ec0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsCommittedTransactionStatus.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsCommittedTransactionStatus.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsEntityFungibleBalanceChanges.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsEntityFungibleBalanceChanges.java index c6a69c7f1e..8b48e12cd6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsEntityFungibleBalanceChanges.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsEntityFungibleBalanceChanges.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsEntityNonFungibleBalanceChanges.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsEntityNonFungibleBalanceChanges.java index 8d22f37235..037c88ef91 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsEntityNonFungibleBalanceChanges.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsEntityNonFungibleBalanceChanges.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFeeFungibleResourceBalanceChange.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFeeFungibleResourceBalanceChange.java index defd221f56..fb22313a8c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFeeFungibleResourceBalanceChange.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFeeFungibleResourceBalanceChange.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFeeFungibleResourceBalanceChangeType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFeeFungibleResourceBalanceChangeType.java index ff7b49f4fc..153e8d6f53 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFeeFungibleResourceBalanceChangeType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFeeFungibleResourceBalanceChangeType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFungibleResourceBalance.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFungibleResourceBalance.java index 936bc19d90..a22a5599d6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFungibleResourceBalance.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFungibleResourceBalance.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFungibleResourceBalanceChange.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFungibleResourceBalanceChange.java index 0b4867c132..3293931cbf 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFungibleResourceBalanceChange.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsFungibleResourceBalanceChange.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsResultantAccountFungibleBalances.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsResultantAccountFungibleBalances.java index 2aeefde2ee..4c6b8cb161 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsResultantAccountFungibleBalances.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsResultantAccountFungibleBalances.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsResultantFungibleBalance.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsResultantFungibleBalance.java index 72d11385ef..7ac26bfd54 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsResultantFungibleBalance.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsResultantFungibleBalance.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountAllFungibleResourceBalancesRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountAllFungibleResourceBalancesRequest.java index ad8a189281..ebd93b9e08 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountAllFungibleResourceBalancesRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountAllFungibleResourceBalancesRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountAllFungibleResourceBalancesResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountAllFungibleResourceBalancesResponse.java index 7228acf0c4..7359da0979 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountAllFungibleResourceBalancesResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountAllFungibleResourceBalancesResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountDepositBehaviourRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountDepositBehaviourRequest.java index 7e27ae2b49..035d0928a2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountDepositBehaviourRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountDepositBehaviourRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountDepositBehaviourResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountDepositBehaviourResponse.java index 80328827f6..d812cbc413 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountDepositBehaviourResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountDepositBehaviourResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountFungibleResourceBalanceRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountFungibleResourceBalanceRequest.java index 5f743a9468..a733e388cb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountFungibleResourceBalanceRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountFungibleResourceBalanceRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountFungibleResourceBalanceResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountFungibleResourceBalanceResponse.java index 76f4116339..4399132e65 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountFungibleResourceBalanceResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStateAccountFungibleResourceBalanceResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamAccountTransactionOutcomesRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamAccountTransactionOutcomesRequest.java index a8e5aa2bdd..5ef0d1d14f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamAccountTransactionOutcomesRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamAccountTransactionOutcomesRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamAccountTransactionOutcomesResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamAccountTransactionOutcomesResponse.java index 54dec5e66a..bcc2fd528d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamAccountTransactionOutcomesResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamAccountTransactionOutcomesResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamTransactionOutcomesRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamTransactionOutcomesRequest.java index 09f8bd96f8..34b7a15750 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamTransactionOutcomesRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamTransactionOutcomesRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamTransactionOutcomesResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamTransactionOutcomesResponse.java index e977d45533..700f206fef 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamTransactionOutcomesResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsStreamTransactionOutcomesResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionConstructionRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionConstructionRequest.java index 9f3936b3d0..f43c579bb3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionConstructionRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionConstructionRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionConstructionResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionConstructionResponse.java index c69c2f5479..68ea242324 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionConstructionResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionConstructionResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionIntentStatus.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionIntentStatus.java index 6fe621d4df..8dc97de5ef 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionIntentStatus.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionIntentStatus.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionPayloadDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionPayloadDetails.java index 66f9b872e2..3c97187d7c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionPayloadDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionPayloadDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionPayloadStatus.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionPayloadStatus.java index 7a34112658..8e66a28211 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionPayloadStatus.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionPayloadStatus.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionStatusRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionStatusRequest.java index dc731c0a85..5ccf961d6e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionStatusRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionStatusRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionStatusResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionStatusResponse.java index 1d559a0c86..da3206fe38 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionStatusResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionStatusResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorDetails.java index 133bc24849..625fc15c7b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorDetailsType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorDetailsType.java index ba33bc6d52..3504df32b4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorDetailsType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorDetailsType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorResponse.java index 93b66c135e..690e4a743d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorResponseAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorResponseAllOf.java index 6cb6ba00b8..459ef9aedd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorResponseAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitErrorResponseAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitIntentAlreadyCommitted.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitIntentAlreadyCommitted.java index e4a72672e4..7435f8c3bf 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitIntentAlreadyCommitted.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitIntentAlreadyCommitted.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitIntentAlreadyCommittedAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitIntentAlreadyCommittedAllOf.java index 1ec30d2738..851364257b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitIntentAlreadyCommittedAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitIntentAlreadyCommittedAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.java index bec361fffb..4610f90342 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetailsAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetailsAllOf.java index c76e25cacc..aed11b2636 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetailsAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetailsAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRejectedErrorDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRejectedErrorDetails.java index ace893f47c..acac8a6ea0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRejectedErrorDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRejectedErrorDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRejectedErrorDetailsAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRejectedErrorDetailsAllOf.java index f226ea7a9e..dfc81d19d8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRejectedErrorDetailsAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRejectedErrorDetailsAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRequest.java index 678fb88d2c..d62fa54153 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitResponse.java index 5bc21d30e8..b014730b6f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/LtsTransactionSubmitResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MainMethodKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MainMethodKey.java index e9733dcbf2..72490e31f7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MainMethodKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MainMethodKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MapSubstateKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MapSubstateKey.java index 1dd6f6fd56..88bcacbd2f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MapSubstateKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MapSubstateKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MapSubstateKeyAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MapSubstateKeyAllOf.java index 499d154ba9..8dd47c4f68 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MapSubstateKeyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MapSubstateKeyAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolListRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolListRequest.java index 10ec4bd429..83c5d04c65 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolListRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolListRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolListResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolListResponse.java index 802820d86e..9450890f0d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolListResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolListResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionHashes.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionHashes.java index 0cfeb9e979..e9d55fb366 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionHashes.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionHashes.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionRequest.java index b9f469dc84..5e62c33f2a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionResponse.java index b742fbe161..709c93c42e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionResponsePayloadsInner.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionResponsePayloadsInner.java index 56079679e0..e506c4c7df 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionResponsePayloadsInner.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MempoolTransactionResponsePayloadsInner.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataKey.java index 3d685d0f47..04981706c6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntrySubstate.java index 853a8903af..c738eab9c0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntrySubstateAllOf.java index 42f36d04d9..197ac044be 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntryValue.java index d5544b458c..935f6239d4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MetadataModuleEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAccessibility.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAccessibility.java index 8caa38ec57..4fa4ff762f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAccessibility.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAccessibility.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAccessibilityType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAccessibilityType.java index 9278e397af..4e1aad5471 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAccessibilityType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAccessibilityType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAuthType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAuthType.java index ed36816abf..709b1e3148 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAuthType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodAuthType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodEventEmitterIdentifier.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodEventEmitterIdentifier.java index 038f502799..2c891fe9c1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodEventEmitterIdentifier.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodEventEmitterIdentifier.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodEventEmitterIdentifierAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodEventEmitterIdentifierAllOf.java index e8ac83b8bf..f70e89c4a0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodEventEmitterIdentifierAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MethodEventEmitterIdentifierAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ModuleId.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ModuleId.java index 280aaf7866..e24ce4a4a0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ModuleId.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ModuleId.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ModuleVersion.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ModuleVersion.java index f0929541a2..e06857ddcc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ModuleVersion.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ModuleVersion.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateSubstate.java index ee790fc14d..5a1c9b283b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateSubstateAllOf.java index 3a1d489e8b..5d112a741f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateValue.java index 76e3d0c39a..e615b883d3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MultiResourcePoolFieldStateValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MutableField.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MutableField.java index d7ba4aa1d2..f96a06bf4d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/MutableField.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/MutableField.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponse.java index 7952c89e37..74e38b5597 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponseVersion.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponseVersion.java index f96192a8f0..37973677ac 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponseVersion.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponseVersion.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponseWellKnownAddresses.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponseWellKnownAddresses.java index d10b80f025..d4572a5aa9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponseWellKnownAddresses.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkConfigurationResponseWellKnownAddresses.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkDefinition.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkDefinition.java index 7516f2c2b7..61ef5616bb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkDefinition.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkDefinition.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkStatusRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkStatusRequest.java index 5fe56fc7ef..12c1e0a137 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkStatusRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkStatusRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkStatusResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkStatusResponse.java index deca4f6ae9..778f710e81 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkStatusResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NetworkStatusResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NextEpoch.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NextEpoch.java index 4606bef51a..68194f3394 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NextEpoch.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NextEpoch.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleAuthorizedDepositorBadge.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleAuthorizedDepositorBadge.java index 6d97ab785f..41dda299f6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleAuthorizedDepositorBadge.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleAuthorizedDepositorBadge.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleAuthorizedDepositorBadgeAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleAuthorizedDepositorBadgeAllOf.java index 1db89fdda9..cbf5b45072 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleAuthorizedDepositorBadgeAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleAuthorizedDepositorBadgeAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleGlobalId.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleGlobalId.java index dcc53ed1a6..a7ca69aa8a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleGlobalId.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleGlobalId.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleIdType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleIdType.java index c52f50c682..6740f0ee29 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleIdType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleIdType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleLocalId.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleLocalId.java index 8f6f477465..fde839aa85 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleLocalId.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleLocalId.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungiblePresentedBadge.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungiblePresentedBadge.java index 500b5c56a7..bf51a0d12d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungiblePresentedBadge.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungiblePresentedBadge.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungiblePresentedBadgeAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungiblePresentedBadgeAllOf.java index 421fd2b2df..b3efe00145 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungiblePresentedBadgeAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungiblePresentedBadgeAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleRequirement.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleRequirement.java index d3daab311e..2a1ad9edc1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleRequirement.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleRequirement.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleRequirementAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleRequirementAllOf.java index ab21f65781..1b0d54f6ea 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleRequirementAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleRequirementAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceAmount.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceAmount.java index 915b9037e1..7d6c619868 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceAmount.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceAmount.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceAmountAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceAmountAllOf.java index d2323eebf2..6bc75c36dc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceAmountAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceAmountAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntrySubstate.java index 75b70e2c8a..9920e45c99 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntrySubstateAllOf.java index 87ad6d826a..c62b651dc3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntryValue.java index 7b68c8ef72..e490686e69 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerDataEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeSubstate.java index 332a5f2cc9..846936e7ad 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeSubstateAllOf.java index 0e9787c7e5..4921079c3c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeValue.java index 657beda647..62b69673bf 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldIdTypeValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstate.java index 7811ef5c8c..6277cd8141 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstateAllOf.java index 18e4e09532..ff85243706 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsValue.java index d8fd529b92..74d64a99fd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldMutableFieldsValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstate.java index a0c85e3999..b9a87874a5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstateAllOf.java index 48802d6109..9f507b7039 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplyValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplyValue.java index d7ff46c399..b6f7b7e6e7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplyValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleResourceManagerFieldTotalSupplyValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntrySubstate.java index ddbe8a3a51..e80cfb26b3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntrySubstateAllOf.java index 0a5a395ff8..0ba87480ac 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntryValue.java index b12881caa9..116a20aeb0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultContentsIndexEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceSubstate.java index 0a85df89a4..a7ff61663a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceSubstateAllOf.java index 2413607db6..29e5cfe852 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceValue.java index d315bb916f..cbe8787b7b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldBalanceValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusSubstate.java index 135c591869..3fb2a4d1d2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusSubstateAllOf.java index 01c34dc0cb..f8a1c9f003 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusValue.java index dedae0021e..8732d30fbc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NonFungibleVaultFieldFrozenStatusValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NotarizedTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NotarizedTransaction.java index 8924e640fb..34928cb398 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/NotarizedTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/NotarizedTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectFieldStructure.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectFieldStructure.java index 54a444d3f4..f92b5af7f1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectFieldStructure.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectFieldStructure.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectFieldStructureAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectFieldStructureAllOf.java index ffdde76363..975462cf30 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectFieldStructureAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectFieldStructureAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectHook.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectHook.java index 4d4d38aecc..a26f76c845 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectHook.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectHook.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectIndexPartitionEntryStructure.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectIndexPartitionEntryStructure.java index d870aae452..948301ee9a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectIndexPartitionEntryStructure.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectIndexPartitionEntryStructure.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectInstanceTypeReference.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectInstanceTypeReference.java index 44d14d4fe2..433fce010e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectInstanceTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectInstanceTypeReference.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectInstanceTypeReferenceAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectInstanceTypeReferenceAllOf.java index 739cdaee9d..8732c311c6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectInstanceTypeReferenceAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectInstanceTypeReferenceAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectKeyValuePartitionEntryStructure.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectKeyValuePartitionEntryStructure.java index e39c0e1cd1..33635780a0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectKeyValuePartitionEntryStructure.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectKeyValuePartitionEntryStructure.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectRoleKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectRoleKey.java index 1b7cff24b0..eeeea099e1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectRoleKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectRoleKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSortedIndexPartitionEntryStructure.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSortedIndexPartitionEntryStructure.java index d9166499c7..8661ef312f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSortedIndexPartitionEntryStructure.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSortedIndexPartitionEntryStructure.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSubstateTypeReference.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSubstateTypeReference.java index e56021566e..49ce763c83 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSubstateTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSubstateTypeReference.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSubstateTypeReferenceType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSubstateTypeReferenceType.java index 338e6449b3..c887d349ed 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSubstateTypeReferenceType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectSubstateTypeReferenceType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectTypeInfoDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectTypeInfoDetails.java index cf7740cfec..b2886051e4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectTypeInfoDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectTypeInfoDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectTypeInfoDetailsAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectTypeInfoDetailsAllOf.java index 653306745e..c829b00c11 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectTypeInfoDetailsAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ObjectTypeInfoDetailsAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateSubstate.java index db276b1e0b..9ec7eee560 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateSubstateAllOf.java index 3427361f4d..1de9f7c463 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateValue.java index df6a9b8719..c8be9a893f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OneResourcePoolFieldStateValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OuterObjectOnlyMethodAccessibility.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OuterObjectOnlyMethodAccessibility.java index c4ab4c022e..c6ee12088b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OuterObjectOnlyMethodAccessibility.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OuterObjectOnlyMethodAccessibility.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnPackageOnlyMethodAccessibility.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnPackageOnlyMethodAccessibility.java index 3ca6ad31d5..e28656ecdb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnPackageOnlyMethodAccessibility.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnPackageOnlyMethodAccessibility.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnerRole.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnerRole.java index a2ad06844b..2ce6fa6083 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnerRole.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnerRole.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnerRoleUpdater.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnerRoleUpdater.java index 25b152d6f4..d683a62835 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnerRoleUpdater.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/OwnerRoleUpdater.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntrySubstate.java index 125b69424d..5e1b7ad396 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntrySubstateAllOf.java index 9520b0ff80..9698bfc603 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntryValue.java index 8858c77637..3c04f292de 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintAuthTemplateEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntrySubstate.java index 706a3f4af8..266b922277 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntrySubstateAllOf.java index 9567b7d067..74077e94e3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntryValue.java index afb940a8f8..97dba401a0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDefinitionEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntrySubstate.java index 3ab97e6eba..94e57542a2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntrySubstateAllOf.java index 151e407053..0a5c88f376 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntryValue.java index 3acddd3f2e..98162af1e7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintDependenciesEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntrySubstate.java index 381e1ea8a2..3cd5c0a62a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntrySubstateAllOf.java index 745abfb5f8..119fe157a4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntryValue.java index 8175664aff..d674422e4e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageBlueprintRoyaltyEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntrySubstate.java index 02e09f32d8..8feb0f8e56 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntrySubstateAllOf.java index 1b321fc8d7..6c51c22ffc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntryValue.java index 4fbd22ca6c..cd3f0d1e4c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeInstrumentedCodeEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeKey.java index 271886a0fb..bae4c4622b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntrySubstate.java index 74cd1640eb..2b163a8398 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntrySubstateAllOf.java index fafef7f8eb..9c5c8f1511 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntryValue.java index 970dbcd0da..035ac999a5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeOriginalCodeEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntrySubstate.java index 86ee47f371..2f38d8ec03 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntrySubstateAllOf.java index d221166d84..49c6834ba9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntryValue.java index 89abceb802..567bc9466c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageCodeVmTypeEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageExport.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageExport.java index cd94ae3e2b..dc6763e84f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageExport.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageExport.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorSubstate.java index 57f173095c..db36ef5a07 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorSubstateAllOf.java index c59fa4de4f..1101452a7e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorValue.java index 30c428c0fc..265cc55da6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageFieldRoyaltyAccumulatorValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageObjectSubstateTypeReference.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageObjectSubstateTypeReference.java index e65c1a087c..0c4b664230 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageObjectSubstateTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageObjectSubstateTypeReference.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageTypeReference.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageTypeReference.java index 638f049b7e..6d4f39c6cb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PackageTypeReference.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransaction.java index 66750c2c78..94d7a3fc26 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransactionAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransactionAllOf.java index 8d1d8c6d43..56ea47b0ad 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransactionAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransactionAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransactionIdentifiers.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransactionIdentifiers.java index 9128123024..fd428715b4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransactionIdentifiers.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedLedgerTransactionIdentifiers.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransaction.java index 559524fcfe..2144519048 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionAllOf.java index 6821fb5e01..cd0e744688 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionAllOfValidationError.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionAllOfValidationError.java index 925ce4aa8f..655127bb86 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionAllOfValidationError.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionAllOfValidationError.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionIdentifiers.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionIdentifiers.java index 2919dc15ff..82e5a8c151 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionIdentifiers.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedNotarizedTransactionIdentifiers.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntent.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntent.java index fe64e573e1..02316d547e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntent.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntent.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntentAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntentAllOf.java index 4c22f917e1..cb19f50216 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntentAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntentAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntentIdentifiers.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntentIdentifiers.java index 95a3f03ce3..16f151970b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntentIdentifiers.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedSignedTransactionIntentIdentifiers.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransaction.java index 94b4a4d0ae..ce9c6573dc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntent.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntent.java index 93f9f48b7a..b9b1d1b839 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntent.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntent.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntentAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntentAllOf.java index f22eb96ac9..1c46e93efc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntentAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntentAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntentIdentifiers.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntentIdentifiers.java index 01f9e40e44..151aae685b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntentIdentifiers.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionIntentIdentifiers.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionType.java index dedba7ea32..a93e72d85a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ParsedTransactionType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionDescription.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionDescription.java index 0419461cf4..5686a1d06d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionDescription.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionDescription.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionDescriptionType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionDescriptionType.java index f3805ffe29..97e9056ced 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionDescriptionType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionDescriptionType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionId.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionId.java index f8ee90727e..842a2110ed 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionId.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionId.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionKind.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionKind.java index 2910fabebd..c5119bfc80 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionKind.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PartitionKind.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PaymentFromVault.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PaymentFromVault.java index 8d6d832284..cf1242c2a0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PaymentFromVault.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PaymentFromVault.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PaymentToRoyaltyRecipient.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PaymentToRoyaltyRecipient.java index bdc28514ee..fa0599aa33 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PaymentToRoyaltyRecipient.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PaymentToRoyaltyRecipient.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PendingOwnerStakeWithdrawal.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PendingOwnerStakeWithdrawal.java index b89b12e216..987e77bdfd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PendingOwnerStakeWithdrawal.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PendingOwnerStakeWithdrawal.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextMessageContent.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextMessageContent.java index f478d1d3a5..18e7183644 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextMessageContent.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextMessageContent.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextMessageContentType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextMessageContentType.java index b8ad63c636..9e1513d9ca 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextMessageContentType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextMessageContentType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextTransactionMessage.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextTransactionMessage.java index 91865f3985..531fd2d590 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextTransactionMessage.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextTransactionMessage.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextTransactionMessageAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextTransactionMessageAllOf.java index dc80c8152d..f4d87c9835 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextTransactionMessageAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PlaintextTransactionMessageAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PoolVault.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PoolVault.java index 79526a32a3..1e2a941dd6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PoolVault.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PoolVault.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PresentedBadge.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PresentedBadge.java index fafb4db483..0d52013821 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PresentedBadge.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PresentedBadge.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PresentedBadgeType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PresentedBadgeType.java index abf82a0464..10eea583a4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PresentedBadgeType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PresentedBadgeType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PrimaryRoleRecoveryAttempt.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PrimaryRoleRecoveryAttempt.java index 67147e9be3..5979c99c82 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PrimaryRoleRecoveryAttempt.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PrimaryRoleRecoveryAttempt.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofAccessRuleNode.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofAccessRuleNode.java index cfbda3ec4a..ac94f2850f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofAccessRuleNode.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofAccessRuleNode.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofAccessRuleNodeAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofAccessRuleNodeAllOf.java index 0fef099328..a3635487f2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofAccessRuleNodeAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofAccessRuleNodeAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofRule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofRule.java index 8030aa4380..a5ae8410c4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofRule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofRuleType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofRuleType.java index 6e5165ddcb..f026ac4c34 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofRuleType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProofRuleType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProposerReward.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProposerReward.java index a26ad58787..817b020ed0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProposerReward.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProposerReward.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtectedAccessRule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtectedAccessRule.java index 97c2e3f570..9bdfe60f1a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtectedAccessRule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtectedAccessRule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtectedAccessRuleAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtectedAccessRuleAllOf.java index a2c644af95..9223d61b7b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtectedAccessRuleAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtectedAccessRuleAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolUpdateLedgerProofOrigin.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolUpdateLedgerProofOrigin.java index c5b381c3a5..45ae226a3b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolUpdateLedgerProofOrigin.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolUpdateLedgerProofOrigin.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolUpdateLedgerProofOriginAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolUpdateLedgerProofOriginAllOf.java index 6b8195d712..7f0d16bc43 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolUpdateLedgerProofOriginAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolUpdateLedgerProofOriginAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolVersionReadiness.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolVersionReadiness.java index 286b5f401b..d9952fdd9c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolVersionReadiness.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ProtocolVersionReadiness.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicKey.java index 9b9dfd3fad..31f3db7434 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicKeyType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicKeyType.java index 523d3c6a4c..d5f457bd63 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicKeyType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicKeyType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicMethodAccessibility.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicMethodAccessibility.java index f4e6660b95..d7817b66ca 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicMethodAccessibility.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/PublicMethodAccessibility.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ReceiverInfo.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ReceiverInfo.java index 6060d9b236..0563e3ce0a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ReceiverInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ReceiverInfo.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RecoveryProposal.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RecoveryProposal.java index ed3c867d30..78ed99638d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RecoveryProposal.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RecoveryProposal.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RecoveryRoleRecoveryAttempt.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RecoveryRoleRecoveryAttempt.java index 14e60f930e..60467b3e4b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RecoveryRoleRecoveryAttempt.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RecoveryRoleRecoveryAttempt.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ReferenceType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ReferenceType.java index b51dae3e11..efb6f38229 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ReferenceType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ReferenceType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RemoteGenericSubstitution.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RemoteGenericSubstitution.java index 5c43881239..26c1865610 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RemoteGenericSubstitution.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RemoteGenericSubstitution.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RemoteGenericSubstitutionAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RemoteGenericSubstitutionAllOf.java index 6556beef7b..7b42d93566 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RemoteGenericSubstitutionAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RemoteGenericSubstitutionAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequestedStateVersionOutOfBoundsErrorDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequestedStateVersionOutOfBoundsErrorDetails.java index 2a9d52174c..086fa13ec5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequestedStateVersionOutOfBoundsErrorDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequestedStateVersionOutOfBoundsErrorDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequireProofRule.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequireProofRule.java index d896665ab9..401be89bde 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequireProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequireProofRule.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequireProofRuleAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequireProofRuleAllOf.java index e2f85f3058..9a35c75cfc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequireProofRuleAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequireProofRuleAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/Requirement.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/Requirement.java index 193f7c9998..27c548e2c6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/Requirement.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/Requirement.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequirementType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequirementType.java index 63e613da66..2e04b1d67f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequirementType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RequirementType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAmount.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAmount.java index 8257093d21..5e060b70b8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAmount.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAmount.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAuthorizedDepositorBadge.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAuthorizedDepositorBadge.java index e8cf3ffa21..e0c8531b5e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAuthorizedDepositorBadge.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAuthorizedDepositorBadge.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAuthorizedDepositorBadgeAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAuthorizedDepositorBadgeAllOf.java index 79673707b9..9cb8548de8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAuthorizedDepositorBadgeAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceAuthorizedDepositorBadgeAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceChange.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceChange.java index fb8f7840e8..fd548589b1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceChange.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceChange.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceKey.java index 27fefb24e6..a51b820189 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourcePreference.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourcePreference.java index f6f4a633af..fff8d9b9d6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourcePreference.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourcePreference.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourcePresentedBadge.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourcePresentedBadge.java index 60f06fa28f..066fda33a2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourcePresentedBadge.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourcePresentedBadge.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceRequirement.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceRequirement.java index f3c6464df9..6dd6bdbbbc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceRequirement.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceRequirement.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceRequirementAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceRequirementAllOf.java index 4cdaeee461..7a1db9e578 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceRequirementAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceRequirementAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceSpecificDepositBehaviour.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceSpecificDepositBehaviour.java index f577c23cca..2ce826f327 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceSpecificDepositBehaviour.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceSpecificDepositBehaviour.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceType.java index cb363c7e6f..fce63935b8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ResourceType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstate.java index 45ea313cba..9c9f9dcb98 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstateAllOf.java index 8458a4887f..9772cbef74 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleValue.java index 1289eebb64..2c96b57fc6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleFieldOwnerRoleValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntrySubstate.java index b464a53c1a..a5cd22bc18 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntrySubstateAllOf.java index 6926c5d92b..d09657b4d7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntryValue.java index 6dcf22ead8..20d1bc40ab 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleAssignmentModuleRuleEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleDetails.java index 7d51833a25..e2f1ced9ee 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleProtectedMethodAccessibility.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleProtectedMethodAccessibility.java index b993756fee..d9d05bbf57 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleProtectedMethodAccessibility.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleProtectedMethodAccessibility.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleProtectedMethodAccessibilityAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleProtectedMethodAccessibilityAllOf.java index 9285f2c6dd..481a3bffd8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleProtectedMethodAccessibilityAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleProtectedMethodAccessibilityAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleSpecification.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleSpecification.java index ed51263ab7..7b1942d20b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleSpecification.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoleSpecification.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateLedgerTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateLedgerTransaction.java index f1a6134f7a..4a067778b9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateLedgerTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateLedgerTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateLedgerTransactionAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateLedgerTransactionAllOf.java index 9c32abe255..e03a7772d6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateLedgerTransactionAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateLedgerTransactionAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateTransaction.java index 40d697faad..ac626aafd3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoundUpdateTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyAmount.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyAmount.java index a085964288..83aa8558b9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyAmount.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyAmount.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateSubstate.java index b83267fe04..3e3b0d3e6a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateSubstateAllOf.java index 7ca2dd9c37..caeb1ccb20 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateValue.java index 19731c5f41..278a348c5d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleFieldStateValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstate.java index f21d4f24c1..ffbd78e66b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstateAllOf.java index 1c292f151b..9ae4163e37 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntryValue.java index 34214dc634..0228812d01 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/RoyaltyModuleMethodRoyaltyEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SborData.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SborData.java index a0ada7eafb..81fab33dc9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SborData.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SborData.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SborFormatOptions.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SborFormatOptions.java index a08a7dd442..c7caa51cba 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SborFormatOptions.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SborFormatOptions.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScenariosRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScenariosRequest.java index f31e3d979d..b52fd15317 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScenariosRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScenariosRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScenariosResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScenariosResponse.java index d21762b96b..112ba2408d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScenariosResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScenariosResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntrySubstate.java index dbf3f45319..8b5b9c8701 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntrySubstateAllOf.java index ec3cb90f76..d4afb9e0db 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntryValue.java index f6883ac5d5..afed02bd9c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaKey.java index 1fb237aefa..58c8cab565 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SchemaKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScopedTypeId.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScopedTypeId.java index 7034a769ee..06b5b19ab1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScopedTypeId.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScopedTypeId.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScryptoInstant.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScryptoInstant.java index 9cd1eeb438..11e4a9e73c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScryptoInstant.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScryptoInstant.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScryptoSchema.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScryptoSchema.java index 821bed6511..ee813ab4c5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScryptoSchema.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ScryptoSchema.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignallingValidator.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignallingValidator.java index b68011d67e..2e7c5551cd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignallingValidator.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignallingValidator.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/Signature.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/Signature.java index 3c3e861fec..6ce6bea29c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/Signature.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/Signature.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignatureWithPublicKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignatureWithPublicKey.java index 898353f56e..01e3985df7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignatureWithPublicKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignatureWithPublicKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignedTransactionIntent.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignedTransactionIntent.java index 5bde97eac7..704c968d5f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignedTransactionIntent.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignedTransactionIntent.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignificantProtocolUpdateReadinessEntry.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignificantProtocolUpdateReadinessEntry.java index 6e8d224822..281ec1714f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignificantProtocolUpdateReadinessEntry.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SignificantProtocolUpdateReadinessEntry.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedIndexBlueprintCollectionSchema.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedIndexBlueprintCollectionSchema.java index 7ec12770eb..f2f7454af9 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedIndexBlueprintCollectionSchema.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedIndexBlueprintCollectionSchema.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedIndexBlueprintCollectionSchemaAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedIndexBlueprintCollectionSchemaAllOf.java index d777f37d4c..2d4562d1a1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedIndexBlueprintCollectionSchemaAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedIndexBlueprintCollectionSchemaAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedSubstateKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedSubstateKey.java index 26d77f4269..7c95fbda27 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedSubstateKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedSubstateKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedSubstateKeyAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedSubstateKeyAllOf.java index 638b351765..4f011620f1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedSubstateKeyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SortedSubstateKeyAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccessControllerRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccessControllerRequest.java index d5d8a6df56..015ce04961 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccessControllerRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccessControllerRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccessControllerResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccessControllerResponse.java index 464bf51cb0..0397e788dc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccessControllerResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccessControllerResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccountRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccountRequest.java index 88a2b44e77..6f7f61a690 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccountRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccountRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccountResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccountResponse.java index 3672ab022f..9f80c7dd8a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccountResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateAccountResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentDescendentNode.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentDescendentNode.java index 734e9abe69..6001d66c43 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentDescendentNode.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentDescendentNode.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentRequest.java index a77fb9658e..39d707d3f0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentResponse.java index a880ca87bb..05a82a0d59 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateComponentResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateConsensusManagerRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateConsensusManagerRequest.java index d61174d7c1..514161be76 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateConsensusManagerRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateConsensusManagerRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateConsensusManagerResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateConsensusManagerResponse.java index d32ef75a4c..ea9d3b361d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateConsensusManagerResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateConsensusManagerResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateFungibleResourceManager.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateFungibleResourceManager.java index d9113bdf05..9a5f2108d7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateFungibleResourceManager.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateFungibleResourceManager.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateFungibleResourceManagerAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateFungibleResourceManagerAllOf.java index f44f26b3e1..0185f93060 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateFungibleResourceManagerAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateFungibleResourceManagerAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleRequest.java index 507fa6f259..6f1777ebde 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResourceManager.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResourceManager.java index 6637cba7fe..d1df4c62c3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResourceManager.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResourceManager.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResourceManagerAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResourceManagerAllOf.java index 2774567a7d..e4548d947e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResourceManagerAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResourceManagerAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResponse.java index 6598a65996..3e6b0a1b8b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateNonFungibleResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StatePackageRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StatePackageRequest.java index e6d0549c84..61620160f4 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StatePackageRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StatePackageRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StatePackageResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StatePackageResponse.java index cec8154773..ee26eb512f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StatePackageResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StatePackageResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceManager.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceManager.java index a7a8016b28..a78bf80c18 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceManager.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceManager.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceRequest.java index 4e202464aa..fba8249fa3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceResponse.java index e5f95c72c3..56346f1995 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateResourceResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateUpdates.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateUpdates.java index 8a5100ce6f..cb9cfbca5a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateUpdates.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateUpdates.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateValidatorRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateValidatorRequest.java index 08ec236815..7c0c9a1f47 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateValidatorRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateValidatorRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateValidatorResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateValidatorResponse.java index 8271d591a6..ac46ecd79d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateValidatorResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StateValidatorResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticBlueprintPayloadDef.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticBlueprintPayloadDef.java index df542f9dd0..b1b8fdb304 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticBlueprintPayloadDef.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticBlueprintPayloadDef.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticBlueprintPayloadDefAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticBlueprintPayloadDefAllOf.java index 87b86bb709..2a2a306813 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticBlueprintPayloadDefAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticBlueprintPayloadDefAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticRoleDefinitionAuthTemplate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticRoleDefinitionAuthTemplate.java index d9504f5939..a65459a0fb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticRoleDefinitionAuthTemplate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StaticRoleDefinitionAuthTemplate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetails.java index eb525aa308..c72d0ee4ca 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBounds.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBounds.java index 29a4ffbcf8..c8c0af0ca7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBounds.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBounds.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBoundsAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBoundsAllOf.java index 4918542cdf..715dadbcaf 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBoundsAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBoundsAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBounds.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBounds.java index 64a0accc15..5a1fe743fa 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBounds.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBounds.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBoundsAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBoundsAllOf.java index 7510e022b6..cf34b02041 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBoundsAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBoundsAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsType.java index 04bf481b4f..30354a3607 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorDetailsType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorResponse.java index 593f95ebed..cc22281257 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorResponseAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorResponseAllOf.java index 7a1bf53b5d..ff9a6f40e6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorResponseAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsErrorResponseAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilter.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilter.java index 10fb45926a..d3058c4567 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilter.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilter.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterAny.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterAny.java index 4f11a54a0b..106efb3f89 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterAny.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterAny.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterAnyAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterAnyAllOf.java index 957b6faa61..fe22fcedfc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterAnyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterAnyAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterNewEpochs.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterNewEpochs.java index 34400e6fa4..d582541092 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterNewEpochs.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterNewEpochs.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterNewEpochsAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterNewEpochsAllOf.java index 5f7aaa9e88..1b5849cb85 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterNewEpochsAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterNewEpochsAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateExecution.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateExecution.java index 0367ba7324..f7cc487276 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateExecution.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateExecution.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateExecutionAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateExecutionAllOf.java index 47ac3cbefa..e58bff3a9b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateExecutionAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateExecutionAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateInitializations.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateInitializations.java index a5c033f9b9..2c17a825a2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateInitializations.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterProtocolUpdateInitializations.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterType.java index 8e8858fbbd..893c70f3c1 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsFilterType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsRequest.java index e67a7dd171..3b4697410f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsResponse.java index f638c0dd25..61e6a21aed 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamProofsResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorDetails.java index 86ca3afbf1..876ac93601 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorDetailsType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorDetailsType.java index 2c4f5fb621..33e0404111 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorDetailsType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorDetailsType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorResponse.java index 8b0472e8c8..0d0e38ad3e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorResponseAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorResponseAllOf.java index e6a946af52..d8cb7b4ab3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorResponseAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsErrorResponseAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsRequest.java index 8410ffe091..3c18134697 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsResponse.java index 143cebc6f7..1644ffaa36 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StreamTransactionsResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StringPlaintextMessageContent.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StringPlaintextMessageContent.java index 72fd76aea2..54056443fc 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StringPlaintextMessageContent.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StringPlaintextMessageContent.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StringPlaintextMessageContentAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StringPlaintextMessageContentAllOf.java index 66f04adbc4..26853f9e6a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/StringPlaintextMessageContentAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/StringPlaintextMessageContentAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/Substate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/Substate.java index 84e6a6e060..8927d3ae0a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/Substate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/Substate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateFormatOptions.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateFormatOptions.java index 7964948751..6f825828db 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateFormatOptions.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateFormatOptions.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateId.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateId.java index ff7f93b088..71baae6ca7 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateId.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateId.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateIdAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateIdAllOf.java index d894c51e10..37e1c1f8e5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateIdAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateIdAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateKey.java index 14db68832a..60f83644d2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateKeyType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateKeyType.java index b47dc460f4..7c1e619f6d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateKeyType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateKeyType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateSystemStructure.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateSystemStructure.java index 0fc67f28cc..71633f447c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateSystemStructure.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateSystemStructure.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateSystemStructureType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateSystemStructureType.java index 3cd549f2c2..49033799f3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateSystemStructureType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateSystemStructureType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateType.java index 56ca365ce9..cba8a38f3c 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateValue.java index 6581c72b09..972b406c67 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SubstateValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemCostingParameters.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemCostingParameters.java index b545f45e27..4022664a1a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemCostingParameters.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemCostingParameters.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldKind.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldKind.java index 925bf22762..7df19debc6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldKind.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldKind.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldStructure.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldStructure.java index 0d33c9c443..ef0ec0da5d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldStructure.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldStructure.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldStructureAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldStructureAllOf.java index 6768dcacf4..fea8042876 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldStructureAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemFieldStructureAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemParameters.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemParameters.java index 67eb1768fa..4bb3ff1ee5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemParameters.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemParameters.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemSchemaStructure.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemSchemaStructure.java index c8d02837b3..627f8fba6a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemSchemaStructure.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemSchemaStructure.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemTransaction.java index 7b5724a0cc..5bc3c1191e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/SystemTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TargetIdentifier.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TargetIdentifier.java index eec37b0d55..e254b4ae50 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TargetIdentifier.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TargetIdentifier.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TargetIdentifierType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TargetIdentifierType.java index cda3118bcb..43f09348d3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TargetIdentifierType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TargetIdentifierType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TimestampedValidatorSignature.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TimestampedValidatorSignature.java index edf7971f04..7df5510578 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TimestampedValidatorSignature.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TimestampedValidatorSignature.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionCallPreviewRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionCallPreviewRequest.java index f5f1ffec82..6c2e587459 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionCallPreviewRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionCallPreviewRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionCallPreviewResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionCallPreviewResponse.java index f71c1a7a32..b55af83054 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionCallPreviewResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionCallPreviewResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionFormatOptions.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionFormatOptions.java index c93e944837..0710587975 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionFormatOptions.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionFormatOptions.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionHeader.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionHeader.java index d4a4ee2136..e85c07846b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionHeader.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionHeader.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIdKey.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIdKey.java index 220ee2a270..a28d5492a8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIdKey.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIdKey.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIdentifiers.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIdentifiers.java index 067619c979..ee899099a8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIdentifiers.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIdentifiers.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIntent.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIntent.java index c4bc5a4763..5986a6d65f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIntent.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIntent.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIntentStatus.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIntentStatus.java index e24661b51c..87ab34e079 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIntentStatus.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionIntentStatus.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionMessage.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionMessage.java index 1e846f4980..261ab8e3e0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionMessage.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionMessage.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionMessageType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionMessageType.java index 0f02de78fe..ef070870b6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionMessageType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionMessageType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionParseRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionParseRequest.java index 2637361bf9..47073e89a2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionParseRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionParseRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionParseResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionParseResponse.java index 23ac69360c..32a3f59932 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionParseResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionParseResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPayloadDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPayloadDetails.java index a7821f84c4..2fcca913ae 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPayloadDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPayloadDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPayloadStatus.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPayloadStatus.java index 98cd2ada45..02e3ed7616 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPayloadStatus.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPayloadStatus.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewRequest.java index 115c6b7dd2..200737de88 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). @@ -26,6 +26,7 @@ import com.radixdlt.api.core.generated.models.PublicKey; import com.radixdlt.api.core.generated.models.TransactionMessage; import com.radixdlt.api.core.generated.models.TransactionPreviewRequestFlags; +import com.radixdlt.api.core.generated.models.TransactionPreviewResponseOptions; import io.swagger.annotations.ApiModel; import io.swagger.annotations.ApiModelProperty; import java.util.ArrayList; @@ -49,6 +50,7 @@ TransactionPreviewRequest.JSON_PROPERTY_NONCE, TransactionPreviewRequest.JSON_PROPERTY_SIGNER_PUBLIC_KEYS, TransactionPreviewRequest.JSON_PROPERTY_MESSAGE, + TransactionPreviewRequest.JSON_PROPERTY_OPTIONS, TransactionPreviewRequest.JSON_PROPERTY_FLAGS }) @javax.annotation.processing.Generated(value = "org.openapitools.codegen.languages.JavaClientCodegen") @@ -89,6 +91,9 @@ public class TransactionPreviewRequest { public static final String JSON_PROPERTY_MESSAGE = "message"; private TransactionMessage message; + public static final String JSON_PROPERTY_OPTIONS = "options"; + private TransactionPreviewResponseOptions options; + public static final String JSON_PROPERTY_FLAGS = "flags"; private TransactionPreviewRequestFlags flags; @@ -428,6 +433,32 @@ public void setMessage(TransactionMessage message) { } + public TransactionPreviewRequest options(TransactionPreviewResponseOptions options) { + this.options = options; + return this; + } + + /** + * Get options + * @return options + **/ + @javax.annotation.Nullable + @ApiModelProperty(value = "") + @JsonProperty(JSON_PROPERTY_OPTIONS) + @JsonInclude(value = JsonInclude.Include.USE_DEFAULTS) + + public TransactionPreviewResponseOptions getOptions() { + return options; + } + + + @JsonProperty(JSON_PROPERTY_OPTIONS) + @JsonInclude(value = JsonInclude.Include.USE_DEFAULTS) + public void setOptions(TransactionPreviewResponseOptions options) { + this.options = options; + } + + public TransactionPreviewRequest flags(TransactionPreviewRequestFlags flags) { this.flags = flags; return this; @@ -478,12 +509,13 @@ public boolean equals(Object o) { Objects.equals(this.nonce, transactionPreviewRequest.nonce) && Objects.equals(this.signerPublicKeys, transactionPreviewRequest.signerPublicKeys) && Objects.equals(this.message, transactionPreviewRequest.message) && + Objects.equals(this.options, transactionPreviewRequest.options) && Objects.equals(this.flags, transactionPreviewRequest.flags); } @Override public int hashCode() { - return Objects.hash(network, atLedgerState, manifest, blobsHex, startEpochInclusive, endEpochExclusive, notaryPublicKey, notaryIsSignatory, tipPercentage, nonce, signerPublicKeys, message, flags); + return Objects.hash(network, atLedgerState, manifest, blobsHex, startEpochInclusive, endEpochExclusive, notaryPublicKey, notaryIsSignatory, tipPercentage, nonce, signerPublicKeys, message, options, flags); } @Override @@ -502,6 +534,7 @@ public String toString() { sb.append(" nonce: ").append(toIndentedString(nonce)).append("\n"); sb.append(" signerPublicKeys: ").append(toIndentedString(signerPublicKeys)).append("\n"); sb.append(" message: ").append(toIndentedString(message)).append("\n"); + sb.append(" options: ").append(toIndentedString(options)).append("\n"); sb.append(" flags: ").append(toIndentedString(flags)).append("\n"); sb.append("}"); return sb.toString(); diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewRequestFlags.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewRequestFlags.java index 4f483b4d88..d6287465fd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewRequestFlags.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewRequestFlags.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewResponse.java index e5d0aac9f6..89a4777aa0 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). @@ -40,6 +40,7 @@ TransactionPreviewResponse.JSON_PROPERTY_AT_LEDGER_STATE, TransactionPreviewResponse.JSON_PROPERTY_ENCODED_RECEIPT, TransactionPreviewResponse.JSON_PROPERTY_RECEIPT, + TransactionPreviewResponse.JSON_PROPERTY_RADIX_ENGINE_TOOLKIT_RECEIPT, TransactionPreviewResponse.JSON_PROPERTY_INSTRUCTION_RESOURCE_CHANGES, TransactionPreviewResponse.JSON_PROPERTY_LOGS }) @@ -54,6 +55,9 @@ public class TransactionPreviewResponse { public static final String JSON_PROPERTY_RECEIPT = "receipt"; private TransactionReceipt receipt; + public static final String JSON_PROPERTY_RADIX_ENGINE_TOOLKIT_RECEIPT = "radix_engine_toolkit_receipt"; + private Object radixEngineToolkitReceipt; + public static final String JSON_PROPERTY_INSTRUCTION_RESOURCE_CHANGES = "instruction_resource_changes"; private List instructionResourceChanges = new ArrayList<>(); @@ -95,11 +99,13 @@ public TransactionPreviewResponse encodedReceipt(String encodedReceipt) { } /** - * The hex-sbor-encoded receipt + * 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. * @return encodedReceipt + * @deprecated **/ + @Deprecated @javax.annotation.Nonnull - @ApiModelProperty(required = true, value = "The hex-sbor-encoded receipt") + @ApiModelProperty(required = true, value = "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. ") @JsonProperty(JSON_PROPERTY_ENCODED_RECEIPT) @JsonInclude(value = JsonInclude.Include.ALWAYS) @@ -141,6 +147,32 @@ public void setReceipt(TransactionReceipt receipt) { } + public TransactionPreviewResponse radixEngineToolkitReceipt(Object radixEngineToolkitReceipt) { + this.radixEngineToolkitReceipt = radixEngineToolkitReceipt; + return this; + } + + /** + * 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. + * @return radixEngineToolkitReceipt + **/ + @javax.annotation.Nullable + @ApiModelProperty(value = "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. ") + @JsonProperty(JSON_PROPERTY_RADIX_ENGINE_TOOLKIT_RECEIPT) + @JsonInclude(value = JsonInclude.Include.USE_DEFAULTS) + + public Object getRadixEngineToolkitReceipt() { + return radixEngineToolkitReceipt; + } + + + @JsonProperty(JSON_PROPERTY_RADIX_ENGINE_TOOLKIT_RECEIPT) + @JsonInclude(value = JsonInclude.Include.USE_DEFAULTS) + public void setRadixEngineToolkitReceipt(Object radixEngineToolkitReceipt) { + this.radixEngineToolkitReceipt = radixEngineToolkitReceipt; + } + + public TransactionPreviewResponse instructionResourceChanges(List instructionResourceChanges) { this.instructionResourceChanges = instructionResourceChanges; return this; @@ -218,13 +250,14 @@ public boolean equals(Object o) { return Objects.equals(this.atLedgerState, transactionPreviewResponse.atLedgerState) && Objects.equals(this.encodedReceipt, transactionPreviewResponse.encodedReceipt) && Objects.equals(this.receipt, transactionPreviewResponse.receipt) && + Objects.equals(this.radixEngineToolkitReceipt, transactionPreviewResponse.radixEngineToolkitReceipt) && Objects.equals(this.instructionResourceChanges, transactionPreviewResponse.instructionResourceChanges) && Objects.equals(this.logs, transactionPreviewResponse.logs); } @Override public int hashCode() { - return Objects.hash(atLedgerState, encodedReceipt, receipt, instructionResourceChanges, logs); + return Objects.hash(atLedgerState, encodedReceipt, receipt, radixEngineToolkitReceipt, instructionResourceChanges, logs); } @Override @@ -234,6 +267,7 @@ public String toString() { sb.append(" atLedgerState: ").append(toIndentedString(atLedgerState)).append("\n"); sb.append(" encodedReceipt: ").append(toIndentedString(encodedReceipt)).append("\n"); sb.append(" receipt: ").append(toIndentedString(receipt)).append("\n"); + sb.append(" radixEngineToolkitReceipt: ").append(toIndentedString(radixEngineToolkitReceipt)).append("\n"); sb.append(" instructionResourceChanges: ").append(toIndentedString(instructionResourceChanges)).append("\n"); sb.append(" logs: ").append(toIndentedString(logs)).append("\n"); sb.append("}"); diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewResponseLogsInner.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewResponseLogsInner.java index d33404f6ef..182087579e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewResponseLogsInner.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewResponseLogsInner.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewResponseOptions.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewResponseOptions.java new file mode 100644 index 0000000000..5f210be400 --- /dev/null +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionPreviewResponseOptions.java @@ -0,0 +1,112 @@ +/* + * 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 + * + * + * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). + * https://openapi-generator.tech + * Do not edit the class manually. + */ + + +package com.radixdlt.api.core.generated.models; + +import java.util.Objects; +import java.util.Arrays; +import java.util.Map; +import java.util.HashMap; +import com.fasterxml.jackson.annotation.JsonInclude; +import com.fasterxml.jackson.annotation.JsonProperty; +import com.fasterxml.jackson.annotation.JsonCreator; +import com.fasterxml.jackson.annotation.JsonTypeName; +import com.fasterxml.jackson.annotation.JsonValue; +import io.swagger.annotations.ApiModel; +import io.swagger.annotations.ApiModelProperty; +import com.fasterxml.jackson.annotation.JsonPropertyOrder; + + +/** + * A set of flags to configure the response of the transaction preview. + */ +@ApiModel(description = "A set of flags to configure the response of the transaction preview.") +@JsonPropertyOrder({ + TransactionPreviewResponseOptions.JSON_PROPERTY_RADIX_ENGINE_TOOLKIT_RECEIPT +}) +@javax.annotation.processing.Generated(value = "org.openapitools.codegen.languages.JavaClientCodegen") +public class TransactionPreviewResponseOptions { + public static final String JSON_PROPERTY_RADIX_ENGINE_TOOLKIT_RECEIPT = "radix_engine_toolkit_receipt"; + private Boolean radixEngineToolkitReceipt; + + public TransactionPreviewResponseOptions() { + } + + public TransactionPreviewResponseOptions radixEngineToolkitReceipt(Boolean radixEngineToolkitReceipt) { + this.radixEngineToolkitReceipt = radixEngineToolkitReceipt; + return this; + } + + /** + * 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. + * @return radixEngineToolkitReceipt + **/ + @javax.annotation.Nullable + @ApiModelProperty(value = "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. ") + @JsonProperty(JSON_PROPERTY_RADIX_ENGINE_TOOLKIT_RECEIPT) + @JsonInclude(value = JsonInclude.Include.USE_DEFAULTS) + + public Boolean getRadixEngineToolkitReceipt() { + return radixEngineToolkitReceipt; + } + + + @JsonProperty(JSON_PROPERTY_RADIX_ENGINE_TOOLKIT_RECEIPT) + @JsonInclude(value = JsonInclude.Include.USE_DEFAULTS) + public void setRadixEngineToolkitReceipt(Boolean radixEngineToolkitReceipt) { + this.radixEngineToolkitReceipt = radixEngineToolkitReceipt; + } + + + /** + * Return true if this TransactionPreviewResponseOptions object is equal to o. + */ + @Override + public boolean equals(Object o) { + if (this == o) { + return true; + } + if (o == null || getClass() != o.getClass()) { + return false; + } + TransactionPreviewResponseOptions transactionPreviewResponseOptions = (TransactionPreviewResponseOptions) o; + return Objects.equals(this.radixEngineToolkitReceipt, transactionPreviewResponseOptions.radixEngineToolkitReceipt); + } + + @Override + public int hashCode() { + return Objects.hash(radixEngineToolkitReceipt); + } + + @Override + public String toString() { + StringBuilder sb = new StringBuilder(); + sb.append("class TransactionPreviewResponseOptions {\n"); + sb.append(" radixEngineToolkitReceipt: ").append(toIndentedString(radixEngineToolkitReceipt)).append("\n"); + sb.append("}"); + return sb.toString(); + } + + /** + * Convert the given object to string with each line indented by 4 spaces + * (except the first line). + */ + private String toIndentedString(Object o) { + if (o == null) { + return "null"; + } + return o.toString().replace("\n", "\n "); + } + +} + diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceipt.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceipt.java index 5e5d9f9cb9..04f9a28deb 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceipt.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceipt.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceiptRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceiptRequest.java index cbe1c29251..47cf731e61 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceiptRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceiptRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceiptResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceiptResponse.java index dbe59500d9..1d00cdb689 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceiptResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionReceiptResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatus.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatus.java index 7359b3f169..e267b1f8d3 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatus.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatus.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatusRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatusRequest.java index b8bc2d2460..4650fd792f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatusRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatusRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatusResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatusResponse.java index 2c330b9fdd..1e58b2c7df 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatusResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionStatusResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorDetails.java index b5f7b4fac9..ae8b6d526d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorDetailsType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorDetailsType.java index bbb8464412..daba6e1061 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorDetailsType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorDetailsType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorResponse.java index 8314bec966..7f08d3d21e 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorResponseAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorResponseAllOf.java index 9346013c58..894979545f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorResponseAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitErrorResponseAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitIntentAlreadyCommitted.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitIntentAlreadyCommitted.java index 06329d4625..01030bfa99 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitIntentAlreadyCommitted.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitIntentAlreadyCommitted.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitPriorityThresholdNotMetErrorDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitPriorityThresholdNotMetErrorDetails.java index b55c7f13ba..c3fe61c8ad 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitPriorityThresholdNotMetErrorDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitPriorityThresholdNotMetErrorDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitRejectedErrorDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitRejectedErrorDetails.java index 598fe2d4eb..5e15fc948d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitRejectedErrorDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitRejectedErrorDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitRequest.java index 941109fc2a..388afe4879 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitResponse.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitResponse.java index 1980a3233e..ee6036f919 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionSubmitResponse.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntrySubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntrySubstate.java index 495aef26b8..44ef40d7db 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntrySubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntrySubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntrySubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntrySubstateAllOf.java index 5be0b6f657..2aa2ab5daf 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntrySubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntrySubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntryValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntryValue.java index 452ace006f..c5187969d8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntryValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerCollectionEntryValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateSubstate.java index 6eb40167da..7c7517cf17 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateSubstateAllOf.java index ed5f62e280..b88467fdef 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateValue.java index 1b3fa58878..1f197f9c9a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerFieldStateValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerTransactionStatus.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerTransactionStatus.java index 54af4eb0c6..8910195ba8 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerTransactionStatus.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TransactionTrackerTransactionStatus.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateSubstate.java index a841adeb74..71aab697fe 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateSubstateAllOf.java index 1a70c2bdb0..62fbc77067 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateValue.java index a69890a48f..9817c80f54 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TwoResourcePoolFieldStateValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoDetails.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoDetails.java index 4a9ac7951c..355bd26d21 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoDetails.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoSubstate.java index 359ab54f99..610bfc8875 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoSubstateAllOf.java index b470a64e6d..e72921eda5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoValue.java index 65192e8355..5a2235f63b 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoModuleFieldTypeInfoValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoType.java index 82232d0194..7d6949ebfd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/TypeInfoType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/UpdatedSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/UpdatedSubstate.java index 5bc39e28b5..bcadcd9290 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/UpdatedSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/UpdatedSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/UserLedgerTransaction.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/UserLedgerTransaction.java index 77e912b973..577f0c2606 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/UserLedgerTransaction.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/UserLedgerTransaction.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/UserLedgerTransactionAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/UserLedgerTransactionAllOf.java index 5658b81b1e..f1e6e6a7fd 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/UserLedgerTransactionAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/UserLedgerTransactionAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFeeChangeRequest.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFeeChangeRequest.java index 938da07f73..e2d3c30de5 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFeeChangeRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFeeChangeRequest.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstate.java index b2453e3933..29664cfe42 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstateAllOf.java index 85416dceae..13660ffc9f 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalValue.java index f2890c5046..4f38f69862 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldProtocolUpdateReadinessSignalValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateSubstate.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateSubstate.java index 53d989d9eb..64a0d289b6 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateSubstate.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateSubstate.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateSubstateAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateSubstateAllOf.java index 85f6e048dd..8fae029e24 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateSubstateAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateSubstateAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateValue.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateValue.java index 18a5835988..30d455f2ed 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateValue.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/ValidatorFieldStateValue.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/VaultBalance.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/VaultBalance.java index 0fb4e21703..d91093943a 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/VaultBalance.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/VaultBalance.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/VersionLedgerStateSelector.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/VersionLedgerStateSelector.java index 4f2171cebd..48445edee2 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/VersionLedgerStateSelector.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/VersionLedgerStateSelector.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/VersionLedgerStateSelectorAllOf.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/VersionLedgerStateSelectorAllOf.java index 5f9e668af1..948b73115d 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/VersionLedgerStateSelectorAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/VersionLedgerStateSelectorAllOf.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/VirtualLazyLoadSchema.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/VirtualLazyLoadSchema.java index 48646dca45..da1aeb0600 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/VirtualLazyLoadSchema.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/VirtualLazyLoadSchema.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/core/generated/models/VmType.java b/core/src/test-core/java/com/radixdlt/api/core/generated/models/VmType.java index 030d0e06f0..4d5a202e48 100644 --- a/core/src/test-core/java/com/radixdlt/api/core/generated/models/VmType.java +++ b/core/src/test-core/java/com/radixdlt/api/core/generated/models/VmType.java @@ -1,8 +1,8 @@ /* - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/AttachedModulesApi.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/AttachedModulesApi.java index 6ca185b44c..48329b4c4b 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/AttachedModulesApi.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/AttachedModulesApi.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/EntitiesApi.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/EntitiesApi.java index 04f675413b..56a84faa01 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/EntitiesApi.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/EntitiesApi.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/ExtraApi.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/ExtraApi.java index a8aac7e2d1..d8975d61c5 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/ExtraApi.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/ExtraApi.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/KvStoresApi.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/KvStoresApi.java index 437e237a33..4044526ff2 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/KvStoresApi.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/KvStoresApi.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/ObjectsApi.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/ObjectsApi.java index 8958244034..31b8832241 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/ObjectsApi.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/ObjectsApi.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/TypesApi.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/TypesApi.java index a27ab6e324..f687f3b2e2 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/TypesApi.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/api/TypesApi.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiClient.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiClient.java index 391c98ee85..2df85ee035 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiClient.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiClient.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiException.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiException.java index b800ff8165..c33184e057 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiException.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiException.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiResponse.java index f89952bac3..be51e8698e 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/ApiResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/Configuration.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/Configuration.java index b32f7cf195..ebe3978b0b 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/Configuration.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/Configuration.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/Pair.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/Pair.java index 8c7ebd1496..6e42ce459d 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/Pair.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/Pair.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/RFC3339DateFormat.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/RFC3339DateFormat.java index 4ecbe5d214..761ea877f2 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/RFC3339DateFormat.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/client/RFC3339DateFormat.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AbstractOpenApiSchema.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AbstractOpenApiSchema.java index d5e461f6ec..059160cffb 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AbstractOpenApiSchema.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AbstractOpenApiSchema.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRule.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRule.java index b5466dbbd5..03bd607b26 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRule.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRule.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleNode.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleNode.java index 53f3c324f7..03a72e94b7 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleNode.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleNode.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleNodeType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleNodeType.java index c5669d7565..30015fad55 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleNodeType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleNodeType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleType.java index a49ddf1d06..957154dd3e 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AccessRuleType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfAccessRuleNode.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfAccessRuleNode.java index 0b2de4382b..f446592093 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfAccessRuleNode.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfAccessRuleNode.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfProofRule.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfProofRule.java index 781cddbbdb..5dc769a2ad 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfProofRule.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfProofRuleAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfProofRuleAllOf.java index de4124c21b..b340250ef5 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfProofRuleAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllOfProofRuleAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllowAllAccessRule.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllowAllAccessRule.java index bdc7be148f..fed2ff8375 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllowAllAccessRule.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AllowAllAccessRule.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AmountOfProofRule.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AmountOfProofRule.java index 0f9c1818dd..7436e31c5b 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AmountOfProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AmountOfProofRule.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AmountOfProofRuleAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AmountOfProofRuleAllOf.java index 7cfed925ca..ee85a83a32 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AmountOfProofRuleAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AmountOfProofRuleAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyGenericTypeParameter.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyGenericTypeParameter.java index 741a2cea76..a57c6a0eeb 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyGenericTypeParameter.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyGenericTypeParameter.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfAccessRuleNode.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfAccessRuleNode.java index 160d723c14..7a9dfb8ef0 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfAccessRuleNode.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfAccessRuleNode.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfAccessRuleNodeAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfAccessRuleNodeAllOf.java index ae9d43e955..d323fc8c34 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfAccessRuleNodeAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfAccessRuleNodeAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfProofRule.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfProofRule.java index c7d50c144e..56d537384d 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AnyOfProofRule.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/Assignment.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/Assignment.java index 3bad218a09..936aa8e173 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/Assignment.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/Assignment.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AssignmentType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AssignmentType.java index 385d73fea0..e4a9ef9456 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AssignmentType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AssignmentType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AttachedModuleId.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AttachedModuleId.java index d29514b988..cc12bc57e6 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AttachedModuleId.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/AttachedModuleId.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintCollectionInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintCollectionInfo.java index 0f896f987e..1227ccf314 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintCollectionInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintCollectionInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintEventInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintEventInfo.java index 10df0d0b38..55448dc7b0 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintEventInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintEventInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldCondition.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldCondition.java index 8a3b11c89b..5751c8fa82 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldCondition.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldCondition.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldConditionType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldConditionType.java index 22b5cd1e95..11eb5db3b5 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldConditionType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldConditionType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldInfo.java index 5ba4b55d55..dc440bffd2 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldTransience.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldTransience.java index 73a259db28..3ac7d4b030 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldTransience.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFieldTransience.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFilter.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFilter.java index 023f422885..f314e9cbe8 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFilter.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFilter.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFilterAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFilterAllOf.java index e2332db151..cd79aec0bb 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFilterAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFilterAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionAuthorization.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionAuthorization.java index 39c329096b..e7ed61d760 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionAuthorization.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionAuthorization.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionAuthorizationType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionAuthorizationType.java index 8ea4724169..bc9b48aa7e 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionAuthorizationType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionAuthorizationType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionInfo.java index 5139ba6efe..bbc37bd0b3 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintFunctionInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintGenericTypeReference.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintGenericTypeReference.java index ad448e6921..9486e75565 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintGenericTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintGenericTypeReference.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintGenericTypeReferenceAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintGenericTypeReferenceAllOf.java index 52f2e01aa6..c2e5fe2280 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintGenericTypeReferenceAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintGenericTypeReferenceAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintInfoRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintInfoRequest.java index b81219e487..94c8b4b861 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintInfoRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintInfoRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintInfoResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintInfoResponse.java index 8a0eb5524c..3ea079cff1 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintInfoResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintInfoResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodAuthorization.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodAuthorization.java index bb8899bfed..3e86438dcd 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodAuthorization.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodAuthorization.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodAuthorizationType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodAuthorizationType.java index 0d6c0ec44c..e59eeae7aa 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodAuthorizationType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodAuthorizationType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodInfo.java index 0ace79577b..16d3158c7e 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodReceiverInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodReceiverInfo.java index 7bd8ea9e2d..b87a179858 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodReceiverInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintMethodReceiverInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintNamedTypeInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintNamedTypeInfo.java index dda58e4965..ba1bf2c793 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintNamedTypeInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintNamedTypeInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintReference.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintReference.java index c6e5b381e4..d1040f2e09 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintReference.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintReference.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintResolvedTypeReference.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintResolvedTypeReference.java index e514ae0d2d..a4c3b6be81 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintResolvedTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintResolvedTypeReference.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintResolvedTypeReferenceType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintResolvedTypeReferenceType.java index abd39b4320..ffb01ddc83 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintResolvedTypeReferenceType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintResolvedTypeReferenceType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRoleInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRoleInfo.java index 9faf3b5ed1..f87bf01879 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRoleInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRoleInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRolesDefinition.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRolesDefinition.java index 2445cc92c4..ad617b9067 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRolesDefinition.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRolesDefinition.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRolesDefinitionType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRolesDefinitionType.java index 7a4d895cb2..c6646ce073 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRolesDefinitionType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintRolesDefinitionType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintStaticTypeReference.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintStaticTypeReference.java index 0b32afb97e..fa6d522d81 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintStaticTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintStaticTypeReference.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintStaticTypeReferenceAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintStaticTypeReferenceAllOf.java index ea7fc5a093..ce077f118c 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintStaticTypeReferenceAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BlueprintStaticTypeReferenceAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolArrayMetadataValue.java index 0e742367b8..5260baae7f 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolArrayMetadataValueAllOf.java index c9245e8541..9248d3173b 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolMetadataValue.java index 88871ff522..944a86ec46 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolMetadataValueAllOf.java index f0bb6739bf..4b3d906c47 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/BoolMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByAccessRuleBlueprintFunctionAuthorization.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByAccessRuleBlueprintFunctionAuthorization.java index 1b6256cb0a..102d2c5ccc 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByAccessRuleBlueprintFunctionAuthorization.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByAccessRuleBlueprintFunctionAuthorization.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByAccessRuleBlueprintFunctionAuthorizationAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByAccessRuleBlueprintFunctionAuthorizationAllOf.java index f2c74cdb9b..5e2fabee47 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByAccessRuleBlueprintFunctionAuthorizationAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByAccessRuleBlueprintFunctionAuthorizationAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByRolesBlueprintMethodAuthorization.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByRolesBlueprintMethodAuthorization.java index 94f87c258f..54a2639d40 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByRolesBlueprintMethodAuthorization.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByRolesBlueprintMethodAuthorization.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByRolesBlueprintMethodAuthorizationAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByRolesBlueprintMethodAuthorizationAllOf.java index 5b9e4d66e7..eaaaa3faa9 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByRolesBlueprintMethodAuthorizationAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ByRolesBlueprintMethodAuthorizationAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CollectionEntryKey.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CollectionEntryKey.java index 202c7a8904..3bb45478ac 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CollectionEntryKey.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CollectionEntryKey.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ConsensusInstant.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ConsensusInstant.java index f36ad6bc24..8381634d1a 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ConsensusInstant.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ConsensusInstant.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CountOfProofRule.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CountOfProofRule.java index 901cf97a32..9a0b38b929 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CountOfProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CountOfProofRule.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CountOfProofRuleAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CountOfProofRuleAllOf.java index 55d37c04df..13676a0263 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CountOfProofRuleAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/CountOfProofRuleAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalArrayMetadataValue.java index 0f6bcc5e25..94cdb9b2fa 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalArrayMetadataValueAllOf.java index 312f64279c..4ad8bf2499 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalMetadataValue.java index e6d9dbf45e..674d17ae3a 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalMetadataValueAllOf.java index 716c4a8e3e..f0c81e89df 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DecimalMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DenyAllAccessRule.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DenyAllAccessRule.java index 51ea22c57a..3d0e63a38d 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DenyAllAccessRule.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DenyAllAccessRule.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DetailedBlueprintInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DetailedBlueprintInfo.java index 10956fc2f6..4d68f5579c 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DetailedBlueprintInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/DetailedBlueprintInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EcdsaSecp256k1PublicKey.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EcdsaSecp256k1PublicKey.java index 15f5c43a6d..716ad103aa 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EcdsaSecp256k1PublicKey.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EcdsaSecp256k1PublicKey.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EcdsaSecp256k1PublicKeyAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EcdsaSecp256k1PublicKeyAllOf.java index 220cf9e601..e6519aab00 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EcdsaSecp256k1PublicKeyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EcdsaSecp256k1PublicKeyAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EddsaEd25519PublicKey.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EddsaEd25519PublicKey.java index db57beea6a..a2b49077f0 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EddsaEd25519PublicKey.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EddsaEd25519PublicKey.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EddsaEd25519PublicKeyAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EddsaEd25519PublicKeyAllOf.java index 82df1aaac6..5f99d33142 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EddsaEd25519PublicKeyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EddsaEd25519PublicKeyAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityAncestryInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityAncestryInfo.java index d1adf43813..b78b3f30a9 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityAncestryInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityAncestryInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfo.java index f106b70c62..9fecd15d43 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfoRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfoRequest.java index 011bb1eac5..274fba8d5b 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfoRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfoRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfoResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfoResponse.java index d40f2a119b..aa6c5a8db8 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfoResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityInfoResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySchemaEntryRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySchemaEntryRequest.java index 3e99677c4d..5c17cfb9ef 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySchemaEntryRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySchemaEntryRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySchemaEntryResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySchemaEntryResponse.java index 4fefbcb2b1..2049ca68bb 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySchemaEntryResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySchemaEntryResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySearchFilter.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySearchFilter.java index b0f4e06593..0d20de868c 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySearchFilter.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySearchFilter.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySearchFilterType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySearchFilterType.java index 5ceff43b72..67dc11b6fb 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySearchFilterType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntitySearchFilterType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityType.java index fd64c84b60..f371554802 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityTypeFilter.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityTypeFilter.java index aa8e361f8a..aaa37be698 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityTypeFilter.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityTypeFilter.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityTypeFilterAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityTypeFilterAllOf.java index a84aa1f6f1..cfafa52a69 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityTypeFilterAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EntityTypeFilterAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EpochRound.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EpochRound.java index 4abb7b3088..d992a1cc92 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EpochRound.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/EpochRound.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorDetails.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorDetails.java index 51ab9a045b..da58d61bf4 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorDetails.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorResponse.java index 41c31187f9..d7a915c3b8 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorType.java index 343cd77847..026561a5c9 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ErrorType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExplicitAssignment.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExplicitAssignment.java index ab51bf6128..14dbefeea6 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExplicitAssignment.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExplicitAssignment.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExtraEntitySearchRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExtraEntitySearchRequest.java index 7603e7a379..6d35049607 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExtraEntitySearchRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExtraEntitySearchRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExtraEntitySearchResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExtraEntitySearchResponse.java index 0109bdfe6f..ce9312a394 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExtraEntitySearchResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ExtraEntitySearchResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GenericTypeParameter.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GenericTypeParameter.java index d461b28f27..b4af974168 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GenericTypeParameter.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GenericTypeParameter.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GenericTypeParameterType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GenericTypeParameterType.java index fc9ba1ae0f..e215e1c922 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GenericTypeParameterType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GenericTypeParameterType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressArrayMetadataValue.java index e5a1666f51..070d81ab8b 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressArrayMetadataValueAllOf.java index 6c6e193312..b531f60816 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressMetadataValue.java index 5ad1b9a714..53e51a15fa 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressMetadataValueAllOf.java index 489b430651..94bffd11e6 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/GlobalAddressMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32ArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32ArrayMetadataValue.java index 295ce87a0e..fd904d2d87 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32ArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32ArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32ArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32ArrayMetadataValueAllOf.java index a373ba0c39..09fb3a3dcb 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32ArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32ArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32MetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32MetadataValue.java index d2b0b59b72..d8a2ad4cd2 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32MetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32MetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32MetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32MetadataValueAllOf.java index d069dfde85..7e67f67742 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32MetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I32MetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64ArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64ArrayMetadataValue.java index b5fd350af2..71f27449f4 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64ArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64ArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64ArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64ArrayMetadataValueAllOf.java index eda7977f12..f2b8ad0635 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64ArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64ArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64MetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64MetadataValue.java index ac883a76a6..0ab16b85a5 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64MetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64MetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64MetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64MetadataValueAllOf.java index 9b2857adf1..36366ef5aa 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64MetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/I64MetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOuterObjectFeatureFieldCondition.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOuterObjectFeatureFieldCondition.java index 8dac906bc5..4b4c2f3c7b 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOuterObjectFeatureFieldCondition.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOuterObjectFeatureFieldCondition.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOwnFeatureFieldCondition.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOwnFeatureFieldCondition.java index 1bc16ccdb1..bc038aeb20 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOwnFeatureFieldCondition.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOwnFeatureFieldCondition.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOwnFeatureFieldConditionAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOwnFeatureFieldConditionAllOf.java index 36ddd6819f..9bcb3db5b8 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOwnFeatureFieldConditionAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IfOwnFeatureFieldConditionAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IndexEntryKey.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IndexEntryKey.java index 33237053d9..207c8a011e 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IndexEntryKey.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/IndexEntryKey.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantArrayMetadataValue.java index c0bb78d0c7..82053b62ae 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantArrayMetadataValueAllOf.java index 838d002d0f..8a80d5bec8 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantMetadataValue.java index 0a189650ae..c3a01a7532 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantMetadataValueAllOf.java index 3fe2e194b5..9dbe67696b 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/InstantMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntityInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntityInfo.java index 0d106dabc8..c185c7f107 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntityInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntityInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntityInfoAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntityInfoAllOf.java index 203571e749..68d55bbc15 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntityInfoAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntityInfoAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryKey.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryKey.java index 0d16138d67..02c4672b0e 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryKey.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryKey.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryKeyAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryKeyAllOf.java index 668838d80c..445f9f8a12 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryKeyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryKeyAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryRequest.java index 244af8c70e..afedccf372 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryResponse.java index bd3ac5ff50..67b763a8db 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreEntryResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreIteratorRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreIteratorRequest.java index 4321b5fc92..3b08ad318c 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreIteratorRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreIteratorRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreIteratorResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreIteratorResponse.java index c75ab11c75..e4bef249dd 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreIteratorResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreIteratorResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreMapKey.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreMapKey.java index 1e9d19d9a8..c010aefb5a 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreMapKey.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/KeyValueStoreMapKey.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerHashes.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerHashes.java index 259c346423..8ba34c0c49 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerHashes.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerHashes.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerHeaderSummary.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerHeaderSummary.java index c150c43419..ff068d70e5 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerHeaderSummary.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerHeaderSummary.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSelector.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSelector.java index 494d9acc85..2a6e784e42 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSelector.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSelector.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSelectorType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSelectorType.java index fb3b7b9b58..90ecf170ba 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSelectorType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSelectorType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSummary.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSummary.java index 8245c83cfb..df35480816 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSummary.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LedgerStateSummary.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ListedEntityItem.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ListedEntityItem.java index 54ca8f49df..6ac949407a 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ListedEntityItem.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ListedEntityItem.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LocalBlueprintRolesDefinition.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LocalBlueprintRolesDefinition.java index 4903ebc53e..55108a636c 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LocalBlueprintRolesDefinition.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LocalBlueprintRolesDefinition.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LocalBlueprintRolesDefinitionAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LocalBlueprintRolesDefinitionAllOf.java index d1976361b7..2001740aa6 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LocalBlueprintRolesDefinitionAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/LocalBlueprintRolesDefinitionAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataEntryKey.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataEntryKey.java index 2e4f29692b..ff5a3cdc3d 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataEntryKey.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataEntryKey.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataValue.java index 7cdd87b5e6..4455f8c8b4 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataValueType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataValueType.java index 1aaeb39d14..7872a68ec0 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataValueType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MetadataValueType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MethodReceiverReferenceType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MethodReceiverReferenceType.java index 7aba5ecc58..54a33dbbd8 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MethodReceiverReferenceType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MethodReceiverReferenceType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MethodReceiverType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MethodReceiverType.java index b9c7061c6a..77e10484bb 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MethodReceiverType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/MethodReceiverType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalId.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalId.java index f1234355bf..602aa550cc 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalId.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalId.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdArrayMetadataValue.java index b1070e4032..449d712d8e 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdArrayMetadataValueAllOf.java index 734cf62999..5bca0e60d2 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdMetadataValue.java index 9d068ecb6d..4e474cec1a 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdMetadataValueAllOf.java index 5c9df530cd..4c734b648c 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleGlobalIdMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdArrayMetadataValue.java index f509735b4a..24fc0fa7a5 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdArrayMetadataValueAllOf.java index 02ff604e30..6173e285e7 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdMetadataValue.java index 948e72e0ac..ebeff59e7a 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdMetadataValueAllOf.java index 16dc41e57f..77b7d03f62 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleLocalIdMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleRequirement.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleRequirement.java index 7f41fec67b..a24d0ef006 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleRequirement.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleRequirement.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleRequirementAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleRequirementAllOf.java index e226eb580b..200056901b 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleRequirementAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/NonFungibleRequirementAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionEntryRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionEntryRequest.java index 3aff2e8a12..33c321d125 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionEntryRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionEntryRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionEntryResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionEntryResponse.java index 0a078cca40..0401e62dfe 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionEntryResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionEntryResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionInfo.java index 73b33fb911..af0351244b 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionIteratorRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionIteratorRequest.java index 121a73a7b7..5658e9dfa8 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionIteratorRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionIteratorRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionIteratorResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionIteratorResponse.java index 8569484e3d..91a6016f51 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionIteratorResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionIteratorResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionKind.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionKind.java index 4e8d62e7e7..bd029bd5d2 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionKind.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectCollectionKind.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfo.java index fa77611bc6..53f16fffa9 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfoAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfoAllOf.java index b2bd5d7630..de9e993ccf 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfoAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfoAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfoAllOfAttachedModules.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfoAllOfAttachedModules.java index 648488a77b..cca8382489 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfoAllOfAttachedModules.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectEntityInfoAllOfAttachedModules.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldInfo.java index 1de36f4d6b..daaa9f2fc7 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldRequest.java index 34f79413c3..9e16ffb242 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldResponse.java index 98cc68764f..d32435c702 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectFieldResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectInstanceInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectInstanceInfo.java index 9b34e03198..8f104645ce 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectInstanceInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectInstanceInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataEntryRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataEntryRequest.java index 7adf294613..ecd07feca3 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataEntryRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataEntryRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataEntryResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataEntryResponse.java index 50cdefe451..d38255da41 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataEntryResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataEntryResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataIteratorRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataIteratorRequest.java index 5f516d206b..5bd0a87992 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataIteratorRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataIteratorRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataIteratorResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataIteratorResponse.java index e003dd2cb9..fd99775df8 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataIteratorResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMetadataIteratorResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMethodRoyalty.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMethodRoyalty.java index 555e48e76b..208a7102cb 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMethodRoyalty.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectMethodRoyalty.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectModuleStateInfo.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectModuleStateInfo.java index 64e2a188be..771b88d8f4 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectModuleStateInfo.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectModuleStateInfo.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentRequest.java index 455fb76b36..a08aa9f556 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentResponse.java index 52bbb4eb0a..5389a85a65 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentResponseAttachedModulesInner.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentResponseAttachedModulesInner.java index c1a0a9d512..59209699a5 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentResponseAttachedModulesInner.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoleAssignmentResponseAttachedModulesInner.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoyaltyRequest.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoyaltyRequest.java index 5494e240b3..70780ea7b3 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoyaltyRequest.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoyaltyRequest.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoyaltyResponse.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoyaltyResponse.java index d2184e7158..dc5c61b65a 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoyaltyResponse.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ObjectRoyaltyResponse.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OriginArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OriginArrayMetadataValue.java index a9474f3bac..3583efb9d1 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OriginArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OriginArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OriginMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OriginMetadataValue.java index 6a614d41f2..c7cfd6dfda 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OriginMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OriginMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OuterBlueprintRolesDefinition.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OuterBlueprintRolesDefinition.java index c9380b1f4e..5757f99183 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OuterBlueprintRolesDefinition.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OuterBlueprintRolesDefinition.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OuterObjectOnlyBlueprintMethodAuthorization.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OuterObjectOnlyBlueprintMethodAuthorization.java index e3bc6ae92a..1ba448a443 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OuterObjectOnlyBlueprintMethodAuthorization.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OuterObjectOnlyBlueprintMethodAuthorization.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnPackageOnlyBlueprintMethodAuthorization.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnPackageOnlyBlueprintMethodAuthorization.java index 88fb16fe9d..397762452c 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnPackageOnlyBlueprintMethodAuthorization.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnPackageOnlyBlueprintMethodAuthorization.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerAssignment.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerAssignment.java index e6ed524fd9..30cf3864ee 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerAssignment.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerAssignment.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerRoleEntry.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerRoleEntry.java index 8f6920cdae..b97c8dda51 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerRoleEntry.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerRoleEntry.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerRoleUpdater.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerRoleUpdater.java index d72aa2ceb9..cab1f4a60d 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerRoleUpdater.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/OwnerRoleUpdater.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofAccessRuleNode.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofAccessRuleNode.java index aa5f880a5a..72dc04e492 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofAccessRuleNode.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofAccessRuleNode.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofAccessRuleNodeAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofAccessRuleNodeAllOf.java index d6358d4ae0..787f2b4bb3 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofAccessRuleNodeAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofAccessRuleNodeAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofRule.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofRule.java index c20623a82f..4fa5e668ae 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofRule.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofRuleType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofRuleType.java index c45d4b6d0e..77dc8e1d70 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofRuleType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProofRuleType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProtectedAccessRule.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProtectedAccessRule.java index a7a046ff65..bea95cbf51 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProtectedAccessRule.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProtectedAccessRule.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProtectedAccessRuleAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProtectedAccessRuleAllOf.java index 5a6a5cb05f..84812f2af0 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProtectedAccessRuleAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ProtectedAccessRuleAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicBlueprintFunctionAuthorization.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicBlueprintFunctionAuthorization.java index 7e6ccb9cdc..193d9de0b7 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicBlueprintFunctionAuthorization.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicBlueprintFunctionAuthorization.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicBlueprintMethodAuthorization.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicBlueprintMethodAuthorization.java index a29bef5709..0991e78c9e 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicBlueprintMethodAuthorization.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicBlueprintMethodAuthorization.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKey.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKey.java index 5795a4a6a0..2d2eeea780 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKey.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKey.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyArrayMetadataValue.java index 0b03fe0141..6116b09541 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyArrayMetadataValueAllOf.java index 4bf8e403e7..2a08e0d800 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHash.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHash.java index 3fe9ca6543..12009f96b6 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHash.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHash.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashArrayMetadataValue.java index bea449c2d3..5abd055670 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashArrayMetadataValueAllOf.java index 231ca5d0a7..b6c05c8a02 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashMetadataValue.java index 855d930c90..9b1da3b966 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashMetadataValueAllOf.java index 86df21c3b9..ae6f59e9ec 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyHashMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyMetadataValue.java index 3dfdf1b630..9fcceb6517 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyMetadataValueAllOf.java index 57762ee47b..1d777e3436 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyType.java index fa5eb83ac2..2c0f9a28ae 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/PublicKeyType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemInvalidDetails.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemInvalidDetails.java index 19ab38f553..54d5550c64 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemInvalidDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemInvalidDetails.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemNotFoundDetails.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemNotFoundDetails.java index 6261b42988..cad7f22fa8 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemNotFoundDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemNotFoundDetails.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemNotFoundDetailsAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemNotFoundDetailsAllOf.java index 3e7a16dbdf..9c729a0123 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemNotFoundDetailsAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemNotFoundDetailsAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemType.java index 3f862d212c..c541cb5560 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequestedItemType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequireProofRule.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequireProofRule.java index 9014a60071..879011310d 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequireProofRule.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequireProofRule.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequireProofRuleAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequireProofRuleAllOf.java index 8a0e6eb118..9f4dbd84a4 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequireProofRuleAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequireProofRuleAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/Requirement.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/Requirement.java index c2c8b887d9..a6b32d8cf3 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/Requirement.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/Requirement.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequirementType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequirementType.java index 2c318e339e..ea1f6b750d 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequirementType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RequirementType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResolvedTypeReference.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResolvedTypeReference.java index dd22a2d2da..509a0ae45f 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResolvedTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResolvedTypeReference.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResolvedTypeReferenceType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResolvedTypeReferenceType.java index ffa3f1752b..0d0e5187d5 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResolvedTypeReferenceType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResolvedTypeReferenceType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResourceRequirement.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResourceRequirement.java index 3fc887dcd6..355573d150 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResourceRequirement.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResourceRequirement.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResourceRequirementAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResourceRequirementAllOf.java index ae7d15d4f5..347d2e119e 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResourceRequirementAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ResourceRequirementAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RoleAssignmentEntry.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RoleAssignmentEntry.java index fba6796a33..0a52f0e76c 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RoleAssignmentEntry.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RoleAssignmentEntry.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RootOnlyBlueprintFunctionAuthorization.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RootOnlyBlueprintFunctionAuthorization.java index 0efdfd7f71..0e261ee7b6 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RootOnlyBlueprintFunctionAuthorization.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RootOnlyBlueprintFunctionAuthorization.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RoyaltyAmount.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RoyaltyAmount.java index fa6c01ed32..31c2ab874a 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RoyaltyAmount.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/RoyaltyAmount.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SborData.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SborData.java index cc51cb5cdd..260e495db6 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SborData.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SborData.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SborFormatOptions.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SborFormatOptions.java index cd794e9f67..8ce6ac6155 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SborFormatOptions.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SborFormatOptions.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaDefinedTypeReference.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaDefinedTypeReference.java index 942b65d70d..0909933945 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaDefinedTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaDefinedTypeReference.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaDefinedTypeReferenceAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaDefinedTypeReferenceAllOf.java index 817a322314..50ef856e2b 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaDefinedTypeReferenceAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaDefinedTypeReferenceAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaReference.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaReference.java index 533cc54d5e..46bcdc3d10 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaReference.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SchemaReference.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ScryptoInstant.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ScryptoInstant.java index 6c3811f41d..9db6844bab 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ScryptoInstant.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/ScryptoInstant.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SortedIndexEntryKey.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SortedIndexEntryKey.java index c1f1a22f0a..57984a092a 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SortedIndexEntryKey.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SortedIndexEntryKey.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SortedIndexEntryKeyAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SortedIndexEntryKeyAllOf.java index d81281e71e..3d18a604bc 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SortedIndexEntryKeyAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SortedIndexEntryKeyAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInFutureDetails.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInFutureDetails.java index f51724496c..a08944dfca 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInFutureDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInFutureDetails.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInFutureDetailsAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInFutureDetailsAllOf.java index 7ca84577c7..54e53e0335 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInFutureDetailsAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInFutureDetailsAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInTooDistantPastDetails.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInTooDistantPastDetails.java index cf6b7a54ad..33c95553f9 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInTooDistantPastDetails.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInTooDistantPastDetails.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInTooDistantPastDetailsAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInTooDistantPastDetailsAllOf.java index 03b8c63ae6..9a7362cf52 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInTooDistantPastDetailsAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StateVersionInTooDistantPastDetailsAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringArrayMetadataValue.java index 537042d95e..a8f4bdc9b3 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringArrayMetadataValueAllOf.java index 1b3b338890..52dad29a5f 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringMetadataValue.java index 2cadfb6e1b..bc2c06a656 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringMetadataValueAllOf.java index be5a31003b..eb1d50068a 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/StringMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemType.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemType.java index 4a81289900..8ee7de0ec3 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemType.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemType.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemTypeFilter.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemTypeFilter.java index 70e487d29e..d20887763c 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemTypeFilter.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemTypeFilter.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemTypeFilterAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemTypeFilterAllOf.java index b69dd3d54f..692775f008 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemTypeFilterAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/SystemTypeFilterAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32ArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32ArrayMetadataValue.java index 5da79bc784..cceec0bf07 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32ArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32ArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32ArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32ArrayMetadataValueAllOf.java index 7dc466ff54..194e53d6b9 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32ArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32ArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32MetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32MetadataValue.java index 4413e9a093..48242b6bf0 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32MetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32MetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32MetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32MetadataValueAllOf.java index af262fb91f..0b3a397c2e 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32MetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U32MetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64ArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64ArrayMetadataValue.java index fdc80a5b9a..730531c119 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64ArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64ArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64ArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64ArrayMetadataValueAllOf.java index 63f3436b32..28c4c5ff71 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64ArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64ArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64MetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64MetadataValue.java index 8ca89e8e02..61610545ba 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64MetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64MetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64MetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64MetadataValueAllOf.java index 3e29c4274c..9df5e8ae9f 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64MetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U64MetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8ArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8ArrayMetadataValue.java index d0ed441bd9..bedc2b1d9a 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8ArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8ArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8ArrayMetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8ArrayMetadataValueAllOf.java index 658ef2b8c0..c699f40a72 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8ArrayMetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8ArrayMetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8MetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8MetadataValue.java index 8ac7500765..7583d3b3fb 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8MetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8MetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8MetadataValueAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8MetadataValueAllOf.java index ec4f218a88..06d3c9830d 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8MetadataValueAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/U8MetadataValueAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UnversionedBlueprintReference.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UnversionedBlueprintReference.java index 93d4f0b8ab..50647d3528 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UnversionedBlueprintReference.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UnversionedBlueprintReference.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UrlArrayMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UrlArrayMetadataValue.java index c6275c4064..aa01d2bd05 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UrlArrayMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UrlArrayMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UrlMetadataValue.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UrlMetadataValue.java index 1de3c2d8e6..5936de56ff 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UrlMetadataValue.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/UrlMetadataValue.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/VersionLedgerStateSelector.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/VersionLedgerStateSelector.java index 08d169168a..c7d90eebe5 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/VersionLedgerStateSelector.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/VersionLedgerStateSelector.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/VersionLedgerStateSelectorAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/VersionLedgerStateSelectorAllOf.java index c5d069edd4..18a27cb0ac 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/VersionLedgerStateSelectorAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/VersionLedgerStateSelectorAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/WellKnownTypeReference.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/WellKnownTypeReference.java index 2e50583139..cce2d0cfa2 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/WellKnownTypeReference.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/WellKnownTypeReference.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/WellKnownTypeReferenceAllOf.java b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/WellKnownTypeReferenceAllOf.java index 63cce9ec0f..977b4aef31 100644 --- a/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/WellKnownTypeReferenceAllOf.java +++ b/core/src/test-core/java/com/radixdlt/api/engine_state/generated/models/WellKnownTypeReferenceAllOf.java @@ -1,8 +1,8 @@ /* - * Engine State API - Babylon (Anemone) + * Engine State API (Beta) * **This API is currently in Beta** This specification may experience breaking changes as part of Babylon Node releases. Such changes will be clearly mentioned in the [babylon-node release notes](https://github.com/radixdlt/babylon-node/releases). We advise against using this API for business-critical integrations before the `version` indicated above becomes stable, which is expected in Q4 of 2024. This API provides a complete view of the current ledger state, operating at a relatively low level (i.e. returning Entities' data and type information in a generic way, without interpreting specifics of different native or custom components). It mirrors how the Radix Engine views the ledger state in its \"System\" layer, and thus can be useful for Scrypto developers, who need to inspect how the Engine models and stores their application's state, or how an interface / authentication scheme of another component looks like. * - * The version of the OpenAPI document: v0.1-beta + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/core/src/test/java/com/radixdlt/api/core/TransactionPreviewTest.java b/core/src/test/java/com/radixdlt/api/core/TransactionPreviewTest.java index 17783531b9..862d96a02d 100644 --- a/core/src/test/java/com/radixdlt/api/core/TransactionPreviewTest.java +++ b/core/src/test/java/com/radixdlt/api/core/TransactionPreviewTest.java @@ -331,6 +331,69 @@ public void transaction_previewed_with_message_consumes_more_cost_units() throws } } + @SuppressWarnings("DataFlowIssue") // Suppress invalid null reference warnings + @Test + public void transaction_previewed_doesnt_include_toolkit_receipt_by_default() throws Exception { + try (var test = buildRunningServerTest(defaultConfig())) { + test.suppressUnusedWarning(); + + // Prepare a request with the RET receipt opt-ins + var manifest = Manifest.valid().apply(new Manifest.Parameters(networkDefinition)); + var request = + new TransactionPreviewRequest() + .network(networkLogicalName) + .startEpochInclusive(0L) + .endEpochExclusive(100L) + .tipPercentage(1) + .nonce(10L) + .flags( + new TransactionPreviewRequestFlags() + .useFreeCredit(true) + .assumeAllSignatureProofs(true) + .skipEpochCheck(true)) + .manifest(manifest); + + // Ask for a preview of the manifest + var previewResponse = + getTransactionApi().transactionPreviewPost(request).getRadixEngineToolkitReceipt(); + + // Message should be included + assertThat(previewResponse).isNull(); + } + } + + @SuppressWarnings("DataFlowIssue") // Suppress invalid null reference warnings + @Test + public void transaction_previewed_includes_a_toolkit_receipt_when_requested() throws Exception { + try (var test = buildRunningServerTest(defaultConfig())) { + test.suppressUnusedWarning(); + + // Prepare a request with the RET receipt opt-ins + var manifest = Manifest.valid().apply(new Manifest.Parameters(networkDefinition)); + var request = + new TransactionPreviewRequest() + .network(networkLogicalName) + .startEpochInclusive(0L) + .endEpochExclusive(100L) + .tipPercentage(1) + .nonce(10L) + .flags( + new TransactionPreviewRequestFlags() + .useFreeCredit(true) + .assumeAllSignatureProofs(true) + .skipEpochCheck(true)) + .manifest(manifest) + .options(new TransactionPreviewResponseOptions().radixEngineToolkitReceipt(true)); + + // Ask for a preview of the manifest + var previewResponse = + getTransactionApi().transactionPreviewPost(request).getRadixEngineToolkitReceipt(); + + // Message should be included + assertThat(previewResponse).isNotNull(); + } + } + private TransactionPreviewResponse previewAtVersion( Functions.Func1 manifest, Optional atStateVersion) throws ApiException { diff --git a/core/src/test/java/com/radixdlt/p2p/hostip/NetworkQueryHostIpTest.java b/core/src/test/java/com/radixdlt/p2p/hostip/NetworkQueryHostIpTest.java index 6cbb0da7b6..95ac5e6563 100644 --- a/core/src/test/java/com/radixdlt/p2p/hostip/NetworkQueryHostIpTest.java +++ b/core/src/test/java/com/radixdlt/p2p/hostip/NetworkQueryHostIpTest.java @@ -111,22 +111,19 @@ public void testCollectionEmpty() { } @Test - public void testCollectionNotEmptyQueryFailed() throws IOException { - HttpURLConnection conn = mock(HttpURLConnection.class); - doReturn(404).when(conn).getResponseCode(); - URL url = mock(URL.class); - doReturn(conn).when(url).openConnection(); - NetworkQueryHostIp nqhip = NetworkQueryHostIp.create(List.of(url)); - Optional host = nqhip.queryNetworkHosts().maybeHostIp(); + public void testCollectionNotEmptyQueryNotSuccessful() throws IOException { + NetworkQueryHostIp nqhip = NetworkQueryHostIp.create(List.of(makeUrl(404, "not found"))); + Optional host = nqhip.queryNetworkHosts().conclusiveHostIp(); assertFalse(host.isPresent()); } @Test - public void testCollectionNotEmptyQueryFailed2() throws IOException { + public void testCollectionNotEmptyQueryIoException() throws IOException { URL url = mock(URL.class); + doReturn("https://mock.url/with-io-problems").when(url).toString(); doThrow(new IOException("test exception")).when(url).openConnection(); NetworkQueryHostIp nqhip = NetworkQueryHostIp.create(List.of(url)); - Optional host = nqhip.queryNetworkHosts().maybeHostIp(); + Optional host = nqhip.queryNetworkHosts().conclusiveHostIp(); assertFalse(host.isPresent()); } @@ -134,18 +131,24 @@ public void testCollectionNotEmptyQueryFailed2() throws IOException { public void testCollectionAllDifferent() throws IOException { List urls = List.of( - makeUrl("127.0.0.1"), makeUrl("127.0.0.2"), makeUrl("127.0.0.3"), makeUrl("127.0.0.4")); + makeUrl(200, "127.0.0.1"), + makeUrl(200, "127.0.0.2"), + makeUrl(200, "127.0.0.3"), + makeUrl(200, "127.0.0.4")); NetworkQueryHostIp nqhip = NetworkQueryHostIp.create(urls); - Optional host = nqhip.queryNetworkHosts().maybeHostIp(); + Optional host = nqhip.queryNetworkHosts().conclusiveHostIp(); assertFalse(host.isPresent()); } - private static URL makeUrl(String data) throws IOException { - ByteArrayInputStream input = new ByteArrayInputStream(data.getBytes(StandardCharsets.UTF_8)); + private static URL makeUrl(int status, String body) throws IOException { HttpURLConnection conn = mock(HttpURLConnection.class); - doReturn(input).when(conn).getInputStream(); + doReturn(status).when(conn).getResponseCode(); + doReturn(new ByteArrayInputStream(body.getBytes(StandardCharsets.UTF_8))) + .when(conn) + .getInputStream(); URL url = mock(URL.class); doReturn(conn).when(url).openConnection(); + doReturn("https://mock.url/?result=%s".formatted(body)).when(url).toString(); return url; } } diff --git a/docs/branching-strategy.md b/docs/branching-strategy.md index c1624aa33e..3187d53dcc 100644 --- a/docs/branching-strategy.md +++ b/docs/branching-strategy.md @@ -8,7 +8,6 @@ Once you have read the [contributing guide](../CONTRIBUTING.md), if you want to > As of 2024-05-15, the strictly ordered list of supported base branches, starting from earliest/furthest upstream, is: > > * `release/bottlenose` - This is currently running on mainnet. -> * `release/anemone` > * `main` > * `develop` > diff --git a/sdk/typescript/lib/generated/.openapi-generator/FILES b/sdk/typescript/lib/generated/.openapi-generator/FILES index 85c9b3d91b..109c99f0de 100644 --- a/sdk/typescript/lib/generated/.openapi-generator/FILES +++ b/sdk/typescript/lib/generated/.openapi-generator/FILES @@ -635,6 +635,7 @@ models/TransactionPreviewRequest.ts models/TransactionPreviewRequestFlags.ts models/TransactionPreviewResponse.ts models/TransactionPreviewResponseLogsInner.ts +models/TransactionPreviewResponseOptions.ts models/TransactionReceipt.ts models/TransactionReceiptRequest.ts models/TransactionReceiptResponse.ts diff --git a/sdk/typescript/lib/generated/apis/LTSApi.ts b/sdk/typescript/lib/generated/apis/LTSApi.ts index e09a31770d..9e22f2921b 100644 --- a/sdk/typescript/lib/generated/apis/LTSApi.ts +++ b/sdk/typescript/lib/generated/apis/LTSApi.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/apis/MempoolApi.ts b/sdk/typescript/lib/generated/apis/MempoolApi.ts index 11de62655c..e1c2e40ecb 100644 --- a/sdk/typescript/lib/generated/apis/MempoolApi.ts +++ b/sdk/typescript/lib/generated/apis/MempoolApi.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/apis/StateApi.ts b/sdk/typescript/lib/generated/apis/StateApi.ts index c01336732c..9dddaaca98 100644 --- a/sdk/typescript/lib/generated/apis/StateApi.ts +++ b/sdk/typescript/lib/generated/apis/StateApi.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/apis/StatusApi.ts b/sdk/typescript/lib/generated/apis/StatusApi.ts index 1ab4dc4afa..c7ad284015 100644 --- a/sdk/typescript/lib/generated/apis/StatusApi.ts +++ b/sdk/typescript/lib/generated/apis/StatusApi.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/apis/StreamApi.ts b/sdk/typescript/lib/generated/apis/StreamApi.ts index 3327ba40ae..7b6b03f739 100644 --- a/sdk/typescript/lib/generated/apis/StreamApi.ts +++ b/sdk/typescript/lib/generated/apis/StreamApi.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/apis/TransactionApi.ts b/sdk/typescript/lib/generated/apis/TransactionApi.ts index 57d4ac1f5e..8bcedef003 100644 --- a/sdk/typescript/lib/generated/apis/TransactionApi.ts +++ b/sdk/typescript/lib/generated/apis/TransactionApi.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccessControllerFieldStateSubstate.ts b/sdk/typescript/lib/generated/models/AccessControllerFieldStateSubstate.ts index 5fef021e23..7a2e164dfa 100644 --- a/sdk/typescript/lib/generated/models/AccessControllerFieldStateSubstate.ts +++ b/sdk/typescript/lib/generated/models/AccessControllerFieldStateSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccessControllerFieldStateSubstateAllOf.ts b/sdk/typescript/lib/generated/models/AccessControllerFieldStateSubstateAllOf.ts index 220d7bb967..94387bc814 100644 --- a/sdk/typescript/lib/generated/models/AccessControllerFieldStateSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/AccessControllerFieldStateSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccessControllerFieldStateValue.ts b/sdk/typescript/lib/generated/models/AccessControllerFieldStateValue.ts index 2590ea59e5..e91a47e6df 100644 --- a/sdk/typescript/lib/generated/models/AccessControllerFieldStateValue.ts +++ b/sdk/typescript/lib/generated/models/AccessControllerFieldStateValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccessRule.ts b/sdk/typescript/lib/generated/models/AccessRule.ts index 9c10cf9065..7e593d9546 100644 --- a/sdk/typescript/lib/generated/models/AccessRule.ts +++ b/sdk/typescript/lib/generated/models/AccessRule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccessRuleBase.ts b/sdk/typescript/lib/generated/models/AccessRuleBase.ts index de6d18071b..ca8e951769 100644 --- a/sdk/typescript/lib/generated/models/AccessRuleBase.ts +++ b/sdk/typescript/lib/generated/models/AccessRuleBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccessRuleNode.ts b/sdk/typescript/lib/generated/models/AccessRuleNode.ts index e6e54fa860..970ed0651b 100644 --- a/sdk/typescript/lib/generated/models/AccessRuleNode.ts +++ b/sdk/typescript/lib/generated/models/AccessRuleNode.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccessRuleNodeBase.ts b/sdk/typescript/lib/generated/models/AccessRuleNodeBase.ts index 1513e63f9e..d887d959b3 100644 --- a/sdk/typescript/lib/generated/models/AccessRuleNodeBase.ts +++ b/sdk/typescript/lib/generated/models/AccessRuleNodeBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccessRuleNodeType.ts b/sdk/typescript/lib/generated/models/AccessRuleNodeType.ts index 0093f257ce..30a1f2152c 100644 --- a/sdk/typescript/lib/generated/models/AccessRuleNodeType.ts +++ b/sdk/typescript/lib/generated/models/AccessRuleNodeType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccessRuleType.ts b/sdk/typescript/lib/generated/models/AccessRuleType.ts index 0459dd9d51..865599e95c 100644 --- a/sdk/typescript/lib/generated/models/AccessRuleType.ts +++ b/sdk/typescript/lib/generated/models/AccessRuleType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountAddressKey.ts b/sdk/typescript/lib/generated/models/AccountAddressKey.ts index 4da6b06cd4..38c9f3992c 100644 --- a/sdk/typescript/lib/generated/models/AccountAddressKey.ts +++ b/sdk/typescript/lib/generated/models/AccountAddressKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntrySubstate.ts b/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntrySubstate.ts index fe44bb8a0c..47023949e7 100644 --- a/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntrySubstateAllOf.ts index 660a94f988..229160ecfd 100644 --- a/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntryValue.ts b/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntryValue.ts index 8e83b5a3d9..bab7c5af0b 100644 --- a/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntryValue.ts +++ b/sdk/typescript/lib/generated/models/AccountAuthorizedDepositorEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountFieldStateSubstate.ts b/sdk/typescript/lib/generated/models/AccountFieldStateSubstate.ts index 61c6021f2b..b2346ab707 100644 --- a/sdk/typescript/lib/generated/models/AccountFieldStateSubstate.ts +++ b/sdk/typescript/lib/generated/models/AccountFieldStateSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountFieldStateSubstateAllOf.ts b/sdk/typescript/lib/generated/models/AccountFieldStateSubstateAllOf.ts index 7b1bee66f7..c12f246513 100644 --- a/sdk/typescript/lib/generated/models/AccountFieldStateSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/AccountFieldStateSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountFieldStateValue.ts b/sdk/typescript/lib/generated/models/AccountFieldStateValue.ts index 7a8f8b7ec8..efa4966434 100644 --- a/sdk/typescript/lib/generated/models/AccountFieldStateValue.ts +++ b/sdk/typescript/lib/generated/models/AccountFieldStateValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntrySubstate.ts b/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntrySubstate.ts index a4f9cb050b..9d752756e9 100644 --- a/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntrySubstateAllOf.ts index 50586a715b..5e47a69a2f 100644 --- a/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntryValue.ts b/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntryValue.ts index 9b9e03ee52..5a4fd87560 100644 --- a/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntryValue.ts +++ b/sdk/typescript/lib/generated/models/AccountLockerAccountClaimsEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntrySubstate.ts b/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntrySubstate.ts index 4719cc3ba5..25447d6f44 100644 --- a/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntrySubstateAllOf.ts index 839ceb5e04..36a1b06cc9 100644 --- a/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntryValue.ts b/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntryValue.ts index 17dfdf7d67..5fbc98f79e 100644 --- a/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntryValue.ts +++ b/sdk/typescript/lib/generated/models/AccountResourcePreferenceEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountVaultEntrySubstate.ts b/sdk/typescript/lib/generated/models/AccountVaultEntrySubstate.ts index 0b724502b4..852c0c7b3d 100644 --- a/sdk/typescript/lib/generated/models/AccountVaultEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/AccountVaultEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountVaultEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/AccountVaultEntrySubstateAllOf.ts index 7e6c27f434..ff1298bf48 100644 --- a/sdk/typescript/lib/generated/models/AccountVaultEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/AccountVaultEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AccountVaultEntryValue.ts b/sdk/typescript/lib/generated/models/AccountVaultEntryValue.ts index 784149e650..5c94abcfa3 100644 --- a/sdk/typescript/lib/generated/models/AccountVaultEntryValue.ts +++ b/sdk/typescript/lib/generated/models/AccountVaultEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ActiveValidator.ts b/sdk/typescript/lib/generated/models/ActiveValidator.ts index c9e63a102b..b33f7305f0 100644 --- a/sdk/typescript/lib/generated/models/ActiveValidator.ts +++ b/sdk/typescript/lib/generated/models/ActiveValidator.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ActiveValidatorIndex.ts b/sdk/typescript/lib/generated/models/ActiveValidatorIndex.ts index 2940b1c11a..e494394a22 100644 --- a/sdk/typescript/lib/generated/models/ActiveValidatorIndex.ts +++ b/sdk/typescript/lib/generated/models/ActiveValidatorIndex.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ActiveValidatorKey.ts b/sdk/typescript/lib/generated/models/ActiveValidatorKey.ts index 65c5e64405..4dc6391918 100644 --- a/sdk/typescript/lib/generated/models/ActiveValidatorKey.ts +++ b/sdk/typescript/lib/generated/models/ActiveValidatorKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AddressType.ts b/sdk/typescript/lib/generated/models/AddressType.ts index 5a274afc3f..f58aad5678 100644 --- a/sdk/typescript/lib/generated/models/AddressType.ts +++ b/sdk/typescript/lib/generated/models/AddressType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AllOfAccessRuleNode.ts b/sdk/typescript/lib/generated/models/AllOfAccessRuleNode.ts index 8331d8f5ea..af34844053 100644 --- a/sdk/typescript/lib/generated/models/AllOfAccessRuleNode.ts +++ b/sdk/typescript/lib/generated/models/AllOfAccessRuleNode.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AllOfAccessRuleNodeAllOf.ts b/sdk/typescript/lib/generated/models/AllOfAccessRuleNodeAllOf.ts index 187f1735e1..eb60d6b15d 100644 --- a/sdk/typescript/lib/generated/models/AllOfAccessRuleNodeAllOf.ts +++ b/sdk/typescript/lib/generated/models/AllOfAccessRuleNodeAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AllOfProofRule.ts b/sdk/typescript/lib/generated/models/AllOfProofRule.ts index 79a1d733f9..7a6500bc29 100644 --- a/sdk/typescript/lib/generated/models/AllOfProofRule.ts +++ b/sdk/typescript/lib/generated/models/AllOfProofRule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AllOfProofRuleAllOf.ts b/sdk/typescript/lib/generated/models/AllOfProofRuleAllOf.ts index 5fabf5d614..86e1d914c0 100644 --- a/sdk/typescript/lib/generated/models/AllOfProofRuleAllOf.ts +++ b/sdk/typescript/lib/generated/models/AllOfProofRuleAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AllowAllAccessRule.ts b/sdk/typescript/lib/generated/models/AllowAllAccessRule.ts index c1ae7d777c..4de4bca2a0 100644 --- a/sdk/typescript/lib/generated/models/AllowAllAccessRule.ts +++ b/sdk/typescript/lib/generated/models/AllowAllAccessRule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AllowAllAccessRuleAllOf.ts b/sdk/typescript/lib/generated/models/AllowAllAccessRuleAllOf.ts index 218f4b3191..e1ea285b39 100644 --- a/sdk/typescript/lib/generated/models/AllowAllAccessRuleAllOf.ts +++ b/sdk/typescript/lib/generated/models/AllowAllAccessRuleAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AmountOfProofRule.ts b/sdk/typescript/lib/generated/models/AmountOfProofRule.ts index f0b293926f..fa82cc5e2c 100644 --- a/sdk/typescript/lib/generated/models/AmountOfProofRule.ts +++ b/sdk/typescript/lib/generated/models/AmountOfProofRule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AmountOfProofRuleAllOf.ts b/sdk/typescript/lib/generated/models/AmountOfProofRuleAllOf.ts index dbf919195a..d84444e144 100644 --- a/sdk/typescript/lib/generated/models/AmountOfProofRuleAllOf.ts +++ b/sdk/typescript/lib/generated/models/AmountOfProofRuleAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AnyOfAccessRuleNode.ts b/sdk/typescript/lib/generated/models/AnyOfAccessRuleNode.ts index 9293ca3522..d181361c0d 100644 --- a/sdk/typescript/lib/generated/models/AnyOfAccessRuleNode.ts +++ b/sdk/typescript/lib/generated/models/AnyOfAccessRuleNode.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AnyOfAccessRuleNodeAllOf.ts b/sdk/typescript/lib/generated/models/AnyOfAccessRuleNodeAllOf.ts index d16d75ca4f..1189c931cb 100644 --- a/sdk/typescript/lib/generated/models/AnyOfAccessRuleNodeAllOf.ts +++ b/sdk/typescript/lib/generated/models/AnyOfAccessRuleNodeAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AnyOfProofRule.ts b/sdk/typescript/lib/generated/models/AnyOfProofRule.ts index af80a134a8..7edc8849f9 100644 --- a/sdk/typescript/lib/generated/models/AnyOfProofRule.ts +++ b/sdk/typescript/lib/generated/models/AnyOfProofRule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AnyOfProofRuleAllOf.ts b/sdk/typescript/lib/generated/models/AnyOfProofRuleAllOf.ts index 0cecb2a9f0..d849f6c092 100644 --- a/sdk/typescript/lib/generated/models/AnyOfProofRuleAllOf.ts +++ b/sdk/typescript/lib/generated/models/AnyOfProofRuleAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AttachedModuleId.ts b/sdk/typescript/lib/generated/models/AttachedModuleId.ts index 2fd95948a5..26ee6b1c1e 100644 --- a/sdk/typescript/lib/generated/models/AttachedModuleId.ts +++ b/sdk/typescript/lib/generated/models/AttachedModuleId.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AuthConfig.ts b/sdk/typescript/lib/generated/models/AuthConfig.ts index a7ec14a7d1..289126e7d9 100644 --- a/sdk/typescript/lib/generated/models/AuthConfig.ts +++ b/sdk/typescript/lib/generated/models/AuthConfig.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AuthorizedDepositorBadge.ts b/sdk/typescript/lib/generated/models/AuthorizedDepositorBadge.ts index 2b66b5182c..6df9b67bd1 100644 --- a/sdk/typescript/lib/generated/models/AuthorizedDepositorBadge.ts +++ b/sdk/typescript/lib/generated/models/AuthorizedDepositorBadge.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AuthorizedDepositorBadgeBase.ts b/sdk/typescript/lib/generated/models/AuthorizedDepositorBadgeBase.ts index 67d71a520c..db4be2b5b8 100644 --- a/sdk/typescript/lib/generated/models/AuthorizedDepositorBadgeBase.ts +++ b/sdk/typescript/lib/generated/models/AuthorizedDepositorBadgeBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AuthorizedDepositorBadgeType.ts b/sdk/typescript/lib/generated/models/AuthorizedDepositorBadgeType.ts index 3f46b79dee..a33ac82282 100644 --- a/sdk/typescript/lib/generated/models/AuthorizedDepositorBadgeType.ts +++ b/sdk/typescript/lib/generated/models/AuthorizedDepositorBadgeType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/AuthorizedDepositorKey.ts b/sdk/typescript/lib/generated/models/AuthorizedDepositorKey.ts index 0bead28b24..e9b0c12772 100644 --- a/sdk/typescript/lib/generated/models/AuthorizedDepositorKey.ts +++ b/sdk/typescript/lib/generated/models/AuthorizedDepositorKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BasicErrorResponse.ts b/sdk/typescript/lib/generated/models/BasicErrorResponse.ts index 72e0e2583a..ab45ab88ec 100644 --- a/sdk/typescript/lib/generated/models/BasicErrorResponse.ts +++ b/sdk/typescript/lib/generated/models/BasicErrorResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BasicErrorResponseAllOf.ts b/sdk/typescript/lib/generated/models/BasicErrorResponseAllOf.ts index 7cc2447236..a64201e98d 100644 --- a/sdk/typescript/lib/generated/models/BasicErrorResponseAllOf.ts +++ b/sdk/typescript/lib/generated/models/BasicErrorResponseAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BinaryPlaintextMessageContent.ts b/sdk/typescript/lib/generated/models/BinaryPlaintextMessageContent.ts index 1844fc615a..bbd847e4dc 100644 --- a/sdk/typescript/lib/generated/models/BinaryPlaintextMessageContent.ts +++ b/sdk/typescript/lib/generated/models/BinaryPlaintextMessageContent.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BinaryPlaintextMessageContentAllOf.ts b/sdk/typescript/lib/generated/models/BinaryPlaintextMessageContentAllOf.ts index e6a6a7741c..5b84e985ae 100644 --- a/sdk/typescript/lib/generated/models/BinaryPlaintextMessageContentAllOf.ts +++ b/sdk/typescript/lib/generated/models/BinaryPlaintextMessageContentAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintCollectionSchema.ts b/sdk/typescript/lib/generated/models/BlueprintCollectionSchema.ts index 61ef521ce6..a35d041b93 100644 --- a/sdk/typescript/lib/generated/models/BlueprintCollectionSchema.ts +++ b/sdk/typescript/lib/generated/models/BlueprintCollectionSchema.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintCollectionSchemaBase.ts b/sdk/typescript/lib/generated/models/BlueprintCollectionSchemaBase.ts index 730b2b0b2f..a3c4baf502 100644 --- a/sdk/typescript/lib/generated/models/BlueprintCollectionSchemaBase.ts +++ b/sdk/typescript/lib/generated/models/BlueprintCollectionSchemaBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintCollectionSchemaType.ts b/sdk/typescript/lib/generated/models/BlueprintCollectionSchemaType.ts index 5f590d035e..15e120168f 100644 --- a/sdk/typescript/lib/generated/models/BlueprintCollectionSchemaType.ts +++ b/sdk/typescript/lib/generated/models/BlueprintCollectionSchemaType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintDefinition.ts b/sdk/typescript/lib/generated/models/BlueprintDefinition.ts index d94f042488..0483df6be0 100644 --- a/sdk/typescript/lib/generated/models/BlueprintDefinition.ts +++ b/sdk/typescript/lib/generated/models/BlueprintDefinition.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintDependencies.ts b/sdk/typescript/lib/generated/models/BlueprintDependencies.ts index 45b1804a9a..fd6e4869e3 100644 --- a/sdk/typescript/lib/generated/models/BlueprintDependencies.ts +++ b/sdk/typescript/lib/generated/models/BlueprintDependencies.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintFunctionTargetIdentifier.ts b/sdk/typescript/lib/generated/models/BlueprintFunctionTargetIdentifier.ts index 3ecd948298..0a44348008 100644 --- a/sdk/typescript/lib/generated/models/BlueprintFunctionTargetIdentifier.ts +++ b/sdk/typescript/lib/generated/models/BlueprintFunctionTargetIdentifier.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintFunctionTargetIdentifierAllOf.ts b/sdk/typescript/lib/generated/models/BlueprintFunctionTargetIdentifierAllOf.ts index ed1e3c8ea5..a889ee65a2 100644 --- a/sdk/typescript/lib/generated/models/BlueprintFunctionTargetIdentifierAllOf.ts +++ b/sdk/typescript/lib/generated/models/BlueprintFunctionTargetIdentifierAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintInfo.ts b/sdk/typescript/lib/generated/models/BlueprintInfo.ts index 5a6c4bf764..8e240a777b 100644 --- a/sdk/typescript/lib/generated/models/BlueprintInfo.ts +++ b/sdk/typescript/lib/generated/models/BlueprintInfo.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintInterface.ts b/sdk/typescript/lib/generated/models/BlueprintInterface.ts index f5581f8e63..45a7e55b77 100644 --- a/sdk/typescript/lib/generated/models/BlueprintInterface.ts +++ b/sdk/typescript/lib/generated/models/BlueprintInterface.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintMethodRoyalty.ts b/sdk/typescript/lib/generated/models/BlueprintMethodRoyalty.ts index 8437130a37..57cd61826f 100644 --- a/sdk/typescript/lib/generated/models/BlueprintMethodRoyalty.ts +++ b/sdk/typescript/lib/generated/models/BlueprintMethodRoyalty.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintPayloadDef.ts b/sdk/typescript/lib/generated/models/BlueprintPayloadDef.ts index 4ca4238367..ab01157192 100644 --- a/sdk/typescript/lib/generated/models/BlueprintPayloadDef.ts +++ b/sdk/typescript/lib/generated/models/BlueprintPayloadDef.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintPayloadDefBase.ts b/sdk/typescript/lib/generated/models/BlueprintPayloadDefBase.ts index 8977123c84..288eccf2be 100644 --- a/sdk/typescript/lib/generated/models/BlueprintPayloadDefBase.ts +++ b/sdk/typescript/lib/generated/models/BlueprintPayloadDefBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintPayloadDefType.ts b/sdk/typescript/lib/generated/models/BlueprintPayloadDefType.ts index c101f553b6..fcef4642ea 100644 --- a/sdk/typescript/lib/generated/models/BlueprintPayloadDefType.ts +++ b/sdk/typescript/lib/generated/models/BlueprintPayloadDefType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintRoyaltyConfig.ts b/sdk/typescript/lib/generated/models/BlueprintRoyaltyConfig.ts index 305996e394..633bf88aee 100644 --- a/sdk/typescript/lib/generated/models/BlueprintRoyaltyConfig.ts +++ b/sdk/typescript/lib/generated/models/BlueprintRoyaltyConfig.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintSchemaBlueprintTypeReference.ts b/sdk/typescript/lib/generated/models/BlueprintSchemaBlueprintTypeReference.ts index 291e8ce35e..0dec9d8cf6 100644 --- a/sdk/typescript/lib/generated/models/BlueprintSchemaBlueprintTypeReference.ts +++ b/sdk/typescript/lib/generated/models/BlueprintSchemaBlueprintTypeReference.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintSchemaBlueprintTypeReferenceAllOf.ts b/sdk/typescript/lib/generated/models/BlueprintSchemaBlueprintTypeReferenceAllOf.ts index d752509976..eba16278be 100644 --- a/sdk/typescript/lib/generated/models/BlueprintSchemaBlueprintTypeReferenceAllOf.ts +++ b/sdk/typescript/lib/generated/models/BlueprintSchemaBlueprintTypeReferenceAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintSchemaCollectionPartition.ts b/sdk/typescript/lib/generated/models/BlueprintSchemaCollectionPartition.ts index 9c5f47fa39..e4d225a0fe 100644 --- a/sdk/typescript/lib/generated/models/BlueprintSchemaCollectionPartition.ts +++ b/sdk/typescript/lib/generated/models/BlueprintSchemaCollectionPartition.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintSchemaFieldPartition.ts b/sdk/typescript/lib/generated/models/BlueprintSchemaFieldPartition.ts index 26136adfed..4642f56ea1 100644 --- a/sdk/typescript/lib/generated/models/BlueprintSchemaFieldPartition.ts +++ b/sdk/typescript/lib/generated/models/BlueprintSchemaFieldPartition.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintTypeIdentifier.ts b/sdk/typescript/lib/generated/models/BlueprintTypeIdentifier.ts index 9202a3d039..d37ccda190 100644 --- a/sdk/typescript/lib/generated/models/BlueprintTypeIdentifier.ts +++ b/sdk/typescript/lib/generated/models/BlueprintTypeIdentifier.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintTypeReference.ts b/sdk/typescript/lib/generated/models/BlueprintTypeReference.ts index d1fa836a99..4a200dce95 100644 --- a/sdk/typescript/lib/generated/models/BlueprintTypeReference.ts +++ b/sdk/typescript/lib/generated/models/BlueprintTypeReference.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintTypeReferenceBase.ts b/sdk/typescript/lib/generated/models/BlueprintTypeReferenceBase.ts index 2ddb1f1ef5..24c8d1586f 100644 --- a/sdk/typescript/lib/generated/models/BlueprintTypeReferenceBase.ts +++ b/sdk/typescript/lib/generated/models/BlueprintTypeReferenceBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintTypeReferenceKind.ts b/sdk/typescript/lib/generated/models/BlueprintTypeReferenceKind.ts index effe274829..da5977fc2b 100644 --- a/sdk/typescript/lib/generated/models/BlueprintTypeReferenceKind.ts +++ b/sdk/typescript/lib/generated/models/BlueprintTypeReferenceKind.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BlueprintVersionKey.ts b/sdk/typescript/lib/generated/models/BlueprintVersionKey.ts index f2afc733c6..c1250931b7 100644 --- a/sdk/typescript/lib/generated/models/BlueprintVersionKey.ts +++ b/sdk/typescript/lib/generated/models/BlueprintVersionKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldKernelBootSubstate.ts b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldKernelBootSubstate.ts index 6623882988..88d9840111 100644 --- a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldKernelBootSubstate.ts +++ b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldKernelBootSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldKernelBootSubstateAllOf.ts b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldKernelBootSubstateAllOf.ts index 0d9e8aae42..5294096424 100644 --- a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldKernelBootSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldKernelBootSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootSubstate.ts b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootSubstate.ts index 547a0d1dab..2ee10bcea2 100644 --- a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootSubstate.ts +++ b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootSubstateAllOf.ts b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootSubstateAllOf.ts index 71bd6750f4..217b87fa48 100644 --- a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootValue.ts b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootValue.ts index f4a13d11c2..9105bbf58e 100644 --- a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootValue.ts +++ b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldSystemBootValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootSubstate.ts b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootSubstate.ts index adbd855fcc..995ddd02c4 100644 --- a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootSubstate.ts +++ b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootSubstateAllOf.ts b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootSubstateAllOf.ts index 2b36621d91..b38ee70dc6 100644 --- a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootValue.ts b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootValue.ts index dcb5896cfc..9fd0268111 100644 --- a/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootValue.ts +++ b/sdk/typescript/lib/generated/models/BootLoaderModuleFieldVmBootValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/CommittedIntentMetadata.ts b/sdk/typescript/lib/generated/models/CommittedIntentMetadata.ts index d821c78fb7..d92c64216c 100644 --- a/sdk/typescript/lib/generated/models/CommittedIntentMetadata.ts +++ b/sdk/typescript/lib/generated/models/CommittedIntentMetadata.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/CommittedStateIdentifier.ts b/sdk/typescript/lib/generated/models/CommittedStateIdentifier.ts index f72a40150b..fd3b8096eb 100644 --- a/sdk/typescript/lib/generated/models/CommittedStateIdentifier.ts +++ b/sdk/typescript/lib/generated/models/CommittedStateIdentifier.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/CommittedStateIdentifierAllOf.ts b/sdk/typescript/lib/generated/models/CommittedStateIdentifierAllOf.ts index 9629dc9fbc..1c3efb92e8 100644 --- a/sdk/typescript/lib/generated/models/CommittedStateIdentifierAllOf.ts +++ b/sdk/typescript/lib/generated/models/CommittedStateIdentifierAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/CommittedTransaction.ts b/sdk/typescript/lib/generated/models/CommittedTransaction.ts index 40546c1e42..6480bf0ade 100644 --- a/sdk/typescript/lib/generated/models/CommittedTransaction.ts +++ b/sdk/typescript/lib/generated/models/CommittedTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/CommittedTransactionBalanceChanges.ts b/sdk/typescript/lib/generated/models/CommittedTransactionBalanceChanges.ts index d30ab1ded0..9602751559 100644 --- a/sdk/typescript/lib/generated/models/CommittedTransactionBalanceChanges.ts +++ b/sdk/typescript/lib/generated/models/CommittedTransactionBalanceChanges.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ComponentMethodTargetIdentifier.ts b/sdk/typescript/lib/generated/models/ComponentMethodTargetIdentifier.ts index ffd82aa947..df42c2d2c6 100644 --- a/sdk/typescript/lib/generated/models/ComponentMethodTargetIdentifier.ts +++ b/sdk/typescript/lib/generated/models/ComponentMethodTargetIdentifier.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ComponentMethodTargetIdentifierAllOf.ts b/sdk/typescript/lib/generated/models/ComponentMethodTargetIdentifierAllOf.ts index 1396834032..d8af7e9bb7 100644 --- a/sdk/typescript/lib/generated/models/ComponentMethodTargetIdentifierAllOf.ts +++ b/sdk/typescript/lib/generated/models/ComponentMethodTargetIdentifierAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusLedgerProofOrigin.ts b/sdk/typescript/lib/generated/models/ConsensusLedgerProofOrigin.ts index f9bd0a4625..42963fa508 100644 --- a/sdk/typescript/lib/generated/models/ConsensusLedgerProofOrigin.ts +++ b/sdk/typescript/lib/generated/models/ConsensusLedgerProofOrigin.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusLedgerProofOriginAllOf.ts b/sdk/typescript/lib/generated/models/ConsensusLedgerProofOriginAllOf.ts index 670ac46096..76487da879 100644 --- a/sdk/typescript/lib/generated/models/ConsensusLedgerProofOriginAllOf.ts +++ b/sdk/typescript/lib/generated/models/ConsensusLedgerProofOriginAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigSubstate.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigSubstate.ts index 40df2d966a..dc4e74cb93 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigSubstate.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigSubstateAllOf.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigSubstateAllOf.ts index 5d996734c4..c2aee1655c 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigValue.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigValue.ts index 7d62403696..02f7658879 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigValue.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldConfigValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstate.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstate.ts index ccf8f8d510..d52ea3ed23 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstate.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstateAllOf.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstateAllOf.ts index f3f44774e7..246b618eec 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticValue.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticValue.ts index 05b44a82fd..1eddef9833 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticValue.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentProposalStatisticValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstate.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstate.ts index 4913da8f87..20f0aa24e6 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstate.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstateAllOf.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstateAllOf.ts index e5366cce4d..8ffcb9e0cd 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesValue.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesValue.ts index 5a1f91b6f8..7df3b206cb 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesValue.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeRoundedToMinutesValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeSubstate.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeSubstate.ts index 8b2866d213..bcdefc8d08 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeSubstate.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeSubstateAllOf.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeSubstateAllOf.ts index 8436426f93..295fd12a32 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeValue.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeValue.ts index b477591ec8..b401e7df08 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeValue.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentTimeValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstate.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstate.ts index e2c1e215f8..c6afea750e 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstate.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstateAllOf.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstateAllOf.ts index 31d95c902b..83fe55b8e1 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetValue.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetValue.ts index 085ac57152..54244f866c 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetValue.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldCurrentValidatorSetValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateSubstate.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateSubstate.ts index 4703fa250d..e06e73b6c1 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateSubstate.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateSubstateAllOf.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateSubstateAllOf.ts index ef78452f1f..77073855db 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateValue.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateValue.ts index bc2d2c0a31..186dc77b62 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateValue.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldStateValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsSubstate.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsSubstate.ts index c80ab33e7f..1f9e3d7f4a 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsSubstate.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsSubstateAllOf.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsSubstateAllOf.ts index 9a744777ec..efdc3aa69d 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsValue.ts b/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsValue.ts index e60e8c8eb3..b12e509500 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsValue.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerFieldValidatorRewardsValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstate.ts b/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstate.ts index 6b43bc65ff..cda2437a25 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstateAllOf.ts index 97f6a02c01..8c36032563 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.ts b/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.ts index 15f2790521..7497191cc1 100644 --- a/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.ts +++ b/sdk/typescript/lib/generated/models/ConsensusManagerRegisteredValidatorsByStakeIndexEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/CostingModuleConfig.ts b/sdk/typescript/lib/generated/models/CostingModuleConfig.ts index 4b0159befc..e91291a6c5 100644 --- a/sdk/typescript/lib/generated/models/CostingModuleConfig.ts +++ b/sdk/typescript/lib/generated/models/CostingModuleConfig.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/CostingParameters.ts b/sdk/typescript/lib/generated/models/CostingParameters.ts index d38016300e..c9c83f4442 100644 --- a/sdk/typescript/lib/generated/models/CostingParameters.ts +++ b/sdk/typescript/lib/generated/models/CostingParameters.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/CountOfProofRule.ts b/sdk/typescript/lib/generated/models/CountOfProofRule.ts index 0614bd3228..76ccc9e90b 100644 --- a/sdk/typescript/lib/generated/models/CountOfProofRule.ts +++ b/sdk/typescript/lib/generated/models/CountOfProofRule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/CountOfProofRuleAllOf.ts b/sdk/typescript/lib/generated/models/CountOfProofRuleAllOf.ts index 6062d63342..a0d4424619 100644 --- a/sdk/typescript/lib/generated/models/CountOfProofRuleAllOf.ts +++ b/sdk/typescript/lib/generated/models/CountOfProofRuleAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/CreatedSubstate.ts b/sdk/typescript/lib/generated/models/CreatedSubstate.ts index 00d4928010..974ba07941 100644 --- a/sdk/typescript/lib/generated/models/CreatedSubstate.ts +++ b/sdk/typescript/lib/generated/models/CreatedSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/DataStruct.ts b/sdk/typescript/lib/generated/models/DataStruct.ts index 24bb430c38..23940c8977 100644 --- a/sdk/typescript/lib/generated/models/DataStruct.ts +++ b/sdk/typescript/lib/generated/models/DataStruct.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/DefaultDepositRule.ts b/sdk/typescript/lib/generated/models/DefaultDepositRule.ts index c5035cb20b..45453b85bd 100644 --- a/sdk/typescript/lib/generated/models/DefaultDepositRule.ts +++ b/sdk/typescript/lib/generated/models/DefaultDepositRule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/DeletedSubstate.ts b/sdk/typescript/lib/generated/models/DeletedSubstate.ts index c6a00e3fa2..f11e33e86d 100644 --- a/sdk/typescript/lib/generated/models/DeletedSubstate.ts +++ b/sdk/typescript/lib/generated/models/DeletedSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/DenyAllAccessRule.ts b/sdk/typescript/lib/generated/models/DenyAllAccessRule.ts index f78282b2a2..3e9dc233e7 100644 --- a/sdk/typescript/lib/generated/models/DenyAllAccessRule.ts +++ b/sdk/typescript/lib/generated/models/DenyAllAccessRule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/DenyAllAccessRuleAllOf.ts b/sdk/typescript/lib/generated/models/DenyAllAccessRuleAllOf.ts index 0942ab1f94..a91dc57788 100644 --- a/sdk/typescript/lib/generated/models/DenyAllAccessRuleAllOf.ts +++ b/sdk/typescript/lib/generated/models/DenyAllAccessRuleAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EcdsaSecp256k1PublicKey.ts b/sdk/typescript/lib/generated/models/EcdsaSecp256k1PublicKey.ts index b72825a344..c6bb4c05ae 100644 --- a/sdk/typescript/lib/generated/models/EcdsaSecp256k1PublicKey.ts +++ b/sdk/typescript/lib/generated/models/EcdsaSecp256k1PublicKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EcdsaSecp256k1PublicKeyAllOf.ts b/sdk/typescript/lib/generated/models/EcdsaSecp256k1PublicKeyAllOf.ts index 2593bef378..293c381a0a 100644 --- a/sdk/typescript/lib/generated/models/EcdsaSecp256k1PublicKeyAllOf.ts +++ b/sdk/typescript/lib/generated/models/EcdsaSecp256k1PublicKeyAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EcdsaSecp256k1Signature.ts b/sdk/typescript/lib/generated/models/EcdsaSecp256k1Signature.ts index f8edb8e578..f7f3f0994d 100644 --- a/sdk/typescript/lib/generated/models/EcdsaSecp256k1Signature.ts +++ b/sdk/typescript/lib/generated/models/EcdsaSecp256k1Signature.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureAllOf.ts b/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureAllOf.ts index 06e3513f82..eab2a4abcc 100644 --- a/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureAllOf.ts +++ b/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureWithPublicKey.ts b/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureWithPublicKey.ts index 183648ef8b..04e7141a36 100644 --- a/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureWithPublicKey.ts +++ b/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureWithPublicKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureWithPublicKeyAllOf.ts b/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureWithPublicKeyAllOf.ts index 30e5629938..cc7f1350f7 100644 --- a/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureWithPublicKeyAllOf.ts +++ b/sdk/typescript/lib/generated/models/EcdsaSecp256k1SignatureWithPublicKeyAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EddsaEd25519PublicKey.ts b/sdk/typescript/lib/generated/models/EddsaEd25519PublicKey.ts index 14da67be31..87bf24c844 100644 --- a/sdk/typescript/lib/generated/models/EddsaEd25519PublicKey.ts +++ b/sdk/typescript/lib/generated/models/EddsaEd25519PublicKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EddsaEd25519PublicKeyAllOf.ts b/sdk/typescript/lib/generated/models/EddsaEd25519PublicKeyAllOf.ts index e83c563712..96d40e22da 100644 --- a/sdk/typescript/lib/generated/models/EddsaEd25519PublicKeyAllOf.ts +++ b/sdk/typescript/lib/generated/models/EddsaEd25519PublicKeyAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EddsaEd25519Signature.ts b/sdk/typescript/lib/generated/models/EddsaEd25519Signature.ts index 98c546914a..684e0b30c4 100644 --- a/sdk/typescript/lib/generated/models/EddsaEd25519Signature.ts +++ b/sdk/typescript/lib/generated/models/EddsaEd25519Signature.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EddsaEd25519SignatureAllOf.ts b/sdk/typescript/lib/generated/models/EddsaEd25519SignatureAllOf.ts index 04d960eb5d..8b2e7286bc 100644 --- a/sdk/typescript/lib/generated/models/EddsaEd25519SignatureAllOf.ts +++ b/sdk/typescript/lib/generated/models/EddsaEd25519SignatureAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EddsaEd25519SignatureWithPublicKey.ts b/sdk/typescript/lib/generated/models/EddsaEd25519SignatureWithPublicKey.ts index eb50297e7a..1d0c7f7893 100644 --- a/sdk/typescript/lib/generated/models/EddsaEd25519SignatureWithPublicKey.ts +++ b/sdk/typescript/lib/generated/models/EddsaEd25519SignatureWithPublicKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EddsaEd25519SignatureWithPublicKeyAllOf.ts b/sdk/typescript/lib/generated/models/EddsaEd25519SignatureWithPublicKeyAllOf.ts index fdc22bf70a..8abb8d9ea7 100644 --- a/sdk/typescript/lib/generated/models/EddsaEd25519SignatureWithPublicKeyAllOf.ts +++ b/sdk/typescript/lib/generated/models/EddsaEd25519SignatureWithPublicKeyAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EncryptedMessageCurveDecryptorSet.ts b/sdk/typescript/lib/generated/models/EncryptedMessageCurveDecryptorSet.ts index 1741f5a928..32eda46dc2 100644 --- a/sdk/typescript/lib/generated/models/EncryptedMessageCurveDecryptorSet.ts +++ b/sdk/typescript/lib/generated/models/EncryptedMessageCurveDecryptorSet.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EncryptedMessageDecryptor.ts b/sdk/typescript/lib/generated/models/EncryptedMessageDecryptor.ts index 5b38300bac..933ee9ba85 100644 --- a/sdk/typescript/lib/generated/models/EncryptedMessageDecryptor.ts +++ b/sdk/typescript/lib/generated/models/EncryptedMessageDecryptor.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EncryptedTransactionMessage.ts b/sdk/typescript/lib/generated/models/EncryptedTransactionMessage.ts index a9dee6f3bc..a29927b549 100644 --- a/sdk/typescript/lib/generated/models/EncryptedTransactionMessage.ts +++ b/sdk/typescript/lib/generated/models/EncryptedTransactionMessage.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EncryptedTransactionMessageAllOf.ts b/sdk/typescript/lib/generated/models/EncryptedTransactionMessageAllOf.ts index 495e56758d..f1b41e9ebe 100644 --- a/sdk/typescript/lib/generated/models/EncryptedTransactionMessageAllOf.ts +++ b/sdk/typescript/lib/generated/models/EncryptedTransactionMessageAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EntityModule.ts b/sdk/typescript/lib/generated/models/EntityModule.ts index 3aa04b7cbc..a59dbaddf3 100644 --- a/sdk/typescript/lib/generated/models/EntityModule.ts +++ b/sdk/typescript/lib/generated/models/EntityModule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EntityReference.ts b/sdk/typescript/lib/generated/models/EntityReference.ts index d94caf6891..f5e272878d 100644 --- a/sdk/typescript/lib/generated/models/EntityReference.ts +++ b/sdk/typescript/lib/generated/models/EntityReference.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EntityType.ts b/sdk/typescript/lib/generated/models/EntityType.ts index feb3b0ebc3..fe3dbd0278 100644 --- a/sdk/typescript/lib/generated/models/EntityType.ts +++ b/sdk/typescript/lib/generated/models/EntityType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EpochChangeCondition.ts b/sdk/typescript/lib/generated/models/EpochChangeCondition.ts index 2befa81ecd..24ec13aad0 100644 --- a/sdk/typescript/lib/generated/models/EpochChangeCondition.ts +++ b/sdk/typescript/lib/generated/models/EpochChangeCondition.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EpochEndLedgerProof.ts b/sdk/typescript/lib/generated/models/EpochEndLedgerProof.ts index 626257f7f7..af8894f1e3 100644 --- a/sdk/typescript/lib/generated/models/EpochEndLedgerProof.ts +++ b/sdk/typescript/lib/generated/models/EpochEndLedgerProof.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EpochRound.ts b/sdk/typescript/lib/generated/models/EpochRound.ts index d2d8299f5d..642564d611 100644 --- a/sdk/typescript/lib/generated/models/EpochRound.ts +++ b/sdk/typescript/lib/generated/models/EpochRound.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ErrorResponse.ts b/sdk/typescript/lib/generated/models/ErrorResponse.ts index 22dea77ac4..c768f9ea97 100644 --- a/sdk/typescript/lib/generated/models/ErrorResponse.ts +++ b/sdk/typescript/lib/generated/models/ErrorResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ErrorResponseBase.ts b/sdk/typescript/lib/generated/models/ErrorResponseBase.ts index da22f4a468..494bab2e19 100644 --- a/sdk/typescript/lib/generated/models/ErrorResponseBase.ts +++ b/sdk/typescript/lib/generated/models/ErrorResponseBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ErrorResponseType.ts b/sdk/typescript/lib/generated/models/ErrorResponseType.ts index 40624f4b1b..919291c85b 100644 --- a/sdk/typescript/lib/generated/models/ErrorResponseType.ts +++ b/sdk/typescript/lib/generated/models/ErrorResponseType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/Event.ts b/sdk/typescript/lib/generated/models/Event.ts index 2123e7e4be..fbf4ea1177 100644 --- a/sdk/typescript/lib/generated/models/Event.ts +++ b/sdk/typescript/lib/generated/models/Event.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EventEmitterIdentifier.ts b/sdk/typescript/lib/generated/models/EventEmitterIdentifier.ts index 89f41945e7..a6364e46aa 100644 --- a/sdk/typescript/lib/generated/models/EventEmitterIdentifier.ts +++ b/sdk/typescript/lib/generated/models/EventEmitterIdentifier.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EventEmitterIdentifierBase.ts b/sdk/typescript/lib/generated/models/EventEmitterIdentifierBase.ts index d7ed49de60..85c4c518f7 100644 --- a/sdk/typescript/lib/generated/models/EventEmitterIdentifierBase.ts +++ b/sdk/typescript/lib/generated/models/EventEmitterIdentifierBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EventEmitterIdentifierType.ts b/sdk/typescript/lib/generated/models/EventEmitterIdentifierType.ts index 361b18a84e..7e663886bf 100644 --- a/sdk/typescript/lib/generated/models/EventEmitterIdentifierType.ts +++ b/sdk/typescript/lib/generated/models/EventEmitterIdentifierType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/EventTypeIdentifier.ts b/sdk/typescript/lib/generated/models/EventTypeIdentifier.ts index 41bcb9e907..2b43d3518b 100644 --- a/sdk/typescript/lib/generated/models/EventTypeIdentifier.ts +++ b/sdk/typescript/lib/generated/models/EventTypeIdentifier.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ExecutedScenario.ts b/sdk/typescript/lib/generated/models/ExecutedScenario.ts index 779a062b27..2541021b82 100644 --- a/sdk/typescript/lib/generated/models/ExecutedScenario.ts +++ b/sdk/typescript/lib/generated/models/ExecutedScenario.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ExecutedScenarioTransaction.ts b/sdk/typescript/lib/generated/models/ExecutedScenarioTransaction.ts index 24c9a92347..798426cd16 100644 --- a/sdk/typescript/lib/generated/models/ExecutedScenarioTransaction.ts +++ b/sdk/typescript/lib/generated/models/ExecutedScenarioTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FeeDestination.ts b/sdk/typescript/lib/generated/models/FeeDestination.ts index b8d1ed53fd..90b7c01e37 100644 --- a/sdk/typescript/lib/generated/models/FeeDestination.ts +++ b/sdk/typescript/lib/generated/models/FeeDestination.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FeeSource.ts b/sdk/typescript/lib/generated/models/FeeSource.ts index 1b74b2bfcc..3b853cf0f8 100644 --- a/sdk/typescript/lib/generated/models/FeeSource.ts +++ b/sdk/typescript/lib/generated/models/FeeSource.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FeeSummary.ts b/sdk/typescript/lib/generated/models/FeeSummary.ts index e5c5110ce9..748bf648d8 100644 --- a/sdk/typescript/lib/generated/models/FeeSummary.ts +++ b/sdk/typescript/lib/generated/models/FeeSummary.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSchema.ts b/sdk/typescript/lib/generated/models/FieldSchema.ts index cf94793eba..18fe05c32f 100644 --- a/sdk/typescript/lib/generated/models/FieldSchema.ts +++ b/sdk/typescript/lib/generated/models/FieldSchema.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSchemaFeatureCondition.ts b/sdk/typescript/lib/generated/models/FieldSchemaFeatureCondition.ts index d30d60e943..0b11c0dbbc 100644 --- a/sdk/typescript/lib/generated/models/FieldSchemaFeatureCondition.ts +++ b/sdk/typescript/lib/generated/models/FieldSchemaFeatureCondition.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionAlways.ts b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionAlways.ts index 8ea9a6b297..2a5deab933 100644 --- a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionAlways.ts +++ b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionAlways.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionAlwaysAllOf.ts b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionAlwaysAllOf.ts index 95a7f9aa0a..079aec9b22 100644 --- a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionAlwaysAllOf.ts +++ b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionAlwaysAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionBase.ts b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionBase.ts index 7e20881304..746c7a1fae 100644 --- a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionBase.ts +++ b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeature.ts b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeature.ts index 7d4b6153fe..5cf5d42cb4 100644 --- a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeature.ts +++ b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeature.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeatureAllOf.ts b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeatureAllOf.ts index 120567bff6..cb5dc25b01 100644 --- a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeatureAllOf.ts +++ b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOuterObjectFeatureAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOwnFeature.ts b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOwnFeature.ts index dac4ebdaf3..790a3b1ceb 100644 --- a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOwnFeature.ts +++ b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOwnFeature.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOwnFeatureAllOf.ts b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOwnFeatureAllOf.ts index 67b7e8a80b..5173f9d3bc 100644 --- a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOwnFeatureAllOf.ts +++ b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionIfOwnFeatureAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionType.ts b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionType.ts index 705c1acd15..2aafb46ec2 100644 --- a/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionType.ts +++ b/sdk/typescript/lib/generated/models/FieldSchemaFeatureConditionType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSubstateKey.ts b/sdk/typescript/lib/generated/models/FieldSubstateKey.ts index e0e47daa4c..7fdf74fdfb 100644 --- a/sdk/typescript/lib/generated/models/FieldSubstateKey.ts +++ b/sdk/typescript/lib/generated/models/FieldSubstateKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FieldSubstateKeyAllOf.ts b/sdk/typescript/lib/generated/models/FieldSubstateKeyAllOf.ts index 97253999f8..4fa624dff2 100644 --- a/sdk/typescript/lib/generated/models/FieldSubstateKeyAllOf.ts +++ b/sdk/typescript/lib/generated/models/FieldSubstateKeyAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FlashLedgerTransaction.ts b/sdk/typescript/lib/generated/models/FlashLedgerTransaction.ts index cbfa205fb5..8b41fe8613 100644 --- a/sdk/typescript/lib/generated/models/FlashLedgerTransaction.ts +++ b/sdk/typescript/lib/generated/models/FlashLedgerTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FlashLedgerTransactionAllOf.ts b/sdk/typescript/lib/generated/models/FlashLedgerTransactionAllOf.ts index 175f98e262..55312d3b27 100644 --- a/sdk/typescript/lib/generated/models/FlashLedgerTransactionAllOf.ts +++ b/sdk/typescript/lib/generated/models/FlashLedgerTransactionAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FlashSetSubstate.ts b/sdk/typescript/lib/generated/models/FlashSetSubstate.ts index 458efa16b9..6ec2521931 100644 --- a/sdk/typescript/lib/generated/models/FlashSetSubstate.ts +++ b/sdk/typescript/lib/generated/models/FlashSetSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FlashedStateUpdates.ts b/sdk/typescript/lib/generated/models/FlashedStateUpdates.ts index 6a6cccb760..2efee3ec3b 100644 --- a/sdk/typescript/lib/generated/models/FlashedStateUpdates.ts +++ b/sdk/typescript/lib/generated/models/FlashedStateUpdates.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FrozenStatus.ts b/sdk/typescript/lib/generated/models/FrozenStatus.ts index edcaeafda7..ba3ec0aba1 100644 --- a/sdk/typescript/lib/generated/models/FrozenStatus.ts +++ b/sdk/typescript/lib/generated/models/FrozenStatus.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FullyScopedTypeId.ts b/sdk/typescript/lib/generated/models/FullyScopedTypeId.ts index 82b4358f45..e06065c848 100644 --- a/sdk/typescript/lib/generated/models/FullyScopedTypeId.ts +++ b/sdk/typescript/lib/generated/models/FullyScopedTypeId.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FunctionAuthType.ts b/sdk/typescript/lib/generated/models/FunctionAuthType.ts index 068df0ba3a..e5a53f137b 100644 --- a/sdk/typescript/lib/generated/models/FunctionAuthType.ts +++ b/sdk/typescript/lib/generated/models/FunctionAuthType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FunctionEventEmitterIdentifier.ts b/sdk/typescript/lib/generated/models/FunctionEventEmitterIdentifier.ts index 4948d4910f..ecf19f214e 100644 --- a/sdk/typescript/lib/generated/models/FunctionEventEmitterIdentifier.ts +++ b/sdk/typescript/lib/generated/models/FunctionEventEmitterIdentifier.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FunctionEventEmitterIdentifierAllOf.ts b/sdk/typescript/lib/generated/models/FunctionEventEmitterIdentifierAllOf.ts index 9befd0f895..921cf2eabb 100644 --- a/sdk/typescript/lib/generated/models/FunctionEventEmitterIdentifierAllOf.ts +++ b/sdk/typescript/lib/generated/models/FunctionEventEmitterIdentifierAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FunctionSchema.ts b/sdk/typescript/lib/generated/models/FunctionSchema.ts index 368daf2c86..507daaf4bc 100644 --- a/sdk/typescript/lib/generated/models/FunctionSchema.ts +++ b/sdk/typescript/lib/generated/models/FunctionSchema.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleResourceAmount.ts b/sdk/typescript/lib/generated/models/FungibleResourceAmount.ts index 064948584a..4ff4cf3940 100644 --- a/sdk/typescript/lib/generated/models/FungibleResourceAmount.ts +++ b/sdk/typescript/lib/generated/models/FungibleResourceAmount.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleResourceAmountAllOf.ts b/sdk/typescript/lib/generated/models/FungibleResourceAmountAllOf.ts index aabc5a3412..8b553dbbc9 100644 --- a/sdk/typescript/lib/generated/models/FungibleResourceAmountAllOf.ts +++ b/sdk/typescript/lib/generated/models/FungibleResourceAmountAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilitySubstate.ts b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilitySubstate.ts index 2789cc1603..5f5614b899 100644 --- a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilitySubstate.ts +++ b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilitySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilitySubstateAllOf.ts b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilitySubstateAllOf.ts index 4f73b85726..b65e168c5b 100644 --- a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilitySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilitySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilityValue.ts b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilityValue.ts index ae08cb5cfc..94df8b7018 100644 --- a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilityValue.ts +++ b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldDivisibilityValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplySubstate.ts b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplySubstate.ts index dc38b6d33e..3b3d4a296d 100644 --- a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplySubstate.ts +++ b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplySubstateAllOf.ts b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplySubstateAllOf.ts index eceeab9d4f..a83253f472 100644 --- a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplyValue.ts b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplyValue.ts index d8ccd259ca..267a4cf0ae 100644 --- a/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplyValue.ts +++ b/sdk/typescript/lib/generated/models/FungibleResourceManagerFieldTotalSupplyValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceSubstate.ts b/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceSubstate.ts index 7d6e633454..93ae4c9b21 100644 --- a/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceSubstate.ts +++ b/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceSubstateAllOf.ts b/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceSubstateAllOf.ts index 405ef859d8..deb04dd14a 100644 --- a/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceValue.ts b/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceValue.ts index 0190823bb9..a6df9a2056 100644 --- a/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceValue.ts +++ b/sdk/typescript/lib/generated/models/FungibleVaultFieldBalanceValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusSubstate.ts b/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusSubstate.ts index 15bced860f..0efb259c74 100644 --- a/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusSubstate.ts +++ b/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusSubstateAllOf.ts b/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusSubstateAllOf.ts index 178ccbf8e2..8654004721 100644 --- a/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusValue.ts b/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusValue.ts index 5bb77cc735..0da3813fb4 100644 --- a/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusValue.ts +++ b/sdk/typescript/lib/generated/models/FungibleVaultFieldFrozenStatusValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericBlueprintPayloadDef.ts b/sdk/typescript/lib/generated/models/GenericBlueprintPayloadDef.ts index 17b0bce522..3c17d546c2 100644 --- a/sdk/typescript/lib/generated/models/GenericBlueprintPayloadDef.ts +++ b/sdk/typescript/lib/generated/models/GenericBlueprintPayloadDef.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericBlueprintPayloadDefAllOf.ts b/sdk/typescript/lib/generated/models/GenericBlueprintPayloadDefAllOf.ts index 3e8da0424f..551611b171 100644 --- a/sdk/typescript/lib/generated/models/GenericBlueprintPayloadDefAllOf.ts +++ b/sdk/typescript/lib/generated/models/GenericBlueprintPayloadDefAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericKey.ts b/sdk/typescript/lib/generated/models/GenericKey.ts index 98df23039e..6d2b315bbd 100644 --- a/sdk/typescript/lib/generated/models/GenericKey.ts +++ b/sdk/typescript/lib/generated/models/GenericKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntrySubstate.ts b/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntrySubstate.ts index c3078fba4f..ffcba7f1dc 100644 --- a/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntrySubstateAllOf.ts index 4be989f3c3..9e11ee93bd 100644 --- a/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntryValue.ts b/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntryValue.ts index fcaba85a0c..83a699cf76 100644 --- a/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntryValue.ts +++ b/sdk/typescript/lib/generated/models/GenericKeyValueStoreEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateSubstate.ts b/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateSubstate.ts index 00d2bd13c5..36f47b0c6e 100644 --- a/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateSubstate.ts +++ b/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateSubstateAllOf.ts b/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateSubstateAllOf.ts index 50b53c3974..9abac438d8 100644 --- a/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateValue.ts b/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateValue.ts index 4e949f7159..0bf13106e4 100644 --- a/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateValue.ts +++ b/sdk/typescript/lib/generated/models/GenericScryptoComponentFieldStateValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericSubstitution.ts b/sdk/typescript/lib/generated/models/GenericSubstitution.ts index 5d349a8a3f..caa06beb0b 100644 --- a/sdk/typescript/lib/generated/models/GenericSubstitution.ts +++ b/sdk/typescript/lib/generated/models/GenericSubstitution.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericSubstitutionBase.ts b/sdk/typescript/lib/generated/models/GenericSubstitutionBase.ts index 2e7fcd0928..86eb5e9bcf 100644 --- a/sdk/typescript/lib/generated/models/GenericSubstitutionBase.ts +++ b/sdk/typescript/lib/generated/models/GenericSubstitutionBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericSubstitutionType.ts b/sdk/typescript/lib/generated/models/GenericSubstitutionType.ts index 9e096b6bf7..1f06b5fec7 100644 --- a/sdk/typescript/lib/generated/models/GenericSubstitutionType.ts +++ b/sdk/typescript/lib/generated/models/GenericSubstitutionType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericTypeParameter.ts b/sdk/typescript/lib/generated/models/GenericTypeParameter.ts index 6ee078765a..dda8124d25 100644 --- a/sdk/typescript/lib/generated/models/GenericTypeParameter.ts +++ b/sdk/typescript/lib/generated/models/GenericTypeParameter.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenericTypeParameterConstraints.ts b/sdk/typescript/lib/generated/models/GenericTypeParameterConstraints.ts index 6c4c8ec6ed..216ce9c3ce 100644 --- a/sdk/typescript/lib/generated/models/GenericTypeParameterConstraints.ts +++ b/sdk/typescript/lib/generated/models/GenericTypeParameterConstraints.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenesisLedgerProofOrigin.ts b/sdk/typescript/lib/generated/models/GenesisLedgerProofOrigin.ts index a3a8b810e2..9c926aceef 100644 --- a/sdk/typescript/lib/generated/models/GenesisLedgerProofOrigin.ts +++ b/sdk/typescript/lib/generated/models/GenesisLedgerProofOrigin.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenesisLedgerProofOriginAllOf.ts b/sdk/typescript/lib/generated/models/GenesisLedgerProofOriginAllOf.ts index 57cb1a5bce..13a1d839af 100644 --- a/sdk/typescript/lib/generated/models/GenesisLedgerProofOriginAllOf.ts +++ b/sdk/typescript/lib/generated/models/GenesisLedgerProofOriginAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenesisLedgerTransaction.ts b/sdk/typescript/lib/generated/models/GenesisLedgerTransaction.ts index 4faea959dc..b0f5306acf 100644 --- a/sdk/typescript/lib/generated/models/GenesisLedgerTransaction.ts +++ b/sdk/typescript/lib/generated/models/GenesisLedgerTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/GenesisLedgerTransactionAllOf.ts b/sdk/typescript/lib/generated/models/GenesisLedgerTransactionAllOf.ts index dfc25aa11c..1a51e516f2 100644 --- a/sdk/typescript/lib/generated/models/GenesisLedgerTransactionAllOf.ts +++ b/sdk/typescript/lib/generated/models/GenesisLedgerTransactionAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/HookExport.ts b/sdk/typescript/lib/generated/models/HookExport.ts index b1e07b97ec..a440eb1ec9 100644 --- a/sdk/typescript/lib/generated/models/HookExport.ts +++ b/sdk/typescript/lib/generated/models/HookExport.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/IndexBlueprintCollectionSchema.ts b/sdk/typescript/lib/generated/models/IndexBlueprintCollectionSchema.ts index ed64a9d22e..9aa7984289 100644 --- a/sdk/typescript/lib/generated/models/IndexBlueprintCollectionSchema.ts +++ b/sdk/typescript/lib/generated/models/IndexBlueprintCollectionSchema.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/IndexBlueprintCollectionSchemaAllOf.ts b/sdk/typescript/lib/generated/models/IndexBlueprintCollectionSchemaAllOf.ts index 16be891d47..02acad5874 100644 --- a/sdk/typescript/lib/generated/models/IndexBlueprintCollectionSchemaAllOf.ts +++ b/sdk/typescript/lib/generated/models/IndexBlueprintCollectionSchemaAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/IndexedStateSchema.ts b/sdk/typescript/lib/generated/models/IndexedStateSchema.ts index f291c6dba7..f9d41ef477 100644 --- a/sdk/typescript/lib/generated/models/IndexedStateSchema.ts +++ b/sdk/typescript/lib/generated/models/IndexedStateSchema.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/InstanceSchemaBlueprintTypeReference.ts b/sdk/typescript/lib/generated/models/InstanceSchemaBlueprintTypeReference.ts index 29831b2213..285c2954f4 100644 --- a/sdk/typescript/lib/generated/models/InstanceSchemaBlueprintTypeReference.ts +++ b/sdk/typescript/lib/generated/models/InstanceSchemaBlueprintTypeReference.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/InstanceSchemaBlueprintTypeReferenceAllOf.ts b/sdk/typescript/lib/generated/models/InstanceSchemaBlueprintTypeReferenceAllOf.ts index 4851832ab4..88f7c61332 100644 --- a/sdk/typescript/lib/generated/models/InstanceSchemaBlueprintTypeReferenceAllOf.ts +++ b/sdk/typescript/lib/generated/models/InstanceSchemaBlueprintTypeReferenceAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/InstantMs.ts b/sdk/typescript/lib/generated/models/InstantMs.ts index 4d53832af0..161e958154 100644 --- a/sdk/typescript/lib/generated/models/InstantMs.ts +++ b/sdk/typescript/lib/generated/models/InstantMs.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/InstructionResourceChanges.ts b/sdk/typescript/lib/generated/models/InstructionResourceChanges.ts index 2d91625319..bbe605f6ed 100644 --- a/sdk/typescript/lib/generated/models/InstructionResourceChanges.ts +++ b/sdk/typescript/lib/generated/models/InstructionResourceChanges.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/KeyValueBasedStructure.ts b/sdk/typescript/lib/generated/models/KeyValueBasedStructure.ts index 3f9f483c60..d913a15efe 100644 --- a/sdk/typescript/lib/generated/models/KeyValueBasedStructure.ts +++ b/sdk/typescript/lib/generated/models/KeyValueBasedStructure.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/KeyValueBlueprintCollectionSchema.ts b/sdk/typescript/lib/generated/models/KeyValueBlueprintCollectionSchema.ts index 12f68829fc..df70c9aaec 100644 --- a/sdk/typescript/lib/generated/models/KeyValueBlueprintCollectionSchema.ts +++ b/sdk/typescript/lib/generated/models/KeyValueBlueprintCollectionSchema.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/KeyValueBlueprintCollectionSchemaAllOf.ts b/sdk/typescript/lib/generated/models/KeyValueBlueprintCollectionSchemaAllOf.ts index 8d542e42f9..a61df037d4 100644 --- a/sdk/typescript/lib/generated/models/KeyValueBlueprintCollectionSchemaAllOf.ts +++ b/sdk/typescript/lib/generated/models/KeyValueBlueprintCollectionSchemaAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/KeyValueStoreEntryStructure.ts b/sdk/typescript/lib/generated/models/KeyValueStoreEntryStructure.ts index d779db5cc3..1560a777d0 100644 --- a/sdk/typescript/lib/generated/models/KeyValueStoreEntryStructure.ts +++ b/sdk/typescript/lib/generated/models/KeyValueStoreEntryStructure.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/KeyValueStoreEntryStructureAllOf.ts b/sdk/typescript/lib/generated/models/KeyValueStoreEntryStructureAllOf.ts index fa3f5e875b..d7133a0e9c 100644 --- a/sdk/typescript/lib/generated/models/KeyValueStoreEntryStructureAllOf.ts +++ b/sdk/typescript/lib/generated/models/KeyValueStoreEntryStructureAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/KeyValueStoreInfo.ts b/sdk/typescript/lib/generated/models/KeyValueStoreInfo.ts index 85dfa37436..9eba3f6e3d 100644 --- a/sdk/typescript/lib/generated/models/KeyValueStoreInfo.ts +++ b/sdk/typescript/lib/generated/models/KeyValueStoreInfo.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/KeyValueStoreTypeInfoDetails.ts b/sdk/typescript/lib/generated/models/KeyValueStoreTypeInfoDetails.ts index 44fcfda9c8..d91057d0b6 100644 --- a/sdk/typescript/lib/generated/models/KeyValueStoreTypeInfoDetails.ts +++ b/sdk/typescript/lib/generated/models/KeyValueStoreTypeInfoDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/KeyValueStoreTypeInfoDetailsAllOf.ts b/sdk/typescript/lib/generated/models/KeyValueStoreTypeInfoDetailsAllOf.ts index d5a06b5b37..e6b2d119c1 100644 --- a/sdk/typescript/lib/generated/models/KeyValueStoreTypeInfoDetailsAllOf.ts +++ b/sdk/typescript/lib/generated/models/KeyValueStoreTypeInfoDetailsAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LeaderProposalHistory.ts b/sdk/typescript/lib/generated/models/LeaderProposalHistory.ts index 562074eb89..0d30ac7ced 100644 --- a/sdk/typescript/lib/generated/models/LeaderProposalHistory.ts +++ b/sdk/typescript/lib/generated/models/LeaderProposalHistory.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerHashes.ts b/sdk/typescript/lib/generated/models/LedgerHashes.ts index 20a5cc700c..9208373067 100644 --- a/sdk/typescript/lib/generated/models/LedgerHashes.ts +++ b/sdk/typescript/lib/generated/models/LedgerHashes.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerHeader.ts b/sdk/typescript/lib/generated/models/LedgerHeader.ts index 84562e3b79..e1e786cd54 100644 --- a/sdk/typescript/lib/generated/models/LedgerHeader.ts +++ b/sdk/typescript/lib/generated/models/LedgerHeader.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerHeaderSummary.ts b/sdk/typescript/lib/generated/models/LedgerHeaderSummary.ts index 677dd271f5..147b8c1164 100644 --- a/sdk/typescript/lib/generated/models/LedgerHeaderSummary.ts +++ b/sdk/typescript/lib/generated/models/LedgerHeaderSummary.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerProof.ts b/sdk/typescript/lib/generated/models/LedgerProof.ts index ab335dbfb8..d798dbbb17 100644 --- a/sdk/typescript/lib/generated/models/LedgerProof.ts +++ b/sdk/typescript/lib/generated/models/LedgerProof.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerProofOrigin.ts b/sdk/typescript/lib/generated/models/LedgerProofOrigin.ts index 05808916b4..ed0a9a96a5 100644 --- a/sdk/typescript/lib/generated/models/LedgerProofOrigin.ts +++ b/sdk/typescript/lib/generated/models/LedgerProofOrigin.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerProofOriginBase.ts b/sdk/typescript/lib/generated/models/LedgerProofOriginBase.ts index 09c800cedb..7864018416 100644 --- a/sdk/typescript/lib/generated/models/LedgerProofOriginBase.ts +++ b/sdk/typescript/lib/generated/models/LedgerProofOriginBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerProofOriginType.ts b/sdk/typescript/lib/generated/models/LedgerProofOriginType.ts index 6716859177..c13fa09ee0 100644 --- a/sdk/typescript/lib/generated/models/LedgerProofOriginType.ts +++ b/sdk/typescript/lib/generated/models/LedgerProofOriginType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerStateSelector.ts b/sdk/typescript/lib/generated/models/LedgerStateSelector.ts index 4460eff861..b8338db9e0 100644 --- a/sdk/typescript/lib/generated/models/LedgerStateSelector.ts +++ b/sdk/typescript/lib/generated/models/LedgerStateSelector.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerStateSelectorBase.ts b/sdk/typescript/lib/generated/models/LedgerStateSelectorBase.ts index 16c0cf817b..5ea49ebe0d 100644 --- a/sdk/typescript/lib/generated/models/LedgerStateSelectorBase.ts +++ b/sdk/typescript/lib/generated/models/LedgerStateSelectorBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerStateSelectorType.ts b/sdk/typescript/lib/generated/models/LedgerStateSelectorType.ts index f64d56848f..a30627b2ca 100644 --- a/sdk/typescript/lib/generated/models/LedgerStateSelectorType.ts +++ b/sdk/typescript/lib/generated/models/LedgerStateSelectorType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerStateSummary.ts b/sdk/typescript/lib/generated/models/LedgerStateSummary.ts index 911ea6987e..8a9f0c104b 100644 --- a/sdk/typescript/lib/generated/models/LedgerStateSummary.ts +++ b/sdk/typescript/lib/generated/models/LedgerStateSummary.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerTransaction.ts b/sdk/typescript/lib/generated/models/LedgerTransaction.ts index 589b27f670..cb09c60785 100644 --- a/sdk/typescript/lib/generated/models/LedgerTransaction.ts +++ b/sdk/typescript/lib/generated/models/LedgerTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerTransactionBase.ts b/sdk/typescript/lib/generated/models/LedgerTransactionBase.ts index 9667053584..75af080ca6 100644 --- a/sdk/typescript/lib/generated/models/LedgerTransactionBase.ts +++ b/sdk/typescript/lib/generated/models/LedgerTransactionBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LedgerTransactionType.ts b/sdk/typescript/lib/generated/models/LedgerTransactionType.ts index ee81a63858..fe29873a0c 100644 --- a/sdk/typescript/lib/generated/models/LedgerTransactionType.ts +++ b/sdk/typescript/lib/generated/models/LedgerTransactionType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LimitParameters.ts b/sdk/typescript/lib/generated/models/LimitParameters.ts index 74e6024c7e..e8d72fc94a 100644 --- a/sdk/typescript/lib/generated/models/LimitParameters.ts +++ b/sdk/typescript/lib/generated/models/LimitParameters.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LocalGenericSubstitution.ts b/sdk/typescript/lib/generated/models/LocalGenericSubstitution.ts index 26b08cf3e5..cd13d4194c 100644 --- a/sdk/typescript/lib/generated/models/LocalGenericSubstitution.ts +++ b/sdk/typescript/lib/generated/models/LocalGenericSubstitution.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LocalGenericSubstitutionAllOf.ts b/sdk/typescript/lib/generated/models/LocalGenericSubstitutionAllOf.ts index b7b8fadf85..b0c42f1301 100644 --- a/sdk/typescript/lib/generated/models/LocalGenericSubstitutionAllOf.ts +++ b/sdk/typescript/lib/generated/models/LocalGenericSubstitutionAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LocalNonFungibleKey.ts b/sdk/typescript/lib/generated/models/LocalNonFungibleKey.ts index d7fa420223..f060c1f645 100644 --- a/sdk/typescript/lib/generated/models/LocalNonFungibleKey.ts +++ b/sdk/typescript/lib/generated/models/LocalNonFungibleKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LocalTypeId.ts b/sdk/typescript/lib/generated/models/LocalTypeId.ts index 08b77c059c..ea56e004ac 100644 --- a/sdk/typescript/lib/generated/models/LocalTypeId.ts +++ b/sdk/typescript/lib/generated/models/LocalTypeId.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsCommittedTransactionOutcome.ts b/sdk/typescript/lib/generated/models/LtsCommittedTransactionOutcome.ts index ad4836a5a3..b57a412328 100644 --- a/sdk/typescript/lib/generated/models/LtsCommittedTransactionOutcome.ts +++ b/sdk/typescript/lib/generated/models/LtsCommittedTransactionOutcome.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsCommittedTransactionStatus.ts b/sdk/typescript/lib/generated/models/LtsCommittedTransactionStatus.ts index e8a8762043..9760a02d01 100644 --- a/sdk/typescript/lib/generated/models/LtsCommittedTransactionStatus.ts +++ b/sdk/typescript/lib/generated/models/LtsCommittedTransactionStatus.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsEntityFungibleBalanceChanges.ts b/sdk/typescript/lib/generated/models/LtsEntityFungibleBalanceChanges.ts index ec5fb2881d..476c4c1d68 100644 --- a/sdk/typescript/lib/generated/models/LtsEntityFungibleBalanceChanges.ts +++ b/sdk/typescript/lib/generated/models/LtsEntityFungibleBalanceChanges.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsEntityNonFungibleBalanceChanges.ts b/sdk/typescript/lib/generated/models/LtsEntityNonFungibleBalanceChanges.ts index d0e9054549..f9188ca249 100644 --- a/sdk/typescript/lib/generated/models/LtsEntityNonFungibleBalanceChanges.ts +++ b/sdk/typescript/lib/generated/models/LtsEntityNonFungibleBalanceChanges.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsFeeFungibleResourceBalanceChange.ts b/sdk/typescript/lib/generated/models/LtsFeeFungibleResourceBalanceChange.ts index d873ecb445..2729d725f6 100644 --- a/sdk/typescript/lib/generated/models/LtsFeeFungibleResourceBalanceChange.ts +++ b/sdk/typescript/lib/generated/models/LtsFeeFungibleResourceBalanceChange.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsFeeFungibleResourceBalanceChangeType.ts b/sdk/typescript/lib/generated/models/LtsFeeFungibleResourceBalanceChangeType.ts index 7972902215..2a10aafd5f 100644 --- a/sdk/typescript/lib/generated/models/LtsFeeFungibleResourceBalanceChangeType.ts +++ b/sdk/typescript/lib/generated/models/LtsFeeFungibleResourceBalanceChangeType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsFungibleResourceBalance.ts b/sdk/typescript/lib/generated/models/LtsFungibleResourceBalance.ts index bf348e4725..9f18524110 100644 --- a/sdk/typescript/lib/generated/models/LtsFungibleResourceBalance.ts +++ b/sdk/typescript/lib/generated/models/LtsFungibleResourceBalance.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsFungibleResourceBalanceChange.ts b/sdk/typescript/lib/generated/models/LtsFungibleResourceBalanceChange.ts index eb4ee7db87..d458a39f18 100644 --- a/sdk/typescript/lib/generated/models/LtsFungibleResourceBalanceChange.ts +++ b/sdk/typescript/lib/generated/models/LtsFungibleResourceBalanceChange.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsResultantAccountFungibleBalances.ts b/sdk/typescript/lib/generated/models/LtsResultantAccountFungibleBalances.ts index 550bc58d0c..5877829eda 100644 --- a/sdk/typescript/lib/generated/models/LtsResultantAccountFungibleBalances.ts +++ b/sdk/typescript/lib/generated/models/LtsResultantAccountFungibleBalances.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsResultantFungibleBalance.ts b/sdk/typescript/lib/generated/models/LtsResultantFungibleBalance.ts index f6c7f77135..a0f2e3ea06 100644 --- a/sdk/typescript/lib/generated/models/LtsResultantFungibleBalance.ts +++ b/sdk/typescript/lib/generated/models/LtsResultantFungibleBalance.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsStateAccountAllFungibleResourceBalancesRequest.ts b/sdk/typescript/lib/generated/models/LtsStateAccountAllFungibleResourceBalancesRequest.ts index c5da913daa..93bfbea39a 100644 --- a/sdk/typescript/lib/generated/models/LtsStateAccountAllFungibleResourceBalancesRequest.ts +++ b/sdk/typescript/lib/generated/models/LtsStateAccountAllFungibleResourceBalancesRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsStateAccountAllFungibleResourceBalancesResponse.ts b/sdk/typescript/lib/generated/models/LtsStateAccountAllFungibleResourceBalancesResponse.ts index e19cbce166..adbdc4dd1e 100644 --- a/sdk/typescript/lib/generated/models/LtsStateAccountAllFungibleResourceBalancesResponse.ts +++ b/sdk/typescript/lib/generated/models/LtsStateAccountAllFungibleResourceBalancesResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsStateAccountDepositBehaviourRequest.ts b/sdk/typescript/lib/generated/models/LtsStateAccountDepositBehaviourRequest.ts index 87cbbb6a0c..de40c40339 100644 --- a/sdk/typescript/lib/generated/models/LtsStateAccountDepositBehaviourRequest.ts +++ b/sdk/typescript/lib/generated/models/LtsStateAccountDepositBehaviourRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsStateAccountDepositBehaviourResponse.ts b/sdk/typescript/lib/generated/models/LtsStateAccountDepositBehaviourResponse.ts index a2a405a227..d7e12d2907 100644 --- a/sdk/typescript/lib/generated/models/LtsStateAccountDepositBehaviourResponse.ts +++ b/sdk/typescript/lib/generated/models/LtsStateAccountDepositBehaviourResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsStateAccountFungibleResourceBalanceRequest.ts b/sdk/typescript/lib/generated/models/LtsStateAccountFungibleResourceBalanceRequest.ts index 49d844f307..3cab5f3d4c 100644 --- a/sdk/typescript/lib/generated/models/LtsStateAccountFungibleResourceBalanceRequest.ts +++ b/sdk/typescript/lib/generated/models/LtsStateAccountFungibleResourceBalanceRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsStateAccountFungibleResourceBalanceResponse.ts b/sdk/typescript/lib/generated/models/LtsStateAccountFungibleResourceBalanceResponse.ts index a44d15a62b..0a1b1bd1c6 100644 --- a/sdk/typescript/lib/generated/models/LtsStateAccountFungibleResourceBalanceResponse.ts +++ b/sdk/typescript/lib/generated/models/LtsStateAccountFungibleResourceBalanceResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsStreamAccountTransactionOutcomesRequest.ts b/sdk/typescript/lib/generated/models/LtsStreamAccountTransactionOutcomesRequest.ts index f052aa1d63..a8f568c45f 100644 --- a/sdk/typescript/lib/generated/models/LtsStreamAccountTransactionOutcomesRequest.ts +++ b/sdk/typescript/lib/generated/models/LtsStreamAccountTransactionOutcomesRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsStreamAccountTransactionOutcomesResponse.ts b/sdk/typescript/lib/generated/models/LtsStreamAccountTransactionOutcomesResponse.ts index 92175f1427..8d34065c0b 100644 --- a/sdk/typescript/lib/generated/models/LtsStreamAccountTransactionOutcomesResponse.ts +++ b/sdk/typescript/lib/generated/models/LtsStreamAccountTransactionOutcomesResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsStreamTransactionOutcomesRequest.ts b/sdk/typescript/lib/generated/models/LtsStreamTransactionOutcomesRequest.ts index 3ea56210ca..5194cc8219 100644 --- a/sdk/typescript/lib/generated/models/LtsStreamTransactionOutcomesRequest.ts +++ b/sdk/typescript/lib/generated/models/LtsStreamTransactionOutcomesRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsStreamTransactionOutcomesResponse.ts b/sdk/typescript/lib/generated/models/LtsStreamTransactionOutcomesResponse.ts index 7455e59ae0..027d4a3444 100644 --- a/sdk/typescript/lib/generated/models/LtsStreamTransactionOutcomesResponse.ts +++ b/sdk/typescript/lib/generated/models/LtsStreamTransactionOutcomesResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionConstructionRequest.ts b/sdk/typescript/lib/generated/models/LtsTransactionConstructionRequest.ts index ffc7c08cc7..aeea2e953a 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionConstructionRequest.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionConstructionRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionConstructionResponse.ts b/sdk/typescript/lib/generated/models/LtsTransactionConstructionResponse.ts index 09179fbf67..843592c657 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionConstructionResponse.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionConstructionResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionIntentStatus.ts b/sdk/typescript/lib/generated/models/LtsTransactionIntentStatus.ts index 55d93479fd..48e5330860 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionIntentStatus.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionIntentStatus.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionPayloadDetails.ts b/sdk/typescript/lib/generated/models/LtsTransactionPayloadDetails.ts index c575db95c9..72ae270c42 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionPayloadDetails.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionPayloadDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionPayloadStatus.ts b/sdk/typescript/lib/generated/models/LtsTransactionPayloadStatus.ts index 8a90d593fe..28b24c6f43 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionPayloadStatus.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionPayloadStatus.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionStatusRequest.ts b/sdk/typescript/lib/generated/models/LtsTransactionStatusRequest.ts index 7656ceeddd..ac4bdad069 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionStatusRequest.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionStatusRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionStatusResponse.ts b/sdk/typescript/lib/generated/models/LtsTransactionStatusResponse.ts index 4321880d5b..37abcb5f2c 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionStatusResponse.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionStatusResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetails.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetails.ts index 4da7a12fdc..ea72b3daab 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetails.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetailsBase.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetailsBase.ts index 6974ec8588..168fbe1b65 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetailsBase.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetailsBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetailsType.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetailsType.ts index 2bb04d3a82..b0a5b316ce 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetailsType.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorDetailsType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorResponse.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorResponse.ts index ecc19222b0..a5524f1ab1 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorResponse.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorResponseAllOf.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorResponseAllOf.ts index f828d52b39..e0b56cce61 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorResponseAllOf.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitErrorResponseAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitIntentAlreadyCommitted.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitIntentAlreadyCommitted.ts index 50656573a3..cf31d89269 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitIntentAlreadyCommitted.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitIntentAlreadyCommitted.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitIntentAlreadyCommittedAllOf.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitIntentAlreadyCommittedAllOf.ts index 612b14fcd8..d6a02aac1b 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitIntentAlreadyCommittedAllOf.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitIntentAlreadyCommittedAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.ts index 7a90e9e2a1..484a3bb1b5 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetailsAllOf.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetailsAllOf.ts index 84c6011dce..e7cad0bff2 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetailsAllOf.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitPriorityThresholdNotMetErrorDetailsAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitRejectedErrorDetails.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitRejectedErrorDetails.ts index a7e3bcd454..c3763a2b79 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitRejectedErrorDetails.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitRejectedErrorDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitRejectedErrorDetailsAllOf.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitRejectedErrorDetailsAllOf.ts index a55c0f6a07..ac2b9636fc 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitRejectedErrorDetailsAllOf.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitRejectedErrorDetailsAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitRequest.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitRequest.ts index 4d035f8de9..2296ec99e4 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitRequest.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/LtsTransactionSubmitResponse.ts b/sdk/typescript/lib/generated/models/LtsTransactionSubmitResponse.ts index 1d8b5afaa1..6ebbed7e21 100644 --- a/sdk/typescript/lib/generated/models/LtsTransactionSubmitResponse.ts +++ b/sdk/typescript/lib/generated/models/LtsTransactionSubmitResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MainMethodKey.ts b/sdk/typescript/lib/generated/models/MainMethodKey.ts index 275b41a672..412ffb7168 100644 --- a/sdk/typescript/lib/generated/models/MainMethodKey.ts +++ b/sdk/typescript/lib/generated/models/MainMethodKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MapSubstateKey.ts b/sdk/typescript/lib/generated/models/MapSubstateKey.ts index e342bc9de4..27e76f5e69 100644 --- a/sdk/typescript/lib/generated/models/MapSubstateKey.ts +++ b/sdk/typescript/lib/generated/models/MapSubstateKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MapSubstateKeyAllOf.ts b/sdk/typescript/lib/generated/models/MapSubstateKeyAllOf.ts index 79e5dd242d..bb6860d334 100644 --- a/sdk/typescript/lib/generated/models/MapSubstateKeyAllOf.ts +++ b/sdk/typescript/lib/generated/models/MapSubstateKeyAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MempoolListRequest.ts b/sdk/typescript/lib/generated/models/MempoolListRequest.ts index c7cf113353..57c2d848c3 100644 --- a/sdk/typescript/lib/generated/models/MempoolListRequest.ts +++ b/sdk/typescript/lib/generated/models/MempoolListRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MempoolListResponse.ts b/sdk/typescript/lib/generated/models/MempoolListResponse.ts index d5e0cfe758..a4f38cdd99 100644 --- a/sdk/typescript/lib/generated/models/MempoolListResponse.ts +++ b/sdk/typescript/lib/generated/models/MempoolListResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MempoolTransactionHashes.ts b/sdk/typescript/lib/generated/models/MempoolTransactionHashes.ts index 30473c3963..c12d0c733b 100644 --- a/sdk/typescript/lib/generated/models/MempoolTransactionHashes.ts +++ b/sdk/typescript/lib/generated/models/MempoolTransactionHashes.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MempoolTransactionRequest.ts b/sdk/typescript/lib/generated/models/MempoolTransactionRequest.ts index acf68c0c43..95cd52c645 100644 --- a/sdk/typescript/lib/generated/models/MempoolTransactionRequest.ts +++ b/sdk/typescript/lib/generated/models/MempoolTransactionRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MempoolTransactionResponse.ts b/sdk/typescript/lib/generated/models/MempoolTransactionResponse.ts index f3b8a90f4a..317f0aabb3 100644 --- a/sdk/typescript/lib/generated/models/MempoolTransactionResponse.ts +++ b/sdk/typescript/lib/generated/models/MempoolTransactionResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MempoolTransactionResponsePayloadsInner.ts b/sdk/typescript/lib/generated/models/MempoolTransactionResponsePayloadsInner.ts index 90d6bbeb49..0731ee37f3 100644 --- a/sdk/typescript/lib/generated/models/MempoolTransactionResponsePayloadsInner.ts +++ b/sdk/typescript/lib/generated/models/MempoolTransactionResponsePayloadsInner.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MetadataKey.ts b/sdk/typescript/lib/generated/models/MetadataKey.ts index 2e353938e2..2a09ed63d6 100644 --- a/sdk/typescript/lib/generated/models/MetadataKey.ts +++ b/sdk/typescript/lib/generated/models/MetadataKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MetadataModuleEntrySubstate.ts b/sdk/typescript/lib/generated/models/MetadataModuleEntrySubstate.ts index 04dd479047..f614ee3eb9 100644 --- a/sdk/typescript/lib/generated/models/MetadataModuleEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/MetadataModuleEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MetadataModuleEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/MetadataModuleEntrySubstateAllOf.ts index cab99d79b4..cb3e21951d 100644 --- a/sdk/typescript/lib/generated/models/MetadataModuleEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/MetadataModuleEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MetadataModuleEntryValue.ts b/sdk/typescript/lib/generated/models/MetadataModuleEntryValue.ts index 2ab0d5a76f..9c99ad37e5 100644 --- a/sdk/typescript/lib/generated/models/MetadataModuleEntryValue.ts +++ b/sdk/typescript/lib/generated/models/MetadataModuleEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MethodAccessibility.ts b/sdk/typescript/lib/generated/models/MethodAccessibility.ts index 904ef48082..24e1c69b2d 100644 --- a/sdk/typescript/lib/generated/models/MethodAccessibility.ts +++ b/sdk/typescript/lib/generated/models/MethodAccessibility.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MethodAccessibilityBase.ts b/sdk/typescript/lib/generated/models/MethodAccessibilityBase.ts index 059607807e..7e70409f60 100644 --- a/sdk/typescript/lib/generated/models/MethodAccessibilityBase.ts +++ b/sdk/typescript/lib/generated/models/MethodAccessibilityBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MethodAccessibilityType.ts b/sdk/typescript/lib/generated/models/MethodAccessibilityType.ts index d84cd62a40..d790076647 100644 --- a/sdk/typescript/lib/generated/models/MethodAccessibilityType.ts +++ b/sdk/typescript/lib/generated/models/MethodAccessibilityType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MethodAuthType.ts b/sdk/typescript/lib/generated/models/MethodAuthType.ts index 260cd2c5b1..f80b91f946 100644 --- a/sdk/typescript/lib/generated/models/MethodAuthType.ts +++ b/sdk/typescript/lib/generated/models/MethodAuthType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MethodEventEmitterIdentifier.ts b/sdk/typescript/lib/generated/models/MethodEventEmitterIdentifier.ts index f0642eec45..876e4067cd 100644 --- a/sdk/typescript/lib/generated/models/MethodEventEmitterIdentifier.ts +++ b/sdk/typescript/lib/generated/models/MethodEventEmitterIdentifier.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MethodEventEmitterIdentifierAllOf.ts b/sdk/typescript/lib/generated/models/MethodEventEmitterIdentifierAllOf.ts index 22ed5dd54d..e5dd08d293 100644 --- a/sdk/typescript/lib/generated/models/MethodEventEmitterIdentifierAllOf.ts +++ b/sdk/typescript/lib/generated/models/MethodEventEmitterIdentifierAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ModuleId.ts b/sdk/typescript/lib/generated/models/ModuleId.ts index 0fa20d3572..f71ca1550f 100644 --- a/sdk/typescript/lib/generated/models/ModuleId.ts +++ b/sdk/typescript/lib/generated/models/ModuleId.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ModuleVersion.ts b/sdk/typescript/lib/generated/models/ModuleVersion.ts index 240198d0e6..057835bf01 100644 --- a/sdk/typescript/lib/generated/models/ModuleVersion.ts +++ b/sdk/typescript/lib/generated/models/ModuleVersion.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateSubstate.ts b/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateSubstate.ts index 5625ca2e0e..275df86f55 100644 --- a/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateSubstate.ts +++ b/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateSubstateAllOf.ts b/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateSubstateAllOf.ts index c62897f234..6b7c4c40a1 100644 --- a/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateValue.ts b/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateValue.ts index b43e96faf5..d26510e9ee 100644 --- a/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateValue.ts +++ b/sdk/typescript/lib/generated/models/MultiResourcePoolFieldStateValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/MutableField.ts b/sdk/typescript/lib/generated/models/MutableField.ts index 387cfa6bb7..8c9a88d613 100644 --- a/sdk/typescript/lib/generated/models/MutableField.ts +++ b/sdk/typescript/lib/generated/models/MutableField.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NetworkConfigurationResponse.ts b/sdk/typescript/lib/generated/models/NetworkConfigurationResponse.ts index 9c5c684f69..120fca2d06 100644 --- a/sdk/typescript/lib/generated/models/NetworkConfigurationResponse.ts +++ b/sdk/typescript/lib/generated/models/NetworkConfigurationResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NetworkConfigurationResponseVersion.ts b/sdk/typescript/lib/generated/models/NetworkConfigurationResponseVersion.ts index 4cb6ee1bf0..7ea6953dc1 100644 --- a/sdk/typescript/lib/generated/models/NetworkConfigurationResponseVersion.ts +++ b/sdk/typescript/lib/generated/models/NetworkConfigurationResponseVersion.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NetworkConfigurationResponseWellKnownAddresses.ts b/sdk/typescript/lib/generated/models/NetworkConfigurationResponseWellKnownAddresses.ts index c7c9549ebf..ad647faec0 100644 --- a/sdk/typescript/lib/generated/models/NetworkConfigurationResponseWellKnownAddresses.ts +++ b/sdk/typescript/lib/generated/models/NetworkConfigurationResponseWellKnownAddresses.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NetworkDefinition.ts b/sdk/typescript/lib/generated/models/NetworkDefinition.ts index 58c99f8ee5..5e820d1d4d 100644 --- a/sdk/typescript/lib/generated/models/NetworkDefinition.ts +++ b/sdk/typescript/lib/generated/models/NetworkDefinition.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NetworkStatusRequest.ts b/sdk/typescript/lib/generated/models/NetworkStatusRequest.ts index 943d6a7184..f0347b20dc 100644 --- a/sdk/typescript/lib/generated/models/NetworkStatusRequest.ts +++ b/sdk/typescript/lib/generated/models/NetworkStatusRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NetworkStatusResponse.ts b/sdk/typescript/lib/generated/models/NetworkStatusResponse.ts index d11aef2aa0..f45b22ae27 100644 --- a/sdk/typescript/lib/generated/models/NetworkStatusResponse.ts +++ b/sdk/typescript/lib/generated/models/NetworkStatusResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NextEpoch.ts b/sdk/typescript/lib/generated/models/NextEpoch.ts index aeefbb3e9b..212b8f4e6c 100644 --- a/sdk/typescript/lib/generated/models/NextEpoch.ts +++ b/sdk/typescript/lib/generated/models/NextEpoch.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleAuthorizedDepositorBadge.ts b/sdk/typescript/lib/generated/models/NonFungibleAuthorizedDepositorBadge.ts index 426ff4575f..6583f291c5 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleAuthorizedDepositorBadge.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleAuthorizedDepositorBadge.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleAuthorizedDepositorBadgeAllOf.ts b/sdk/typescript/lib/generated/models/NonFungibleAuthorizedDepositorBadgeAllOf.ts index 4d3373027a..58c885fcfe 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleAuthorizedDepositorBadgeAllOf.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleAuthorizedDepositorBadgeAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleGlobalId.ts b/sdk/typescript/lib/generated/models/NonFungibleGlobalId.ts index e683b3cc58..5bc1766343 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleGlobalId.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleGlobalId.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleIdType.ts b/sdk/typescript/lib/generated/models/NonFungibleIdType.ts index b122d41acc..11ca60fe63 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleIdType.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleIdType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleLocalId.ts b/sdk/typescript/lib/generated/models/NonFungibleLocalId.ts index e85d68f3ae..7be7d60b13 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleLocalId.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleLocalId.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungiblePresentedBadge.ts b/sdk/typescript/lib/generated/models/NonFungiblePresentedBadge.ts index 148ab2c280..cd7e95a94d 100644 --- a/sdk/typescript/lib/generated/models/NonFungiblePresentedBadge.ts +++ b/sdk/typescript/lib/generated/models/NonFungiblePresentedBadge.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungiblePresentedBadgeAllOf.ts b/sdk/typescript/lib/generated/models/NonFungiblePresentedBadgeAllOf.ts index c7afd445a0..c2294e0e9a 100644 --- a/sdk/typescript/lib/generated/models/NonFungiblePresentedBadgeAllOf.ts +++ b/sdk/typescript/lib/generated/models/NonFungiblePresentedBadgeAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleRequirement.ts b/sdk/typescript/lib/generated/models/NonFungibleRequirement.ts index e3d148023f..7bffdea13a 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleRequirement.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleRequirement.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleRequirementAllOf.ts b/sdk/typescript/lib/generated/models/NonFungibleRequirementAllOf.ts index bd57e1fe9c..da94a911e9 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleRequirementAllOf.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleRequirementAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceAmount.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceAmount.ts index 2fc25420be..2512671e3e 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceAmount.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceAmount.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceAmountAllOf.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceAmountAllOf.ts index ffe6041e9c..21f0e35cd3 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceAmountAllOf.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceAmountAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntrySubstate.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntrySubstate.ts index 6dac80a32b..094bf7fac0 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntrySubstateAllOf.ts index b8937f963c..74e92a5bec 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntryValue.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntryValue.ts index 3c3a07fb67..62a4db6e90 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntryValue.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerDataEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeSubstate.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeSubstate.ts index 392bc2a203..3762f44046 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeSubstate.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeSubstateAllOf.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeSubstateAllOf.ts index 94efa73f98..aff5288f92 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeValue.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeValue.ts index 9fff82eb52..e8e5cf9db3 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeValue.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldIdTypeValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstate.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstate.ts index de3a5103c9..cbc6647fdd 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstate.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstateAllOf.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstateAllOf.ts index c3db7f4ba6..ec803d89c3 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsValue.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsValue.ts index 05e3c681de..0a61fcaf54 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsValue.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldMutableFieldsValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstate.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstate.ts index 1206565319..a8cb6717df 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstate.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstateAllOf.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstateAllOf.ts index b6ebf57015..7880759743 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplyValue.ts b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplyValue.ts index 2279f86782..74ed22de3b 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplyValue.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleResourceManagerFieldTotalSupplyValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntrySubstate.ts b/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntrySubstate.ts index 00c47643a0..2f46ccc215 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntrySubstateAllOf.ts index 3dd00ebba0..25b77ee0bb 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntryValue.ts b/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntryValue.ts index 47b50a4d45..58fd9017a0 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntryValue.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleVaultContentsIndexEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceSubstate.ts b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceSubstate.ts index 9766c24443..11a2b8d2fb 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceSubstate.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceSubstateAllOf.ts b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceSubstateAllOf.ts index 27588f418b..c020262757 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceValue.ts b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceValue.ts index 963977f5a3..0f76711c95 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceValue.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldBalanceValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusSubstate.ts b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusSubstate.ts index 247209e0c6..9a5466fdc2 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusSubstate.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusSubstateAllOf.ts b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusSubstateAllOf.ts index e30cc18113..f494bf45eb 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusValue.ts b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusValue.ts index 00b639bff7..a6bd3d571e 100644 --- a/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusValue.ts +++ b/sdk/typescript/lib/generated/models/NonFungibleVaultFieldFrozenStatusValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/NotarizedTransaction.ts b/sdk/typescript/lib/generated/models/NotarizedTransaction.ts index d6ed44c2ee..17815c5453 100644 --- a/sdk/typescript/lib/generated/models/NotarizedTransaction.ts +++ b/sdk/typescript/lib/generated/models/NotarizedTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectFieldStructure.ts b/sdk/typescript/lib/generated/models/ObjectFieldStructure.ts index ae6391fb82..0baaa65d3b 100644 --- a/sdk/typescript/lib/generated/models/ObjectFieldStructure.ts +++ b/sdk/typescript/lib/generated/models/ObjectFieldStructure.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectFieldStructureAllOf.ts b/sdk/typescript/lib/generated/models/ObjectFieldStructureAllOf.ts index cc7474517e..ae71313a34 100644 --- a/sdk/typescript/lib/generated/models/ObjectFieldStructureAllOf.ts +++ b/sdk/typescript/lib/generated/models/ObjectFieldStructureAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectHook.ts b/sdk/typescript/lib/generated/models/ObjectHook.ts index 09d5aec6bb..3031832357 100644 --- a/sdk/typescript/lib/generated/models/ObjectHook.ts +++ b/sdk/typescript/lib/generated/models/ObjectHook.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectIndexPartitionEntryStructure.ts b/sdk/typescript/lib/generated/models/ObjectIndexPartitionEntryStructure.ts index 323f92b8ba..c1ed724cf3 100644 --- a/sdk/typescript/lib/generated/models/ObjectIndexPartitionEntryStructure.ts +++ b/sdk/typescript/lib/generated/models/ObjectIndexPartitionEntryStructure.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectIndexPartitionEntryStructureAllOf.ts b/sdk/typescript/lib/generated/models/ObjectIndexPartitionEntryStructureAllOf.ts index dfa299106e..bcf9352671 100644 --- a/sdk/typescript/lib/generated/models/ObjectIndexPartitionEntryStructureAllOf.ts +++ b/sdk/typescript/lib/generated/models/ObjectIndexPartitionEntryStructureAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectInstanceTypeReference.ts b/sdk/typescript/lib/generated/models/ObjectInstanceTypeReference.ts index 0737919461..67a017be1d 100644 --- a/sdk/typescript/lib/generated/models/ObjectInstanceTypeReference.ts +++ b/sdk/typescript/lib/generated/models/ObjectInstanceTypeReference.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectInstanceTypeReferenceAllOf.ts b/sdk/typescript/lib/generated/models/ObjectInstanceTypeReferenceAllOf.ts index b235f62446..b3fcc4f3b9 100644 --- a/sdk/typescript/lib/generated/models/ObjectInstanceTypeReferenceAllOf.ts +++ b/sdk/typescript/lib/generated/models/ObjectInstanceTypeReferenceAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectKeyValuePartitionEntryStructure.ts b/sdk/typescript/lib/generated/models/ObjectKeyValuePartitionEntryStructure.ts index 309981588a..2597e27066 100644 --- a/sdk/typescript/lib/generated/models/ObjectKeyValuePartitionEntryStructure.ts +++ b/sdk/typescript/lib/generated/models/ObjectKeyValuePartitionEntryStructure.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectKeyValuePartitionEntryStructureAllOf.ts b/sdk/typescript/lib/generated/models/ObjectKeyValuePartitionEntryStructureAllOf.ts index f06808a651..06eb776544 100644 --- a/sdk/typescript/lib/generated/models/ObjectKeyValuePartitionEntryStructureAllOf.ts +++ b/sdk/typescript/lib/generated/models/ObjectKeyValuePartitionEntryStructureAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectRoleKey.ts b/sdk/typescript/lib/generated/models/ObjectRoleKey.ts index 25ae1961e2..4b889fe8aa 100644 --- a/sdk/typescript/lib/generated/models/ObjectRoleKey.ts +++ b/sdk/typescript/lib/generated/models/ObjectRoleKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectSortedIndexPartitionEntryStructure.ts b/sdk/typescript/lib/generated/models/ObjectSortedIndexPartitionEntryStructure.ts index 84716287b5..d4d25f5e77 100644 --- a/sdk/typescript/lib/generated/models/ObjectSortedIndexPartitionEntryStructure.ts +++ b/sdk/typescript/lib/generated/models/ObjectSortedIndexPartitionEntryStructure.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectSortedIndexPartitionEntryStructureAllOf.ts b/sdk/typescript/lib/generated/models/ObjectSortedIndexPartitionEntryStructureAllOf.ts index dd176814d5..8cbdafc467 100644 --- a/sdk/typescript/lib/generated/models/ObjectSortedIndexPartitionEntryStructureAllOf.ts +++ b/sdk/typescript/lib/generated/models/ObjectSortedIndexPartitionEntryStructureAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectSubstateTypeReference.ts b/sdk/typescript/lib/generated/models/ObjectSubstateTypeReference.ts index 1c9c2058b3..b85bef6058 100644 --- a/sdk/typescript/lib/generated/models/ObjectSubstateTypeReference.ts +++ b/sdk/typescript/lib/generated/models/ObjectSubstateTypeReference.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectSubstateTypeReferenceBase.ts b/sdk/typescript/lib/generated/models/ObjectSubstateTypeReferenceBase.ts index 0760adab36..9a0b7f5dc9 100644 --- a/sdk/typescript/lib/generated/models/ObjectSubstateTypeReferenceBase.ts +++ b/sdk/typescript/lib/generated/models/ObjectSubstateTypeReferenceBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectSubstateTypeReferenceType.ts b/sdk/typescript/lib/generated/models/ObjectSubstateTypeReferenceType.ts index 03a1f12e54..b98f23b20b 100644 --- a/sdk/typescript/lib/generated/models/ObjectSubstateTypeReferenceType.ts +++ b/sdk/typescript/lib/generated/models/ObjectSubstateTypeReferenceType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectTypeInfoDetails.ts b/sdk/typescript/lib/generated/models/ObjectTypeInfoDetails.ts index 0023382782..043266dd63 100644 --- a/sdk/typescript/lib/generated/models/ObjectTypeInfoDetails.ts +++ b/sdk/typescript/lib/generated/models/ObjectTypeInfoDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ObjectTypeInfoDetailsAllOf.ts b/sdk/typescript/lib/generated/models/ObjectTypeInfoDetailsAllOf.ts index 8926225ffb..983bd8fbf0 100644 --- a/sdk/typescript/lib/generated/models/ObjectTypeInfoDetailsAllOf.ts +++ b/sdk/typescript/lib/generated/models/ObjectTypeInfoDetailsAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateSubstate.ts b/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateSubstate.ts index f856aeb38a..4d26387c9f 100644 --- a/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateSubstate.ts +++ b/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateSubstateAllOf.ts b/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateSubstateAllOf.ts index 8dafbb3be2..9f1a3d3f77 100644 --- a/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateValue.ts b/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateValue.ts index 97bf28037a..33f346c857 100644 --- a/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateValue.ts +++ b/sdk/typescript/lib/generated/models/OneResourcePoolFieldStateValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/OuterObjectOnlyMethodAccessibility.ts b/sdk/typescript/lib/generated/models/OuterObjectOnlyMethodAccessibility.ts index b57cf0beff..70af7f044b 100644 --- a/sdk/typescript/lib/generated/models/OuterObjectOnlyMethodAccessibility.ts +++ b/sdk/typescript/lib/generated/models/OuterObjectOnlyMethodAccessibility.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/OuterObjectOnlyMethodAccessibilityAllOf.ts b/sdk/typescript/lib/generated/models/OuterObjectOnlyMethodAccessibilityAllOf.ts index 7908003a39..0d2808e6ba 100644 --- a/sdk/typescript/lib/generated/models/OuterObjectOnlyMethodAccessibilityAllOf.ts +++ b/sdk/typescript/lib/generated/models/OuterObjectOnlyMethodAccessibilityAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/OwnPackageOnlyMethodAccessibility.ts b/sdk/typescript/lib/generated/models/OwnPackageOnlyMethodAccessibility.ts index 9a63a80e78..a0d1b1850f 100644 --- a/sdk/typescript/lib/generated/models/OwnPackageOnlyMethodAccessibility.ts +++ b/sdk/typescript/lib/generated/models/OwnPackageOnlyMethodAccessibility.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/OwnPackageOnlyMethodAccessibilityAllOf.ts b/sdk/typescript/lib/generated/models/OwnPackageOnlyMethodAccessibilityAllOf.ts index 60c8ebdea9..b7250f1367 100644 --- a/sdk/typescript/lib/generated/models/OwnPackageOnlyMethodAccessibilityAllOf.ts +++ b/sdk/typescript/lib/generated/models/OwnPackageOnlyMethodAccessibilityAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/OwnerRole.ts b/sdk/typescript/lib/generated/models/OwnerRole.ts index 43480303a7..b811ff985e 100644 --- a/sdk/typescript/lib/generated/models/OwnerRole.ts +++ b/sdk/typescript/lib/generated/models/OwnerRole.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/OwnerRoleUpdater.ts b/sdk/typescript/lib/generated/models/OwnerRoleUpdater.ts index 758c0d0d51..b7f3d134c3 100644 --- a/sdk/typescript/lib/generated/models/OwnerRoleUpdater.ts +++ b/sdk/typescript/lib/generated/models/OwnerRoleUpdater.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntrySubstate.ts b/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntrySubstate.ts index c6e7978673..cab3fb36ce 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntrySubstateAllOf.ts index e0eadb6954..00098be2b8 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntryValue.ts b/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntryValue.ts index 1268868617..42a0af2331 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntryValue.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintAuthTemplateEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntrySubstate.ts b/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntrySubstate.ts index 1997193bb4..081bfe287e 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntrySubstateAllOf.ts index d8b2361517..ebcec9c1f0 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntryValue.ts b/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntryValue.ts index 5a5ccea9d9..7ae2493fee 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntryValue.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintDefinitionEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntrySubstate.ts b/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntrySubstate.ts index af2fd2b470..a3cfac8d9d 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntrySubstateAllOf.ts index e02f684750..45cf053e54 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntryValue.ts b/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntryValue.ts index 1b381c3ada..60e852ca04 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntryValue.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintDependenciesEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntrySubstate.ts b/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntrySubstate.ts index 9868c13cba..ae66eac705 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntrySubstateAllOf.ts index 295ca8b95d..cf6364321a 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntryValue.ts b/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntryValue.ts index a93bbfaa7f..b419a811df 100644 --- a/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntryValue.ts +++ b/sdk/typescript/lib/generated/models/PackageBlueprintRoyaltyEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntrySubstate.ts b/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntrySubstate.ts index 9992e2504a..adde690506 100644 --- a/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntrySubstateAllOf.ts index 6df8f051ec..a0888f6449 100644 --- a/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntryValue.ts b/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntryValue.ts index 190ac865ce..d1508caf32 100644 --- a/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntryValue.ts +++ b/sdk/typescript/lib/generated/models/PackageCodeInstrumentedCodeEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageCodeKey.ts b/sdk/typescript/lib/generated/models/PackageCodeKey.ts index 50314b6bdb..389912f678 100644 --- a/sdk/typescript/lib/generated/models/PackageCodeKey.ts +++ b/sdk/typescript/lib/generated/models/PackageCodeKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntrySubstate.ts b/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntrySubstate.ts index cbfef888d7..d5bdba08c0 100644 --- a/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntrySubstateAllOf.ts index 0a9e10f629..35f92409ad 100644 --- a/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntryValue.ts b/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntryValue.ts index e90d546c99..ec11162900 100644 --- a/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntryValue.ts +++ b/sdk/typescript/lib/generated/models/PackageCodeOriginalCodeEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntrySubstate.ts b/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntrySubstate.ts index d75df25d5a..426314bc7a 100644 --- a/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntrySubstateAllOf.ts index 0a1ab09296..0eb45a0256 100644 --- a/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntryValue.ts b/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntryValue.ts index 9841fe476a..240ea0ac48 100644 --- a/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntryValue.ts +++ b/sdk/typescript/lib/generated/models/PackageCodeVmTypeEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageExport.ts b/sdk/typescript/lib/generated/models/PackageExport.ts index d83433821c..9e4d575633 100644 --- a/sdk/typescript/lib/generated/models/PackageExport.ts +++ b/sdk/typescript/lib/generated/models/PackageExport.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorSubstate.ts b/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorSubstate.ts index c71f704f3e..12d2778db6 100644 --- a/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorSubstate.ts +++ b/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorSubstateAllOf.ts b/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorSubstateAllOf.ts index ed29ba27a5..264cb39268 100644 --- a/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorValue.ts b/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorValue.ts index 38a9268689..a2eaca7431 100644 --- a/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorValue.ts +++ b/sdk/typescript/lib/generated/models/PackageFieldRoyaltyAccumulatorValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageObjectSubstateTypeReference.ts b/sdk/typescript/lib/generated/models/PackageObjectSubstateTypeReference.ts index 8958f04761..57e4911813 100644 --- a/sdk/typescript/lib/generated/models/PackageObjectSubstateTypeReference.ts +++ b/sdk/typescript/lib/generated/models/PackageObjectSubstateTypeReference.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageObjectSubstateTypeReferenceAllOf.ts b/sdk/typescript/lib/generated/models/PackageObjectSubstateTypeReferenceAllOf.ts index 4eb41107a0..369fcca461 100644 --- a/sdk/typescript/lib/generated/models/PackageObjectSubstateTypeReferenceAllOf.ts +++ b/sdk/typescript/lib/generated/models/PackageObjectSubstateTypeReferenceAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PackageTypeReference.ts b/sdk/typescript/lib/generated/models/PackageTypeReference.ts index 7ad1ae7c8f..98e79bb08a 100644 --- a/sdk/typescript/lib/generated/models/PackageTypeReference.ts +++ b/sdk/typescript/lib/generated/models/PackageTypeReference.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedLedgerTransaction.ts b/sdk/typescript/lib/generated/models/ParsedLedgerTransaction.ts index e3f2636c92..554821549f 100644 --- a/sdk/typescript/lib/generated/models/ParsedLedgerTransaction.ts +++ b/sdk/typescript/lib/generated/models/ParsedLedgerTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedLedgerTransactionAllOf.ts b/sdk/typescript/lib/generated/models/ParsedLedgerTransactionAllOf.ts index 2df616cd26..a560d0af4a 100644 --- a/sdk/typescript/lib/generated/models/ParsedLedgerTransactionAllOf.ts +++ b/sdk/typescript/lib/generated/models/ParsedLedgerTransactionAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedLedgerTransactionIdentifiers.ts b/sdk/typescript/lib/generated/models/ParsedLedgerTransactionIdentifiers.ts index a7e575cea2..e8e196e433 100644 --- a/sdk/typescript/lib/generated/models/ParsedLedgerTransactionIdentifiers.ts +++ b/sdk/typescript/lib/generated/models/ParsedLedgerTransactionIdentifiers.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedNotarizedTransaction.ts b/sdk/typescript/lib/generated/models/ParsedNotarizedTransaction.ts index 4371d3841b..b87c7ec63c 100644 --- a/sdk/typescript/lib/generated/models/ParsedNotarizedTransaction.ts +++ b/sdk/typescript/lib/generated/models/ParsedNotarizedTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionAllOf.ts b/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionAllOf.ts index 184afc907d..cb1614594a 100644 --- a/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionAllOf.ts +++ b/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionAllOfValidationError.ts b/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionAllOfValidationError.ts index df5e86abda..d75cee933e 100644 --- a/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionAllOfValidationError.ts +++ b/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionAllOfValidationError.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionIdentifiers.ts b/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionIdentifiers.ts index c41cea273c..3d9ab6723a 100644 --- a/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionIdentifiers.ts +++ b/sdk/typescript/lib/generated/models/ParsedNotarizedTransactionIdentifiers.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntent.ts b/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntent.ts index 5906c90033..e5a295dbfd 100644 --- a/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntent.ts +++ b/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntent.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntentAllOf.ts b/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntentAllOf.ts index e4c008b8c6..4222107d39 100644 --- a/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntentAllOf.ts +++ b/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntentAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntentIdentifiers.ts b/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntentIdentifiers.ts index c4bc1d97cb..0a1afd8892 100644 --- a/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntentIdentifiers.ts +++ b/sdk/typescript/lib/generated/models/ParsedSignedTransactionIntentIdentifiers.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedTransaction.ts b/sdk/typescript/lib/generated/models/ParsedTransaction.ts index c510dd3167..04a0909205 100644 --- a/sdk/typescript/lib/generated/models/ParsedTransaction.ts +++ b/sdk/typescript/lib/generated/models/ParsedTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedTransactionBase.ts b/sdk/typescript/lib/generated/models/ParsedTransactionBase.ts index f706792e17..e050802cef 100644 --- a/sdk/typescript/lib/generated/models/ParsedTransactionBase.ts +++ b/sdk/typescript/lib/generated/models/ParsedTransactionBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedTransactionIntent.ts b/sdk/typescript/lib/generated/models/ParsedTransactionIntent.ts index 49288e4e58..6393a7380f 100644 --- a/sdk/typescript/lib/generated/models/ParsedTransactionIntent.ts +++ b/sdk/typescript/lib/generated/models/ParsedTransactionIntent.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedTransactionIntentAllOf.ts b/sdk/typescript/lib/generated/models/ParsedTransactionIntentAllOf.ts index d605900022..1ca9783cc3 100644 --- a/sdk/typescript/lib/generated/models/ParsedTransactionIntentAllOf.ts +++ b/sdk/typescript/lib/generated/models/ParsedTransactionIntentAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedTransactionIntentIdentifiers.ts b/sdk/typescript/lib/generated/models/ParsedTransactionIntentIdentifiers.ts index d28637fa7c..b5586b46b3 100644 --- a/sdk/typescript/lib/generated/models/ParsedTransactionIntentIdentifiers.ts +++ b/sdk/typescript/lib/generated/models/ParsedTransactionIntentIdentifiers.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ParsedTransactionType.ts b/sdk/typescript/lib/generated/models/ParsedTransactionType.ts index 0c9ee93467..a4774315cd 100644 --- a/sdk/typescript/lib/generated/models/ParsedTransactionType.ts +++ b/sdk/typescript/lib/generated/models/ParsedTransactionType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PartitionDescription.ts b/sdk/typescript/lib/generated/models/PartitionDescription.ts index 29faff4cb8..a7f64c4c2f 100644 --- a/sdk/typescript/lib/generated/models/PartitionDescription.ts +++ b/sdk/typescript/lib/generated/models/PartitionDescription.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PartitionDescriptionType.ts b/sdk/typescript/lib/generated/models/PartitionDescriptionType.ts index 067354fd36..d49fd3f7a6 100644 --- a/sdk/typescript/lib/generated/models/PartitionDescriptionType.ts +++ b/sdk/typescript/lib/generated/models/PartitionDescriptionType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PartitionId.ts b/sdk/typescript/lib/generated/models/PartitionId.ts index c5a648ba20..2a0df6349a 100644 --- a/sdk/typescript/lib/generated/models/PartitionId.ts +++ b/sdk/typescript/lib/generated/models/PartitionId.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PartitionKind.ts b/sdk/typescript/lib/generated/models/PartitionKind.ts index 67d4b85dda..d413af3a49 100644 --- a/sdk/typescript/lib/generated/models/PartitionKind.ts +++ b/sdk/typescript/lib/generated/models/PartitionKind.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PaymentFromVault.ts b/sdk/typescript/lib/generated/models/PaymentFromVault.ts index 8d4723c74d..b985d25dfe 100644 --- a/sdk/typescript/lib/generated/models/PaymentFromVault.ts +++ b/sdk/typescript/lib/generated/models/PaymentFromVault.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PaymentToRoyaltyRecipient.ts b/sdk/typescript/lib/generated/models/PaymentToRoyaltyRecipient.ts index 5af8a68d81..2da0b66dd0 100644 --- a/sdk/typescript/lib/generated/models/PaymentToRoyaltyRecipient.ts +++ b/sdk/typescript/lib/generated/models/PaymentToRoyaltyRecipient.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PendingOwnerStakeWithdrawal.ts b/sdk/typescript/lib/generated/models/PendingOwnerStakeWithdrawal.ts index 10c3526970..6ea2498cd2 100644 --- a/sdk/typescript/lib/generated/models/PendingOwnerStakeWithdrawal.ts +++ b/sdk/typescript/lib/generated/models/PendingOwnerStakeWithdrawal.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PlaintextMessageContent.ts b/sdk/typescript/lib/generated/models/PlaintextMessageContent.ts index c06ac045c4..b53e883f7e 100644 --- a/sdk/typescript/lib/generated/models/PlaintextMessageContent.ts +++ b/sdk/typescript/lib/generated/models/PlaintextMessageContent.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PlaintextMessageContentBase.ts b/sdk/typescript/lib/generated/models/PlaintextMessageContentBase.ts index a7540ae34b..4b2613e83a 100644 --- a/sdk/typescript/lib/generated/models/PlaintextMessageContentBase.ts +++ b/sdk/typescript/lib/generated/models/PlaintextMessageContentBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PlaintextMessageContentType.ts b/sdk/typescript/lib/generated/models/PlaintextMessageContentType.ts index 74ffe56f45..d6578de1c1 100644 --- a/sdk/typescript/lib/generated/models/PlaintextMessageContentType.ts +++ b/sdk/typescript/lib/generated/models/PlaintextMessageContentType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PlaintextTransactionMessage.ts b/sdk/typescript/lib/generated/models/PlaintextTransactionMessage.ts index 3a27ba3c5e..12c90d7959 100644 --- a/sdk/typescript/lib/generated/models/PlaintextTransactionMessage.ts +++ b/sdk/typescript/lib/generated/models/PlaintextTransactionMessage.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PlaintextTransactionMessageAllOf.ts b/sdk/typescript/lib/generated/models/PlaintextTransactionMessageAllOf.ts index 7aa6166869..e4883ad26b 100644 --- a/sdk/typescript/lib/generated/models/PlaintextTransactionMessageAllOf.ts +++ b/sdk/typescript/lib/generated/models/PlaintextTransactionMessageAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PoolVault.ts b/sdk/typescript/lib/generated/models/PoolVault.ts index a0dc8cab33..434fafab4a 100644 --- a/sdk/typescript/lib/generated/models/PoolVault.ts +++ b/sdk/typescript/lib/generated/models/PoolVault.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PresentedBadge.ts b/sdk/typescript/lib/generated/models/PresentedBadge.ts index e4ea9c1061..9a9de18293 100644 --- a/sdk/typescript/lib/generated/models/PresentedBadge.ts +++ b/sdk/typescript/lib/generated/models/PresentedBadge.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PresentedBadgeBase.ts b/sdk/typescript/lib/generated/models/PresentedBadgeBase.ts index a5291b84ca..889d726498 100644 --- a/sdk/typescript/lib/generated/models/PresentedBadgeBase.ts +++ b/sdk/typescript/lib/generated/models/PresentedBadgeBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PresentedBadgeType.ts b/sdk/typescript/lib/generated/models/PresentedBadgeType.ts index b1c10ca652..5f49664833 100644 --- a/sdk/typescript/lib/generated/models/PresentedBadgeType.ts +++ b/sdk/typescript/lib/generated/models/PresentedBadgeType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PrimaryRoleRecoveryAttempt.ts b/sdk/typescript/lib/generated/models/PrimaryRoleRecoveryAttempt.ts index 2fa7ce72f2..b579dc26a5 100644 --- a/sdk/typescript/lib/generated/models/PrimaryRoleRecoveryAttempt.ts +++ b/sdk/typescript/lib/generated/models/PrimaryRoleRecoveryAttempt.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ProofAccessRuleNode.ts b/sdk/typescript/lib/generated/models/ProofAccessRuleNode.ts index 9064b25beb..d9924d336e 100644 --- a/sdk/typescript/lib/generated/models/ProofAccessRuleNode.ts +++ b/sdk/typescript/lib/generated/models/ProofAccessRuleNode.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ProofAccessRuleNodeAllOf.ts b/sdk/typescript/lib/generated/models/ProofAccessRuleNodeAllOf.ts index 3ea7177480..0e374f2567 100644 --- a/sdk/typescript/lib/generated/models/ProofAccessRuleNodeAllOf.ts +++ b/sdk/typescript/lib/generated/models/ProofAccessRuleNodeAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ProofRule.ts b/sdk/typescript/lib/generated/models/ProofRule.ts index d4a5bb33d8..56c18dcb5f 100644 --- a/sdk/typescript/lib/generated/models/ProofRule.ts +++ b/sdk/typescript/lib/generated/models/ProofRule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ProofRuleBase.ts b/sdk/typescript/lib/generated/models/ProofRuleBase.ts index 419732eae0..471242f295 100644 --- a/sdk/typescript/lib/generated/models/ProofRuleBase.ts +++ b/sdk/typescript/lib/generated/models/ProofRuleBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ProofRuleType.ts b/sdk/typescript/lib/generated/models/ProofRuleType.ts index a5355aea2f..1c6b44dde8 100644 --- a/sdk/typescript/lib/generated/models/ProofRuleType.ts +++ b/sdk/typescript/lib/generated/models/ProofRuleType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ProposerReward.ts b/sdk/typescript/lib/generated/models/ProposerReward.ts index 3694766c80..73c6755b18 100644 --- a/sdk/typescript/lib/generated/models/ProposerReward.ts +++ b/sdk/typescript/lib/generated/models/ProposerReward.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ProtectedAccessRule.ts b/sdk/typescript/lib/generated/models/ProtectedAccessRule.ts index c2c5b1d1ca..f6e189caba 100644 --- a/sdk/typescript/lib/generated/models/ProtectedAccessRule.ts +++ b/sdk/typescript/lib/generated/models/ProtectedAccessRule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ProtectedAccessRuleAllOf.ts b/sdk/typescript/lib/generated/models/ProtectedAccessRuleAllOf.ts index 8716df7fe4..6ed4e89c1b 100644 --- a/sdk/typescript/lib/generated/models/ProtectedAccessRuleAllOf.ts +++ b/sdk/typescript/lib/generated/models/ProtectedAccessRuleAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ProtocolUpdateLedgerProofOrigin.ts b/sdk/typescript/lib/generated/models/ProtocolUpdateLedgerProofOrigin.ts index c412161d22..b8285c9acd 100644 --- a/sdk/typescript/lib/generated/models/ProtocolUpdateLedgerProofOrigin.ts +++ b/sdk/typescript/lib/generated/models/ProtocolUpdateLedgerProofOrigin.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ProtocolUpdateLedgerProofOriginAllOf.ts b/sdk/typescript/lib/generated/models/ProtocolUpdateLedgerProofOriginAllOf.ts index 8f45219bd3..f43989bf4c 100644 --- a/sdk/typescript/lib/generated/models/ProtocolUpdateLedgerProofOriginAllOf.ts +++ b/sdk/typescript/lib/generated/models/ProtocolUpdateLedgerProofOriginAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ProtocolVersionReadiness.ts b/sdk/typescript/lib/generated/models/ProtocolVersionReadiness.ts index db52d97d6a..1a5464be25 100644 --- a/sdk/typescript/lib/generated/models/ProtocolVersionReadiness.ts +++ b/sdk/typescript/lib/generated/models/ProtocolVersionReadiness.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PublicKey.ts b/sdk/typescript/lib/generated/models/PublicKey.ts index 4b79ec982f..d48b2f735d 100644 --- a/sdk/typescript/lib/generated/models/PublicKey.ts +++ b/sdk/typescript/lib/generated/models/PublicKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PublicKeyBase.ts b/sdk/typescript/lib/generated/models/PublicKeyBase.ts index 2da6e18179..e1dcd00ecc 100644 --- a/sdk/typescript/lib/generated/models/PublicKeyBase.ts +++ b/sdk/typescript/lib/generated/models/PublicKeyBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PublicKeyType.ts b/sdk/typescript/lib/generated/models/PublicKeyType.ts index 3397f7a1d9..59c5f1d8a8 100644 --- a/sdk/typescript/lib/generated/models/PublicKeyType.ts +++ b/sdk/typescript/lib/generated/models/PublicKeyType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PublicMethodAccessibility.ts b/sdk/typescript/lib/generated/models/PublicMethodAccessibility.ts index d6d4e52291..364bef8a92 100644 --- a/sdk/typescript/lib/generated/models/PublicMethodAccessibility.ts +++ b/sdk/typescript/lib/generated/models/PublicMethodAccessibility.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/PublicMethodAccessibilityAllOf.ts b/sdk/typescript/lib/generated/models/PublicMethodAccessibilityAllOf.ts index f27e66793c..e6b7fc6d13 100644 --- a/sdk/typescript/lib/generated/models/PublicMethodAccessibilityAllOf.ts +++ b/sdk/typescript/lib/generated/models/PublicMethodAccessibilityAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ReceiverInfo.ts b/sdk/typescript/lib/generated/models/ReceiverInfo.ts index 2c6ccd8c06..fa3d0a3af1 100644 --- a/sdk/typescript/lib/generated/models/ReceiverInfo.ts +++ b/sdk/typescript/lib/generated/models/ReceiverInfo.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RecoveryProposal.ts b/sdk/typescript/lib/generated/models/RecoveryProposal.ts index acb5a29b98..1e17240035 100644 --- a/sdk/typescript/lib/generated/models/RecoveryProposal.ts +++ b/sdk/typescript/lib/generated/models/RecoveryProposal.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RecoveryRoleRecoveryAttempt.ts b/sdk/typescript/lib/generated/models/RecoveryRoleRecoveryAttempt.ts index cb7ef2be76..80a9392042 100644 --- a/sdk/typescript/lib/generated/models/RecoveryRoleRecoveryAttempt.ts +++ b/sdk/typescript/lib/generated/models/RecoveryRoleRecoveryAttempt.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ReferenceType.ts b/sdk/typescript/lib/generated/models/ReferenceType.ts index e257bb860c..d263a49bae 100644 --- a/sdk/typescript/lib/generated/models/ReferenceType.ts +++ b/sdk/typescript/lib/generated/models/ReferenceType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RemoteGenericSubstitution.ts b/sdk/typescript/lib/generated/models/RemoteGenericSubstitution.ts index a27cabc37d..4f8d608c3b 100644 --- a/sdk/typescript/lib/generated/models/RemoteGenericSubstitution.ts +++ b/sdk/typescript/lib/generated/models/RemoteGenericSubstitution.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RemoteGenericSubstitutionAllOf.ts b/sdk/typescript/lib/generated/models/RemoteGenericSubstitutionAllOf.ts index 676b76f5a6..93cdd54b3b 100644 --- a/sdk/typescript/lib/generated/models/RemoteGenericSubstitutionAllOf.ts +++ b/sdk/typescript/lib/generated/models/RemoteGenericSubstitutionAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RequestedStateVersionOutOfBoundsErrorDetails.ts b/sdk/typescript/lib/generated/models/RequestedStateVersionOutOfBoundsErrorDetails.ts index e98e725cf0..4c3275f7dd 100644 --- a/sdk/typescript/lib/generated/models/RequestedStateVersionOutOfBoundsErrorDetails.ts +++ b/sdk/typescript/lib/generated/models/RequestedStateVersionOutOfBoundsErrorDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RequireProofRule.ts b/sdk/typescript/lib/generated/models/RequireProofRule.ts index 25a659a3f8..0fe18ff82a 100644 --- a/sdk/typescript/lib/generated/models/RequireProofRule.ts +++ b/sdk/typescript/lib/generated/models/RequireProofRule.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RequireProofRuleAllOf.ts b/sdk/typescript/lib/generated/models/RequireProofRuleAllOf.ts index 72de62a859..ba6a53456e 100644 --- a/sdk/typescript/lib/generated/models/RequireProofRuleAllOf.ts +++ b/sdk/typescript/lib/generated/models/RequireProofRuleAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/Requirement.ts b/sdk/typescript/lib/generated/models/Requirement.ts index 3f532d00ba..cae1b5cb16 100644 --- a/sdk/typescript/lib/generated/models/Requirement.ts +++ b/sdk/typescript/lib/generated/models/Requirement.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RequirementBase.ts b/sdk/typescript/lib/generated/models/RequirementBase.ts index ad728a306d..562a5a054d 100644 --- a/sdk/typescript/lib/generated/models/RequirementBase.ts +++ b/sdk/typescript/lib/generated/models/RequirementBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RequirementType.ts b/sdk/typescript/lib/generated/models/RequirementType.ts index be066e38c4..a911332744 100644 --- a/sdk/typescript/lib/generated/models/RequirementType.ts +++ b/sdk/typescript/lib/generated/models/RequirementType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourceAmount.ts b/sdk/typescript/lib/generated/models/ResourceAmount.ts index 5504222c43..4f7fe2b12c 100644 --- a/sdk/typescript/lib/generated/models/ResourceAmount.ts +++ b/sdk/typescript/lib/generated/models/ResourceAmount.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourceAmountBase.ts b/sdk/typescript/lib/generated/models/ResourceAmountBase.ts index d59226dfcc..47213eddbb 100644 --- a/sdk/typescript/lib/generated/models/ResourceAmountBase.ts +++ b/sdk/typescript/lib/generated/models/ResourceAmountBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourceAuthorizedDepositorBadge.ts b/sdk/typescript/lib/generated/models/ResourceAuthorizedDepositorBadge.ts index 3d6d000801..db7c6c45fd 100644 --- a/sdk/typescript/lib/generated/models/ResourceAuthorizedDepositorBadge.ts +++ b/sdk/typescript/lib/generated/models/ResourceAuthorizedDepositorBadge.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourceAuthorizedDepositorBadgeAllOf.ts b/sdk/typescript/lib/generated/models/ResourceAuthorizedDepositorBadgeAllOf.ts index 3b669ab60f..9510e59934 100644 --- a/sdk/typescript/lib/generated/models/ResourceAuthorizedDepositorBadgeAllOf.ts +++ b/sdk/typescript/lib/generated/models/ResourceAuthorizedDepositorBadgeAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourceChange.ts b/sdk/typescript/lib/generated/models/ResourceChange.ts index f036149995..f9f126051b 100644 --- a/sdk/typescript/lib/generated/models/ResourceChange.ts +++ b/sdk/typescript/lib/generated/models/ResourceChange.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourceKey.ts b/sdk/typescript/lib/generated/models/ResourceKey.ts index bf48bdc833..5fd0ea36d1 100644 --- a/sdk/typescript/lib/generated/models/ResourceKey.ts +++ b/sdk/typescript/lib/generated/models/ResourceKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourcePreference.ts b/sdk/typescript/lib/generated/models/ResourcePreference.ts index ab366018ae..0562dd02df 100644 --- a/sdk/typescript/lib/generated/models/ResourcePreference.ts +++ b/sdk/typescript/lib/generated/models/ResourcePreference.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourcePresentedBadge.ts b/sdk/typescript/lib/generated/models/ResourcePresentedBadge.ts index 1235eec3cd..f06ce83b57 100644 --- a/sdk/typescript/lib/generated/models/ResourcePresentedBadge.ts +++ b/sdk/typescript/lib/generated/models/ResourcePresentedBadge.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourcePresentedBadgeAllOf.ts b/sdk/typescript/lib/generated/models/ResourcePresentedBadgeAllOf.ts index 132f7a940c..5ac9aba9da 100644 --- a/sdk/typescript/lib/generated/models/ResourcePresentedBadgeAllOf.ts +++ b/sdk/typescript/lib/generated/models/ResourcePresentedBadgeAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourceRequirement.ts b/sdk/typescript/lib/generated/models/ResourceRequirement.ts index 7f21e38b00..5f5fd658ac 100644 --- a/sdk/typescript/lib/generated/models/ResourceRequirement.ts +++ b/sdk/typescript/lib/generated/models/ResourceRequirement.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourceRequirementAllOf.ts b/sdk/typescript/lib/generated/models/ResourceRequirementAllOf.ts index baf4d86041..f7c196b5d8 100644 --- a/sdk/typescript/lib/generated/models/ResourceRequirementAllOf.ts +++ b/sdk/typescript/lib/generated/models/ResourceRequirementAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourceSpecificDepositBehaviour.ts b/sdk/typescript/lib/generated/models/ResourceSpecificDepositBehaviour.ts index 5c2f962e5f..bfcc59e07d 100644 --- a/sdk/typescript/lib/generated/models/ResourceSpecificDepositBehaviour.ts +++ b/sdk/typescript/lib/generated/models/ResourceSpecificDepositBehaviour.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ResourceType.ts b/sdk/typescript/lib/generated/models/ResourceType.ts index 839fce770d..471000c1d4 100644 --- a/sdk/typescript/lib/generated/models/ResourceType.ts +++ b/sdk/typescript/lib/generated/models/ResourceType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstate.ts b/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstate.ts index cb1f97746c..d85d3fe51d 100644 --- a/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstate.ts +++ b/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstateAllOf.ts b/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstateAllOf.ts index 2c529f0d58..d3747a51e9 100644 --- a/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleValue.ts b/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleValue.ts index c43b214175..71991c8f06 100644 --- a/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleValue.ts +++ b/sdk/typescript/lib/generated/models/RoleAssignmentModuleFieldOwnerRoleValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntrySubstate.ts b/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntrySubstate.ts index 6ceadf571f..cc7e99d3f8 100644 --- a/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntrySubstateAllOf.ts index c58307ba9c..05f75543e3 100644 --- a/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntryValue.ts b/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntryValue.ts index 39c20c6cd4..9e163a9fcf 100644 --- a/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntryValue.ts +++ b/sdk/typescript/lib/generated/models/RoleAssignmentModuleRuleEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoleDetails.ts b/sdk/typescript/lib/generated/models/RoleDetails.ts index 194eb70f1a..0ccaea6817 100644 --- a/sdk/typescript/lib/generated/models/RoleDetails.ts +++ b/sdk/typescript/lib/generated/models/RoleDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoleProtectedMethodAccessibility.ts b/sdk/typescript/lib/generated/models/RoleProtectedMethodAccessibility.ts index cc49a60b0c..78bd5d776f 100644 --- a/sdk/typescript/lib/generated/models/RoleProtectedMethodAccessibility.ts +++ b/sdk/typescript/lib/generated/models/RoleProtectedMethodAccessibility.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoleProtectedMethodAccessibilityAllOf.ts b/sdk/typescript/lib/generated/models/RoleProtectedMethodAccessibilityAllOf.ts index a143cbae5b..fd34c53266 100644 --- a/sdk/typescript/lib/generated/models/RoleProtectedMethodAccessibilityAllOf.ts +++ b/sdk/typescript/lib/generated/models/RoleProtectedMethodAccessibilityAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoleSpecification.ts b/sdk/typescript/lib/generated/models/RoleSpecification.ts index c9a4834dc1..544cb0ae04 100644 --- a/sdk/typescript/lib/generated/models/RoleSpecification.ts +++ b/sdk/typescript/lib/generated/models/RoleSpecification.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoundUpdateLedgerTransaction.ts b/sdk/typescript/lib/generated/models/RoundUpdateLedgerTransaction.ts index c1f283ec0b..199c911b73 100644 --- a/sdk/typescript/lib/generated/models/RoundUpdateLedgerTransaction.ts +++ b/sdk/typescript/lib/generated/models/RoundUpdateLedgerTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoundUpdateLedgerTransactionAllOf.ts b/sdk/typescript/lib/generated/models/RoundUpdateLedgerTransactionAllOf.ts index 5d83cf68c0..94ef5576f6 100644 --- a/sdk/typescript/lib/generated/models/RoundUpdateLedgerTransactionAllOf.ts +++ b/sdk/typescript/lib/generated/models/RoundUpdateLedgerTransactionAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoundUpdateTransaction.ts b/sdk/typescript/lib/generated/models/RoundUpdateTransaction.ts index 0e90bc56c4..666e13a919 100644 --- a/sdk/typescript/lib/generated/models/RoundUpdateTransaction.ts +++ b/sdk/typescript/lib/generated/models/RoundUpdateTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoyaltyAmount.ts b/sdk/typescript/lib/generated/models/RoyaltyAmount.ts index 9c5aaca0cc..a0f5eb471d 100644 --- a/sdk/typescript/lib/generated/models/RoyaltyAmount.ts +++ b/sdk/typescript/lib/generated/models/RoyaltyAmount.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateSubstate.ts b/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateSubstate.ts index a0bf0f7a70..81003414b0 100644 --- a/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateSubstate.ts +++ b/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateSubstateAllOf.ts b/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateSubstateAllOf.ts index d9b461235f..97b1af9b04 100644 --- a/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateValue.ts b/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateValue.ts index 4a71eb9f4d..8398b4342f 100644 --- a/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateValue.ts +++ b/sdk/typescript/lib/generated/models/RoyaltyModuleFieldStateValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstate.ts b/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstate.ts index ea2103da96..8a3012af06 100644 --- a/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstateAllOf.ts index 925dfeef1d..779b7b9259 100644 --- a/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntryValue.ts b/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntryValue.ts index c75931ddbe..7c67d162e4 100644 --- a/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntryValue.ts +++ b/sdk/typescript/lib/generated/models/RoyaltyModuleMethodRoyaltyEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SborData.ts b/sdk/typescript/lib/generated/models/SborData.ts index f4fc80a0b2..d5f3b0fcaf 100644 --- a/sdk/typescript/lib/generated/models/SborData.ts +++ b/sdk/typescript/lib/generated/models/SborData.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SborFormatOptions.ts b/sdk/typescript/lib/generated/models/SborFormatOptions.ts index ee70583a41..d0dccc3818 100644 --- a/sdk/typescript/lib/generated/models/SborFormatOptions.ts +++ b/sdk/typescript/lib/generated/models/SborFormatOptions.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ScenariosRequest.ts b/sdk/typescript/lib/generated/models/ScenariosRequest.ts index 3c3c328edf..7b9cfcdefa 100644 --- a/sdk/typescript/lib/generated/models/ScenariosRequest.ts +++ b/sdk/typescript/lib/generated/models/ScenariosRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ScenariosResponse.ts b/sdk/typescript/lib/generated/models/ScenariosResponse.ts index 526aab70ce..da013b2e63 100644 --- a/sdk/typescript/lib/generated/models/ScenariosResponse.ts +++ b/sdk/typescript/lib/generated/models/ScenariosResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SchemaEntrySubstate.ts b/sdk/typescript/lib/generated/models/SchemaEntrySubstate.ts index ac8e3dd39c..d9e0b58db5 100644 --- a/sdk/typescript/lib/generated/models/SchemaEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/SchemaEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SchemaEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/SchemaEntrySubstateAllOf.ts index 894b627927..32e0e5cfc7 100644 --- a/sdk/typescript/lib/generated/models/SchemaEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/SchemaEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SchemaEntryValue.ts b/sdk/typescript/lib/generated/models/SchemaEntryValue.ts index 3fc1855952..36c7feebb3 100644 --- a/sdk/typescript/lib/generated/models/SchemaEntryValue.ts +++ b/sdk/typescript/lib/generated/models/SchemaEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SchemaKey.ts b/sdk/typescript/lib/generated/models/SchemaKey.ts index ac5fa84cfd..344e2d509f 100644 --- a/sdk/typescript/lib/generated/models/SchemaKey.ts +++ b/sdk/typescript/lib/generated/models/SchemaKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ScopedTypeId.ts b/sdk/typescript/lib/generated/models/ScopedTypeId.ts index fc8765bd9e..4150169a7e 100644 --- a/sdk/typescript/lib/generated/models/ScopedTypeId.ts +++ b/sdk/typescript/lib/generated/models/ScopedTypeId.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ScryptoInstant.ts b/sdk/typescript/lib/generated/models/ScryptoInstant.ts index 56f714390d..389d004626 100644 --- a/sdk/typescript/lib/generated/models/ScryptoInstant.ts +++ b/sdk/typescript/lib/generated/models/ScryptoInstant.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ScryptoSchema.ts b/sdk/typescript/lib/generated/models/ScryptoSchema.ts index 1149d27dbf..94f5c7ec51 100644 --- a/sdk/typescript/lib/generated/models/ScryptoSchema.ts +++ b/sdk/typescript/lib/generated/models/ScryptoSchema.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SignallingValidator.ts b/sdk/typescript/lib/generated/models/SignallingValidator.ts index 90feb2c58e..26bf946f1c 100644 --- a/sdk/typescript/lib/generated/models/SignallingValidator.ts +++ b/sdk/typescript/lib/generated/models/SignallingValidator.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/Signature.ts b/sdk/typescript/lib/generated/models/Signature.ts index 52a838d167..c0d922e900 100644 --- a/sdk/typescript/lib/generated/models/Signature.ts +++ b/sdk/typescript/lib/generated/models/Signature.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SignatureBase.ts b/sdk/typescript/lib/generated/models/SignatureBase.ts index 84ed903735..ff2b6766d6 100644 --- a/sdk/typescript/lib/generated/models/SignatureBase.ts +++ b/sdk/typescript/lib/generated/models/SignatureBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SignatureWithPublicKey.ts b/sdk/typescript/lib/generated/models/SignatureWithPublicKey.ts index 9eaa24ed28..719c8b2b44 100644 --- a/sdk/typescript/lib/generated/models/SignatureWithPublicKey.ts +++ b/sdk/typescript/lib/generated/models/SignatureWithPublicKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SignatureWithPublicKeyBase.ts b/sdk/typescript/lib/generated/models/SignatureWithPublicKeyBase.ts index bb3ca7c343..d1783d7a1d 100644 --- a/sdk/typescript/lib/generated/models/SignatureWithPublicKeyBase.ts +++ b/sdk/typescript/lib/generated/models/SignatureWithPublicKeyBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SignedTransactionIntent.ts b/sdk/typescript/lib/generated/models/SignedTransactionIntent.ts index a9da27c5ec..7ad36bfc76 100644 --- a/sdk/typescript/lib/generated/models/SignedTransactionIntent.ts +++ b/sdk/typescript/lib/generated/models/SignedTransactionIntent.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SignificantProtocolUpdateReadinessEntry.ts b/sdk/typescript/lib/generated/models/SignificantProtocolUpdateReadinessEntry.ts index 919bfe2896..4dc07fc302 100644 --- a/sdk/typescript/lib/generated/models/SignificantProtocolUpdateReadinessEntry.ts +++ b/sdk/typescript/lib/generated/models/SignificantProtocolUpdateReadinessEntry.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SortedIndexBlueprintCollectionSchema.ts b/sdk/typescript/lib/generated/models/SortedIndexBlueprintCollectionSchema.ts index f5ab670c8c..9a923ff58a 100644 --- a/sdk/typescript/lib/generated/models/SortedIndexBlueprintCollectionSchema.ts +++ b/sdk/typescript/lib/generated/models/SortedIndexBlueprintCollectionSchema.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SortedIndexBlueprintCollectionSchemaAllOf.ts b/sdk/typescript/lib/generated/models/SortedIndexBlueprintCollectionSchemaAllOf.ts index 047ad35ca7..fb0730a690 100644 --- a/sdk/typescript/lib/generated/models/SortedIndexBlueprintCollectionSchemaAllOf.ts +++ b/sdk/typescript/lib/generated/models/SortedIndexBlueprintCollectionSchemaAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SortedSubstateKey.ts b/sdk/typescript/lib/generated/models/SortedSubstateKey.ts index 03b4de3007..7e102b0391 100644 --- a/sdk/typescript/lib/generated/models/SortedSubstateKey.ts +++ b/sdk/typescript/lib/generated/models/SortedSubstateKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SortedSubstateKeyAllOf.ts b/sdk/typescript/lib/generated/models/SortedSubstateKeyAllOf.ts index cf02aa5d44..c5dc3ef5d5 100644 --- a/sdk/typescript/lib/generated/models/SortedSubstateKeyAllOf.ts +++ b/sdk/typescript/lib/generated/models/SortedSubstateKeyAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateAccessControllerRequest.ts b/sdk/typescript/lib/generated/models/StateAccessControllerRequest.ts index 49843b23d3..eebc90e154 100644 --- a/sdk/typescript/lib/generated/models/StateAccessControllerRequest.ts +++ b/sdk/typescript/lib/generated/models/StateAccessControllerRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateAccessControllerResponse.ts b/sdk/typescript/lib/generated/models/StateAccessControllerResponse.ts index 1fe4b8d92f..42913c9646 100644 --- a/sdk/typescript/lib/generated/models/StateAccessControllerResponse.ts +++ b/sdk/typescript/lib/generated/models/StateAccessControllerResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateAccountRequest.ts b/sdk/typescript/lib/generated/models/StateAccountRequest.ts index 37c09da76b..81d9199d43 100644 --- a/sdk/typescript/lib/generated/models/StateAccountRequest.ts +++ b/sdk/typescript/lib/generated/models/StateAccountRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateAccountResponse.ts b/sdk/typescript/lib/generated/models/StateAccountResponse.ts index 0a45e3a6a5..cc5c9ae2fc 100644 --- a/sdk/typescript/lib/generated/models/StateAccountResponse.ts +++ b/sdk/typescript/lib/generated/models/StateAccountResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateComponentDescendentNode.ts b/sdk/typescript/lib/generated/models/StateComponentDescendentNode.ts index 5011d5d4bc..74d6c8b923 100644 --- a/sdk/typescript/lib/generated/models/StateComponentDescendentNode.ts +++ b/sdk/typescript/lib/generated/models/StateComponentDescendentNode.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateComponentRequest.ts b/sdk/typescript/lib/generated/models/StateComponentRequest.ts index 0a31878314..26340c4378 100644 --- a/sdk/typescript/lib/generated/models/StateComponentRequest.ts +++ b/sdk/typescript/lib/generated/models/StateComponentRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateComponentResponse.ts b/sdk/typescript/lib/generated/models/StateComponentResponse.ts index 1e586555c2..24291a1117 100644 --- a/sdk/typescript/lib/generated/models/StateComponentResponse.ts +++ b/sdk/typescript/lib/generated/models/StateComponentResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateConsensusManagerRequest.ts b/sdk/typescript/lib/generated/models/StateConsensusManagerRequest.ts index 757c2697c1..c7f31700e7 100644 --- a/sdk/typescript/lib/generated/models/StateConsensusManagerRequest.ts +++ b/sdk/typescript/lib/generated/models/StateConsensusManagerRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateConsensusManagerResponse.ts b/sdk/typescript/lib/generated/models/StateConsensusManagerResponse.ts index 33ec66e3e1..cafff81e85 100644 --- a/sdk/typescript/lib/generated/models/StateConsensusManagerResponse.ts +++ b/sdk/typescript/lib/generated/models/StateConsensusManagerResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateFungibleResourceManager.ts b/sdk/typescript/lib/generated/models/StateFungibleResourceManager.ts index 63fea7709f..e520ca7549 100644 --- a/sdk/typescript/lib/generated/models/StateFungibleResourceManager.ts +++ b/sdk/typescript/lib/generated/models/StateFungibleResourceManager.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateFungibleResourceManagerAllOf.ts b/sdk/typescript/lib/generated/models/StateFungibleResourceManagerAllOf.ts index 921b2ca548..0d7c9b6bdf 100644 --- a/sdk/typescript/lib/generated/models/StateFungibleResourceManagerAllOf.ts +++ b/sdk/typescript/lib/generated/models/StateFungibleResourceManagerAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateNonFungibleRequest.ts b/sdk/typescript/lib/generated/models/StateNonFungibleRequest.ts index 665f3e21d6..6a895326b2 100644 --- a/sdk/typescript/lib/generated/models/StateNonFungibleRequest.ts +++ b/sdk/typescript/lib/generated/models/StateNonFungibleRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateNonFungibleResourceManager.ts b/sdk/typescript/lib/generated/models/StateNonFungibleResourceManager.ts index a509620acc..acbc20fc1c 100644 --- a/sdk/typescript/lib/generated/models/StateNonFungibleResourceManager.ts +++ b/sdk/typescript/lib/generated/models/StateNonFungibleResourceManager.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateNonFungibleResourceManagerAllOf.ts b/sdk/typescript/lib/generated/models/StateNonFungibleResourceManagerAllOf.ts index eaaf9e56ad..196cb03d85 100644 --- a/sdk/typescript/lib/generated/models/StateNonFungibleResourceManagerAllOf.ts +++ b/sdk/typescript/lib/generated/models/StateNonFungibleResourceManagerAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateNonFungibleResponse.ts b/sdk/typescript/lib/generated/models/StateNonFungibleResponse.ts index b4720f2b71..749c8f0910 100644 --- a/sdk/typescript/lib/generated/models/StateNonFungibleResponse.ts +++ b/sdk/typescript/lib/generated/models/StateNonFungibleResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StatePackageRequest.ts b/sdk/typescript/lib/generated/models/StatePackageRequest.ts index f16f4f272b..fc6bfe5473 100644 --- a/sdk/typescript/lib/generated/models/StatePackageRequest.ts +++ b/sdk/typescript/lib/generated/models/StatePackageRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StatePackageResponse.ts b/sdk/typescript/lib/generated/models/StatePackageResponse.ts index 39521cd659..89540e81ff 100644 --- a/sdk/typescript/lib/generated/models/StatePackageResponse.ts +++ b/sdk/typescript/lib/generated/models/StatePackageResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateResourceManager.ts b/sdk/typescript/lib/generated/models/StateResourceManager.ts index c44f46672f..94af86ed13 100644 --- a/sdk/typescript/lib/generated/models/StateResourceManager.ts +++ b/sdk/typescript/lib/generated/models/StateResourceManager.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateResourceManagerBase.ts b/sdk/typescript/lib/generated/models/StateResourceManagerBase.ts index 4e10d907c2..850db8258d 100644 --- a/sdk/typescript/lib/generated/models/StateResourceManagerBase.ts +++ b/sdk/typescript/lib/generated/models/StateResourceManagerBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateResourceRequest.ts b/sdk/typescript/lib/generated/models/StateResourceRequest.ts index a695cd3f06..505a4e2a6d 100644 --- a/sdk/typescript/lib/generated/models/StateResourceRequest.ts +++ b/sdk/typescript/lib/generated/models/StateResourceRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateResourceResponse.ts b/sdk/typescript/lib/generated/models/StateResourceResponse.ts index bc76e12926..645c3eb864 100644 --- a/sdk/typescript/lib/generated/models/StateResourceResponse.ts +++ b/sdk/typescript/lib/generated/models/StateResourceResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateUpdates.ts b/sdk/typescript/lib/generated/models/StateUpdates.ts index 9070abeaf8..1cb1eeb4ee 100644 --- a/sdk/typescript/lib/generated/models/StateUpdates.ts +++ b/sdk/typescript/lib/generated/models/StateUpdates.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateValidatorRequest.ts b/sdk/typescript/lib/generated/models/StateValidatorRequest.ts index 29af590f36..7662822a6c 100644 --- a/sdk/typescript/lib/generated/models/StateValidatorRequest.ts +++ b/sdk/typescript/lib/generated/models/StateValidatorRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StateValidatorResponse.ts b/sdk/typescript/lib/generated/models/StateValidatorResponse.ts index fb946cfedf..35e8472c1d 100644 --- a/sdk/typescript/lib/generated/models/StateValidatorResponse.ts +++ b/sdk/typescript/lib/generated/models/StateValidatorResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StaticBlueprintPayloadDef.ts b/sdk/typescript/lib/generated/models/StaticBlueprintPayloadDef.ts index 80314c530f..52212c2ad5 100644 --- a/sdk/typescript/lib/generated/models/StaticBlueprintPayloadDef.ts +++ b/sdk/typescript/lib/generated/models/StaticBlueprintPayloadDef.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StaticBlueprintPayloadDefAllOf.ts b/sdk/typescript/lib/generated/models/StaticBlueprintPayloadDefAllOf.ts index d45808a09c..e7e14af849 100644 --- a/sdk/typescript/lib/generated/models/StaticBlueprintPayloadDefAllOf.ts +++ b/sdk/typescript/lib/generated/models/StaticBlueprintPayloadDefAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StaticRoleDefinitionAuthTemplate.ts b/sdk/typescript/lib/generated/models/StaticRoleDefinitionAuthTemplate.ts index 7e09c892e8..1dec32d20a 100644 --- a/sdk/typescript/lib/generated/models/StaticRoleDefinitionAuthTemplate.ts +++ b/sdk/typescript/lib/generated/models/StaticRoleDefinitionAuthTemplate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsErrorDetails.ts b/sdk/typescript/lib/generated/models/StreamProofsErrorDetails.ts index 3e46414d5d..c3dda7f173 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsErrorDetails.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsErrorDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsBase.ts b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsBase.ts index 7e093d47c0..f5f13d222a 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsBase.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBounds.ts b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBounds.ts index f136c3ab61..608e410a2a 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBounds.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBounds.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBoundsAllOf.ts b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBoundsAllOf.ts index 3529cbc991..7482a56569 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBoundsAllOf.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedEpochOutOfBoundsAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBounds.ts b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBounds.ts index fbd664cc69..d9462a5d8b 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBounds.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBounds.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBoundsAllOf.ts b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBoundsAllOf.ts index 0128fd6c47..d89fc9de10 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBoundsAllOf.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsRequestedStateVersionOutOfBoundsAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsType.ts b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsType.ts index 733e19361b..0052a0468a 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsType.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsErrorDetailsType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsErrorResponse.ts b/sdk/typescript/lib/generated/models/StreamProofsErrorResponse.ts index cf6816e650..fa24d21b9c 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsErrorResponse.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsErrorResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsErrorResponseAllOf.ts b/sdk/typescript/lib/generated/models/StreamProofsErrorResponseAllOf.ts index fef29141ef..67b74b249d 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsErrorResponseAllOf.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsErrorResponseAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsFilter.ts b/sdk/typescript/lib/generated/models/StreamProofsFilter.ts index 30bff612dd..1e6e4cf66e 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsFilter.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsFilter.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsFilterAny.ts b/sdk/typescript/lib/generated/models/StreamProofsFilterAny.ts index 2ccb5e5110..af7956ed86 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsFilterAny.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsFilterAny.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsFilterAnyAllOf.ts b/sdk/typescript/lib/generated/models/StreamProofsFilterAnyAllOf.ts index 5a7b99a86a..30a1588f6b 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsFilterAnyAllOf.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsFilterAnyAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsFilterBase.ts b/sdk/typescript/lib/generated/models/StreamProofsFilterBase.ts index e79e5b21d3..91847ba0c3 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsFilterBase.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsFilterBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsFilterNewEpochs.ts b/sdk/typescript/lib/generated/models/StreamProofsFilterNewEpochs.ts index aeb657b186..9cab90901e 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsFilterNewEpochs.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsFilterNewEpochs.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsFilterNewEpochsAllOf.ts b/sdk/typescript/lib/generated/models/StreamProofsFilterNewEpochsAllOf.ts index b89b10ddad..2ca20f92d5 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsFilterNewEpochsAllOf.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsFilterNewEpochsAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateExecution.ts b/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateExecution.ts index bba2958169..3d7147b8f5 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateExecution.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateExecution.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateExecutionAllOf.ts b/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateExecutionAllOf.ts index 15d4f63f18..9ef25b0d8c 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateExecutionAllOf.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateExecutionAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateInitializations.ts b/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateInitializations.ts index ea0b5600c7..c1ddd3238c 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateInitializations.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateInitializations.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateInitializationsAllOf.ts b/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateInitializationsAllOf.ts index 03e901a92a..7832f8687a 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateInitializationsAllOf.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsFilterProtocolUpdateInitializationsAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsFilterType.ts b/sdk/typescript/lib/generated/models/StreamProofsFilterType.ts index aef7f5ef1c..66fe593631 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsFilterType.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsFilterType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsRequest.ts b/sdk/typescript/lib/generated/models/StreamProofsRequest.ts index 0490aeb010..93540527b3 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsRequest.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamProofsResponse.ts b/sdk/typescript/lib/generated/models/StreamProofsResponse.ts index c8403be515..1be88e68cf 100644 --- a/sdk/typescript/lib/generated/models/StreamProofsResponse.ts +++ b/sdk/typescript/lib/generated/models/StreamProofsResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetails.ts b/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetails.ts index b0d01b2b49..b96061c380 100644 --- a/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetails.ts +++ b/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetailsBase.ts b/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetailsBase.ts index 8968822953..17d66adceb 100644 --- a/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetailsBase.ts +++ b/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetailsBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetailsType.ts b/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetailsType.ts index 744a6a9471..7f8f8f9e45 100644 --- a/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetailsType.ts +++ b/sdk/typescript/lib/generated/models/StreamTransactionsErrorDetailsType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamTransactionsErrorResponse.ts b/sdk/typescript/lib/generated/models/StreamTransactionsErrorResponse.ts index d3d70b4500..c8ab0c17e1 100644 --- a/sdk/typescript/lib/generated/models/StreamTransactionsErrorResponse.ts +++ b/sdk/typescript/lib/generated/models/StreamTransactionsErrorResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamTransactionsErrorResponseAllOf.ts b/sdk/typescript/lib/generated/models/StreamTransactionsErrorResponseAllOf.ts index 39d1e1a576..7b1aa3ae36 100644 --- a/sdk/typescript/lib/generated/models/StreamTransactionsErrorResponseAllOf.ts +++ b/sdk/typescript/lib/generated/models/StreamTransactionsErrorResponseAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamTransactionsRequest.ts b/sdk/typescript/lib/generated/models/StreamTransactionsRequest.ts index 8da7bc8332..ff26fd0914 100644 --- a/sdk/typescript/lib/generated/models/StreamTransactionsRequest.ts +++ b/sdk/typescript/lib/generated/models/StreamTransactionsRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StreamTransactionsResponse.ts b/sdk/typescript/lib/generated/models/StreamTransactionsResponse.ts index e04fa90736..7fc6472864 100644 --- a/sdk/typescript/lib/generated/models/StreamTransactionsResponse.ts +++ b/sdk/typescript/lib/generated/models/StreamTransactionsResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StringPlaintextMessageContent.ts b/sdk/typescript/lib/generated/models/StringPlaintextMessageContent.ts index 63cbf59bb3..931ac95af2 100644 --- a/sdk/typescript/lib/generated/models/StringPlaintextMessageContent.ts +++ b/sdk/typescript/lib/generated/models/StringPlaintextMessageContent.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/StringPlaintextMessageContentAllOf.ts b/sdk/typescript/lib/generated/models/StringPlaintextMessageContentAllOf.ts index 90a43c8840..9fa634b9ce 100644 --- a/sdk/typescript/lib/generated/models/StringPlaintextMessageContentAllOf.ts +++ b/sdk/typescript/lib/generated/models/StringPlaintextMessageContentAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/Substate.ts b/sdk/typescript/lib/generated/models/Substate.ts index 9a03f0576c..b5256e989f 100644 --- a/sdk/typescript/lib/generated/models/Substate.ts +++ b/sdk/typescript/lib/generated/models/Substate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateBase.ts b/sdk/typescript/lib/generated/models/SubstateBase.ts index df9a805287..d8a728d23f 100644 --- a/sdk/typescript/lib/generated/models/SubstateBase.ts +++ b/sdk/typescript/lib/generated/models/SubstateBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateFormatOptions.ts b/sdk/typescript/lib/generated/models/SubstateFormatOptions.ts index 0e16c5b24d..53bacba219 100644 --- a/sdk/typescript/lib/generated/models/SubstateFormatOptions.ts +++ b/sdk/typescript/lib/generated/models/SubstateFormatOptions.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateId.ts b/sdk/typescript/lib/generated/models/SubstateId.ts index 2adf25ef4c..f74246928d 100644 --- a/sdk/typescript/lib/generated/models/SubstateId.ts +++ b/sdk/typescript/lib/generated/models/SubstateId.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateIdAllOf.ts b/sdk/typescript/lib/generated/models/SubstateIdAllOf.ts index c4d103740f..1538677be2 100644 --- a/sdk/typescript/lib/generated/models/SubstateIdAllOf.ts +++ b/sdk/typescript/lib/generated/models/SubstateIdAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateKey.ts b/sdk/typescript/lib/generated/models/SubstateKey.ts index d5cf5198b2..6c59a20728 100644 --- a/sdk/typescript/lib/generated/models/SubstateKey.ts +++ b/sdk/typescript/lib/generated/models/SubstateKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateKeyBase.ts b/sdk/typescript/lib/generated/models/SubstateKeyBase.ts index 6832b92c4a..39b82e39c7 100644 --- a/sdk/typescript/lib/generated/models/SubstateKeyBase.ts +++ b/sdk/typescript/lib/generated/models/SubstateKeyBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateKeyType.ts b/sdk/typescript/lib/generated/models/SubstateKeyType.ts index f6943e4192..bcf798eadb 100644 --- a/sdk/typescript/lib/generated/models/SubstateKeyType.ts +++ b/sdk/typescript/lib/generated/models/SubstateKeyType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateSystemStructure.ts b/sdk/typescript/lib/generated/models/SubstateSystemStructure.ts index ae016d521f..6995dd2539 100644 --- a/sdk/typescript/lib/generated/models/SubstateSystemStructure.ts +++ b/sdk/typescript/lib/generated/models/SubstateSystemStructure.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateSystemStructureBase.ts b/sdk/typescript/lib/generated/models/SubstateSystemStructureBase.ts index cd64dfd38d..6918d4358d 100644 --- a/sdk/typescript/lib/generated/models/SubstateSystemStructureBase.ts +++ b/sdk/typescript/lib/generated/models/SubstateSystemStructureBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateSystemStructureType.ts b/sdk/typescript/lib/generated/models/SubstateSystemStructureType.ts index 7db0e86e9b..7f0aa1af23 100644 --- a/sdk/typescript/lib/generated/models/SubstateSystemStructureType.ts +++ b/sdk/typescript/lib/generated/models/SubstateSystemStructureType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateType.ts b/sdk/typescript/lib/generated/models/SubstateType.ts index 9f96904236..0f7192b406 100644 --- a/sdk/typescript/lib/generated/models/SubstateType.ts +++ b/sdk/typescript/lib/generated/models/SubstateType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SubstateValue.ts b/sdk/typescript/lib/generated/models/SubstateValue.ts index 5a0beddcb1..57583ae5f0 100644 --- a/sdk/typescript/lib/generated/models/SubstateValue.ts +++ b/sdk/typescript/lib/generated/models/SubstateValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SystemCostingParameters.ts b/sdk/typescript/lib/generated/models/SystemCostingParameters.ts index 67cb8f90df..d5ee3fbf4b 100644 --- a/sdk/typescript/lib/generated/models/SystemCostingParameters.ts +++ b/sdk/typescript/lib/generated/models/SystemCostingParameters.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SystemFieldKind.ts b/sdk/typescript/lib/generated/models/SystemFieldKind.ts index eea71359f3..1470b276a3 100644 --- a/sdk/typescript/lib/generated/models/SystemFieldKind.ts +++ b/sdk/typescript/lib/generated/models/SystemFieldKind.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SystemFieldStructure.ts b/sdk/typescript/lib/generated/models/SystemFieldStructure.ts index 41c7e455ec..eb54bd0fc9 100644 --- a/sdk/typescript/lib/generated/models/SystemFieldStructure.ts +++ b/sdk/typescript/lib/generated/models/SystemFieldStructure.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SystemFieldStructureAllOf.ts b/sdk/typescript/lib/generated/models/SystemFieldStructureAllOf.ts index 68f33f3e53..6cd508df66 100644 --- a/sdk/typescript/lib/generated/models/SystemFieldStructureAllOf.ts +++ b/sdk/typescript/lib/generated/models/SystemFieldStructureAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SystemParameters.ts b/sdk/typescript/lib/generated/models/SystemParameters.ts index cbd7a2e39b..9b734ba3d8 100644 --- a/sdk/typescript/lib/generated/models/SystemParameters.ts +++ b/sdk/typescript/lib/generated/models/SystemParameters.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SystemSchemaStructure.ts b/sdk/typescript/lib/generated/models/SystemSchemaStructure.ts index 52f04dca1b..0a696cdfbd 100644 --- a/sdk/typescript/lib/generated/models/SystemSchemaStructure.ts +++ b/sdk/typescript/lib/generated/models/SystemSchemaStructure.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SystemSchemaStructureAllOf.ts b/sdk/typescript/lib/generated/models/SystemSchemaStructureAllOf.ts index 54cd3ba375..9bf46ff33c 100644 --- a/sdk/typescript/lib/generated/models/SystemSchemaStructureAllOf.ts +++ b/sdk/typescript/lib/generated/models/SystemSchemaStructureAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/SystemTransaction.ts b/sdk/typescript/lib/generated/models/SystemTransaction.ts index fcbdfce2ca..5520a7bebd 100644 --- a/sdk/typescript/lib/generated/models/SystemTransaction.ts +++ b/sdk/typescript/lib/generated/models/SystemTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TargetIdentifier.ts b/sdk/typescript/lib/generated/models/TargetIdentifier.ts index 655d28e363..862303a063 100644 --- a/sdk/typescript/lib/generated/models/TargetIdentifier.ts +++ b/sdk/typescript/lib/generated/models/TargetIdentifier.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TargetIdentifierBase.ts b/sdk/typescript/lib/generated/models/TargetIdentifierBase.ts index b6716a5b38..22b68f1057 100644 --- a/sdk/typescript/lib/generated/models/TargetIdentifierBase.ts +++ b/sdk/typescript/lib/generated/models/TargetIdentifierBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TargetIdentifierType.ts b/sdk/typescript/lib/generated/models/TargetIdentifierType.ts index 3b80ce85cb..631c63c530 100644 --- a/sdk/typescript/lib/generated/models/TargetIdentifierType.ts +++ b/sdk/typescript/lib/generated/models/TargetIdentifierType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TimestampedValidatorSignature.ts b/sdk/typescript/lib/generated/models/TimestampedValidatorSignature.ts index 0aeafe0e51..aa782db2a2 100644 --- a/sdk/typescript/lib/generated/models/TimestampedValidatorSignature.ts +++ b/sdk/typescript/lib/generated/models/TimestampedValidatorSignature.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionCallPreviewRequest.ts b/sdk/typescript/lib/generated/models/TransactionCallPreviewRequest.ts index 6da48dcbd4..5ffb86b1e6 100644 --- a/sdk/typescript/lib/generated/models/TransactionCallPreviewRequest.ts +++ b/sdk/typescript/lib/generated/models/TransactionCallPreviewRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionCallPreviewResponse.ts b/sdk/typescript/lib/generated/models/TransactionCallPreviewResponse.ts index fc6d609fca..9c66905cc7 100644 --- a/sdk/typescript/lib/generated/models/TransactionCallPreviewResponse.ts +++ b/sdk/typescript/lib/generated/models/TransactionCallPreviewResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionFormatOptions.ts b/sdk/typescript/lib/generated/models/TransactionFormatOptions.ts index 144b438a7f..fa3ec3ccf4 100644 --- a/sdk/typescript/lib/generated/models/TransactionFormatOptions.ts +++ b/sdk/typescript/lib/generated/models/TransactionFormatOptions.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionHeader.ts b/sdk/typescript/lib/generated/models/TransactionHeader.ts index 937f6a615f..f1413a75f8 100644 --- a/sdk/typescript/lib/generated/models/TransactionHeader.ts +++ b/sdk/typescript/lib/generated/models/TransactionHeader.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionIdKey.ts b/sdk/typescript/lib/generated/models/TransactionIdKey.ts index dde489eb74..808b0cfd4d 100644 --- a/sdk/typescript/lib/generated/models/TransactionIdKey.ts +++ b/sdk/typescript/lib/generated/models/TransactionIdKey.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionIdentifiers.ts b/sdk/typescript/lib/generated/models/TransactionIdentifiers.ts index 720384bf1c..a6aed80f41 100644 --- a/sdk/typescript/lib/generated/models/TransactionIdentifiers.ts +++ b/sdk/typescript/lib/generated/models/TransactionIdentifiers.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionIntent.ts b/sdk/typescript/lib/generated/models/TransactionIntent.ts index 51c1d887dc..7b044ce1ae 100644 --- a/sdk/typescript/lib/generated/models/TransactionIntent.ts +++ b/sdk/typescript/lib/generated/models/TransactionIntent.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionIntentStatus.ts b/sdk/typescript/lib/generated/models/TransactionIntentStatus.ts index 073cf4f247..1e39571432 100644 --- a/sdk/typescript/lib/generated/models/TransactionIntentStatus.ts +++ b/sdk/typescript/lib/generated/models/TransactionIntentStatus.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionMessage.ts b/sdk/typescript/lib/generated/models/TransactionMessage.ts index 1bacfd7643..a697d52cf2 100644 --- a/sdk/typescript/lib/generated/models/TransactionMessage.ts +++ b/sdk/typescript/lib/generated/models/TransactionMessage.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionMessageBase.ts b/sdk/typescript/lib/generated/models/TransactionMessageBase.ts index 30f40cfa0a..bdfbd1f11f 100644 --- a/sdk/typescript/lib/generated/models/TransactionMessageBase.ts +++ b/sdk/typescript/lib/generated/models/TransactionMessageBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionMessageType.ts b/sdk/typescript/lib/generated/models/TransactionMessageType.ts index 54a0a6d072..db213f6508 100644 --- a/sdk/typescript/lib/generated/models/TransactionMessageType.ts +++ b/sdk/typescript/lib/generated/models/TransactionMessageType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionParseRequest.ts b/sdk/typescript/lib/generated/models/TransactionParseRequest.ts index a725f7d233..c696f50da6 100644 --- a/sdk/typescript/lib/generated/models/TransactionParseRequest.ts +++ b/sdk/typescript/lib/generated/models/TransactionParseRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionParseResponse.ts b/sdk/typescript/lib/generated/models/TransactionParseResponse.ts index 9f262dd01a..fa939ed9fc 100644 --- a/sdk/typescript/lib/generated/models/TransactionParseResponse.ts +++ b/sdk/typescript/lib/generated/models/TransactionParseResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionPayloadDetails.ts b/sdk/typescript/lib/generated/models/TransactionPayloadDetails.ts index fc916e577f..193c4dea86 100644 --- a/sdk/typescript/lib/generated/models/TransactionPayloadDetails.ts +++ b/sdk/typescript/lib/generated/models/TransactionPayloadDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionPayloadStatus.ts b/sdk/typescript/lib/generated/models/TransactionPayloadStatus.ts index 4d3eadb294..c1c71b6259 100644 --- a/sdk/typescript/lib/generated/models/TransactionPayloadStatus.ts +++ b/sdk/typescript/lib/generated/models/TransactionPayloadStatus.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionPreviewRequest.ts b/sdk/typescript/lib/generated/models/TransactionPreviewRequest.ts index 4f593ded62..1f34af144a 100644 --- a/sdk/typescript/lib/generated/models/TransactionPreviewRequest.ts +++ b/sdk/typescript/lib/generated/models/TransactionPreviewRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). @@ -37,6 +37,12 @@ import { TransactionPreviewRequestFlagsFromJSONTyped, TransactionPreviewRequestFlagsToJSON, } from './TransactionPreviewRequestFlags'; +import type { TransactionPreviewResponseOptions } from './TransactionPreviewResponseOptions'; +import { + TransactionPreviewResponseOptionsFromJSON, + TransactionPreviewResponseOptionsFromJSONTyped, + TransactionPreviewResponseOptionsToJSON, +} from './TransactionPreviewResponseOptions'; /** * @@ -122,6 +128,12 @@ export interface TransactionPreviewRequest { * @memberof TransactionPreviewRequest */ message?: TransactionMessage; + /** + * + * @type {TransactionPreviewResponseOptions} + * @memberof TransactionPreviewRequest + */ + options?: TransactionPreviewResponseOptions; /** * * @type {TransactionPreviewRequestFlags} @@ -167,6 +179,7 @@ export function TransactionPreviewRequestFromJSONTyped(json: any, ignoreDiscrimi 'nonce': json['nonce'], 'signer_public_keys': ((json['signer_public_keys'] as Array).map(PublicKeyFromJSON)), 'message': !exists(json, 'message') ? undefined : TransactionMessageFromJSON(json['message']), + 'options': !exists(json, 'options') ? undefined : TransactionPreviewResponseOptionsFromJSON(json['options']), 'flags': TransactionPreviewRequestFlagsFromJSON(json['flags']), }; } @@ -192,6 +205,7 @@ export function TransactionPreviewRequestToJSON(value?: TransactionPreviewReques 'nonce': value.nonce, 'signer_public_keys': ((value.signer_public_keys as Array).map(PublicKeyToJSON)), 'message': TransactionMessageToJSON(value.message), + 'options': TransactionPreviewResponseOptionsToJSON(value.options), 'flags': TransactionPreviewRequestFlagsToJSON(value.flags), }; } diff --git a/sdk/typescript/lib/generated/models/TransactionPreviewRequestFlags.ts b/sdk/typescript/lib/generated/models/TransactionPreviewRequestFlags.ts index 4d12c4ed44..8d7c50c754 100644 --- a/sdk/typescript/lib/generated/models/TransactionPreviewRequestFlags.ts +++ b/sdk/typescript/lib/generated/models/TransactionPreviewRequestFlags.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionPreviewResponse.ts b/sdk/typescript/lib/generated/models/TransactionPreviewResponse.ts index 2f08a63b02..cfec10224f 100644 --- a/sdk/typescript/lib/generated/models/TransactionPreviewResponse.ts +++ b/sdk/typescript/lib/generated/models/TransactionPreviewResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). @@ -51,9 +51,16 @@ export interface TransactionPreviewResponse { */ at_ledger_state: LedgerStateSummary; /** - * The hex-sbor-encoded receipt + * 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. * @type {string} * @memberof TransactionPreviewResponse + * @deprecated */ encoded_receipt: string; /** @@ -62,6 +69,21 @@ export interface TransactionPreviewResponse { * @memberof TransactionPreviewResponse */ receipt: TransactionReceipt; + /** + * 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. + * @type {object} + * @memberof TransactionPreviewResponse + */ + radix_engine_toolkit_receipt?: object; /** * * @type {Array} @@ -103,6 +125,7 @@ export function TransactionPreviewResponseFromJSONTyped(json: any, ignoreDiscrim 'at_ledger_state': LedgerStateSummaryFromJSON(json['at_ledger_state']), 'encoded_receipt': json['encoded_receipt'], 'receipt': TransactionReceiptFromJSON(json['receipt']), + 'radix_engine_toolkit_receipt': !exists(json, 'radix_engine_toolkit_receipt') ? undefined : json['radix_engine_toolkit_receipt'], 'instruction_resource_changes': ((json['instruction_resource_changes'] as Array).map(InstructionResourceChangesFromJSON)), 'logs': ((json['logs'] as Array).map(TransactionPreviewResponseLogsInnerFromJSON)), }; @@ -120,6 +143,7 @@ export function TransactionPreviewResponseToJSON(value?: TransactionPreviewRespo 'at_ledger_state': LedgerStateSummaryToJSON(value.at_ledger_state), 'encoded_receipt': value.encoded_receipt, 'receipt': TransactionReceiptToJSON(value.receipt), + 'radix_engine_toolkit_receipt': value.radix_engine_toolkit_receipt, 'instruction_resource_changes': ((value.instruction_resource_changes as Array).map(InstructionResourceChangesToJSON)), 'logs': ((value.logs as Array).map(TransactionPreviewResponseLogsInnerToJSON)), }; diff --git a/sdk/typescript/lib/generated/models/TransactionPreviewResponseLogsInner.ts b/sdk/typescript/lib/generated/models/TransactionPreviewResponseLogsInner.ts index c12fee8777..ede33f77d3 100644 --- a/sdk/typescript/lib/generated/models/TransactionPreviewResponseLogsInner.ts +++ b/sdk/typescript/lib/generated/models/TransactionPreviewResponseLogsInner.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionPreviewResponseOptions.ts b/sdk/typescript/lib/generated/models/TransactionPreviewResponseOptions.ts new file mode 100644 index 0000000000..bd75ec27d1 --- /dev/null +++ b/sdk/typescript/lib/generated/models/TransactionPreviewResponseOptions.ts @@ -0,0 +1,67 @@ +/* tslint:disable */ +/* eslint-disable */ +/** + * 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 + * + * + * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). + * https://openapi-generator.tech + * Do not edit the class manually. + */ + +import { exists, mapValues } from '../runtime'; +/** + * A set of flags to configure the response of the transaction preview. + * @export + * @interface TransactionPreviewResponseOptions + */ +export interface TransactionPreviewResponseOptions { + /** + * 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. + * @type {boolean} + * @memberof TransactionPreviewResponseOptions + */ + radix_engine_toolkit_receipt?: boolean; +} + +/** + * Check if a given object implements the TransactionPreviewResponseOptions interface. + */ +export function instanceOfTransactionPreviewResponseOptions(value: object): boolean { + let isInstance = true; + + return isInstance; +} + +export function TransactionPreviewResponseOptionsFromJSON(json: any): TransactionPreviewResponseOptions { + return TransactionPreviewResponseOptionsFromJSONTyped(json, false); +} + +export function TransactionPreviewResponseOptionsFromJSONTyped(json: any, ignoreDiscriminator: boolean): TransactionPreviewResponseOptions { + if ((json === undefined) || (json === null)) { + return json; + } + return { + + 'radix_engine_toolkit_receipt': !exists(json, 'radix_engine_toolkit_receipt') ? undefined : json['radix_engine_toolkit_receipt'], + }; +} + +export function TransactionPreviewResponseOptionsToJSON(value?: TransactionPreviewResponseOptions | null): any { + if (value === undefined) { + return undefined; + } + if (value === null) { + return null; + } + return { + + 'radix_engine_toolkit_receipt': value.radix_engine_toolkit_receipt, + }; +} + diff --git a/sdk/typescript/lib/generated/models/TransactionReceipt.ts b/sdk/typescript/lib/generated/models/TransactionReceipt.ts index c5ef0eca64..7d1476dc7e 100644 --- a/sdk/typescript/lib/generated/models/TransactionReceipt.ts +++ b/sdk/typescript/lib/generated/models/TransactionReceipt.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionReceiptRequest.ts b/sdk/typescript/lib/generated/models/TransactionReceiptRequest.ts index 1307e3913c..80e04aca0e 100644 --- a/sdk/typescript/lib/generated/models/TransactionReceiptRequest.ts +++ b/sdk/typescript/lib/generated/models/TransactionReceiptRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionReceiptResponse.ts b/sdk/typescript/lib/generated/models/TransactionReceiptResponse.ts index 396cbadf5a..535f70bb5c 100644 --- a/sdk/typescript/lib/generated/models/TransactionReceiptResponse.ts +++ b/sdk/typescript/lib/generated/models/TransactionReceiptResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionStatus.ts b/sdk/typescript/lib/generated/models/TransactionStatus.ts index 677850cbe2..97d2ab868b 100644 --- a/sdk/typescript/lib/generated/models/TransactionStatus.ts +++ b/sdk/typescript/lib/generated/models/TransactionStatus.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionStatusRequest.ts b/sdk/typescript/lib/generated/models/TransactionStatusRequest.ts index ee63508e22..13710a3108 100644 --- a/sdk/typescript/lib/generated/models/TransactionStatusRequest.ts +++ b/sdk/typescript/lib/generated/models/TransactionStatusRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionStatusResponse.ts b/sdk/typescript/lib/generated/models/TransactionStatusResponse.ts index 9c9a79412b..a353e967d9 100644 --- a/sdk/typescript/lib/generated/models/TransactionStatusResponse.ts +++ b/sdk/typescript/lib/generated/models/TransactionStatusResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetails.ts b/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetails.ts index 0bdb99b59d..8f81c5562c 100644 --- a/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetails.ts +++ b/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetailsBase.ts b/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetailsBase.ts index 49e53cad36..e8a7925434 100644 --- a/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetailsBase.ts +++ b/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetailsBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetailsType.ts b/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetailsType.ts index 60047ce4a0..8a1e19782d 100644 --- a/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetailsType.ts +++ b/sdk/typescript/lib/generated/models/TransactionSubmitErrorDetailsType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionSubmitErrorResponse.ts b/sdk/typescript/lib/generated/models/TransactionSubmitErrorResponse.ts index f06f90de0e..cfece26af0 100644 --- a/sdk/typescript/lib/generated/models/TransactionSubmitErrorResponse.ts +++ b/sdk/typescript/lib/generated/models/TransactionSubmitErrorResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionSubmitErrorResponseAllOf.ts b/sdk/typescript/lib/generated/models/TransactionSubmitErrorResponseAllOf.ts index b8f7c5e359..51dfac7c7f 100644 --- a/sdk/typescript/lib/generated/models/TransactionSubmitErrorResponseAllOf.ts +++ b/sdk/typescript/lib/generated/models/TransactionSubmitErrorResponseAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionSubmitIntentAlreadyCommitted.ts b/sdk/typescript/lib/generated/models/TransactionSubmitIntentAlreadyCommitted.ts index 0218ee8f00..946cc6fcce 100644 --- a/sdk/typescript/lib/generated/models/TransactionSubmitIntentAlreadyCommitted.ts +++ b/sdk/typescript/lib/generated/models/TransactionSubmitIntentAlreadyCommitted.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionSubmitPriorityThresholdNotMetErrorDetails.ts b/sdk/typescript/lib/generated/models/TransactionSubmitPriorityThresholdNotMetErrorDetails.ts index 2c45abe1ac..6aee845fe0 100644 --- a/sdk/typescript/lib/generated/models/TransactionSubmitPriorityThresholdNotMetErrorDetails.ts +++ b/sdk/typescript/lib/generated/models/TransactionSubmitPriorityThresholdNotMetErrorDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionSubmitRejectedErrorDetails.ts b/sdk/typescript/lib/generated/models/TransactionSubmitRejectedErrorDetails.ts index d4c1e623fb..564156eb53 100644 --- a/sdk/typescript/lib/generated/models/TransactionSubmitRejectedErrorDetails.ts +++ b/sdk/typescript/lib/generated/models/TransactionSubmitRejectedErrorDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionSubmitRequest.ts b/sdk/typescript/lib/generated/models/TransactionSubmitRequest.ts index a6fc319a39..603ad85d0a 100644 --- a/sdk/typescript/lib/generated/models/TransactionSubmitRequest.ts +++ b/sdk/typescript/lib/generated/models/TransactionSubmitRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionSubmitResponse.ts b/sdk/typescript/lib/generated/models/TransactionSubmitResponse.ts index 529104142a..e4c4cccdac 100644 --- a/sdk/typescript/lib/generated/models/TransactionSubmitResponse.ts +++ b/sdk/typescript/lib/generated/models/TransactionSubmitResponse.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntrySubstate.ts b/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntrySubstate.ts index c3e0bfe659..706e672827 100644 --- a/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntrySubstate.ts +++ b/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntrySubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntrySubstateAllOf.ts b/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntrySubstateAllOf.ts index 80abe63d29..f3a1c4e13e 100644 --- a/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntrySubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntrySubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntryValue.ts b/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntryValue.ts index 311d833ede..1e98221f30 100644 --- a/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntryValue.ts +++ b/sdk/typescript/lib/generated/models/TransactionTrackerCollectionEntryValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateSubstate.ts b/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateSubstate.ts index fbf8fd1341..3f4cca4605 100644 --- a/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateSubstate.ts +++ b/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateSubstateAllOf.ts b/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateSubstateAllOf.ts index 13389ef202..6f352b3c27 100644 --- a/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateValue.ts b/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateValue.ts index 7af1113cad..506c115cc3 100644 --- a/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateValue.ts +++ b/sdk/typescript/lib/generated/models/TransactionTrackerFieldStateValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TransactionTrackerTransactionStatus.ts b/sdk/typescript/lib/generated/models/TransactionTrackerTransactionStatus.ts index fe7443226b..aa0265d16d 100644 --- a/sdk/typescript/lib/generated/models/TransactionTrackerTransactionStatus.ts +++ b/sdk/typescript/lib/generated/models/TransactionTrackerTransactionStatus.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateSubstate.ts b/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateSubstate.ts index a40acd2114..93222a5698 100644 --- a/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateSubstate.ts +++ b/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateSubstateAllOf.ts b/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateSubstateAllOf.ts index b5a58dfd11..00b881e304 100644 --- a/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateValue.ts b/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateValue.ts index 8165b9d79a..bfef8802e9 100644 --- a/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateValue.ts +++ b/sdk/typescript/lib/generated/models/TwoResourcePoolFieldStateValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TypeInfoDetails.ts b/sdk/typescript/lib/generated/models/TypeInfoDetails.ts index d5a16e13d3..7ca8a93228 100644 --- a/sdk/typescript/lib/generated/models/TypeInfoDetails.ts +++ b/sdk/typescript/lib/generated/models/TypeInfoDetails.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TypeInfoDetailsBase.ts b/sdk/typescript/lib/generated/models/TypeInfoDetailsBase.ts index 0389ed4671..a157fd686b 100644 --- a/sdk/typescript/lib/generated/models/TypeInfoDetailsBase.ts +++ b/sdk/typescript/lib/generated/models/TypeInfoDetailsBase.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoSubstate.ts b/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoSubstate.ts index 50a6054a5e..a9a5988aa7 100644 --- a/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoSubstate.ts +++ b/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoSubstateAllOf.ts b/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoSubstateAllOf.ts index 8373b01566..892362cfc4 100644 --- a/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoValue.ts b/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoValue.ts index 7758bd4951..2196c9b28f 100644 --- a/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoValue.ts +++ b/sdk/typescript/lib/generated/models/TypeInfoModuleFieldTypeInfoValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/TypeInfoType.ts b/sdk/typescript/lib/generated/models/TypeInfoType.ts index b42e572630..9aca2679aa 100644 --- a/sdk/typescript/lib/generated/models/TypeInfoType.ts +++ b/sdk/typescript/lib/generated/models/TypeInfoType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/UpdatedSubstate.ts b/sdk/typescript/lib/generated/models/UpdatedSubstate.ts index 00f137bc22..67a0f3dc16 100644 --- a/sdk/typescript/lib/generated/models/UpdatedSubstate.ts +++ b/sdk/typescript/lib/generated/models/UpdatedSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/UserLedgerTransaction.ts b/sdk/typescript/lib/generated/models/UserLedgerTransaction.ts index 1aa1b4853a..7ac28efa80 100644 --- a/sdk/typescript/lib/generated/models/UserLedgerTransaction.ts +++ b/sdk/typescript/lib/generated/models/UserLedgerTransaction.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/UserLedgerTransactionAllOf.ts b/sdk/typescript/lib/generated/models/UserLedgerTransactionAllOf.ts index 7830800344..9f7d80b052 100644 --- a/sdk/typescript/lib/generated/models/UserLedgerTransactionAllOf.ts +++ b/sdk/typescript/lib/generated/models/UserLedgerTransactionAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ValidatorFeeChangeRequest.ts b/sdk/typescript/lib/generated/models/ValidatorFeeChangeRequest.ts index ad37735797..c754cc5f63 100644 --- a/sdk/typescript/lib/generated/models/ValidatorFeeChangeRequest.ts +++ b/sdk/typescript/lib/generated/models/ValidatorFeeChangeRequest.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstate.ts b/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstate.ts index f5a9c681ae..e029e15103 100644 --- a/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstate.ts +++ b/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstateAllOf.ts b/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstateAllOf.ts index c9bfdd164e..2e5b093973 100644 --- a/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalValue.ts b/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalValue.ts index 331c01ff98..52880c6e09 100644 --- a/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalValue.ts +++ b/sdk/typescript/lib/generated/models/ValidatorFieldProtocolUpdateReadinessSignalValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ValidatorFieldStateSubstate.ts b/sdk/typescript/lib/generated/models/ValidatorFieldStateSubstate.ts index 6b21340e16..b63fa4fb28 100644 --- a/sdk/typescript/lib/generated/models/ValidatorFieldStateSubstate.ts +++ b/sdk/typescript/lib/generated/models/ValidatorFieldStateSubstate.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ValidatorFieldStateSubstateAllOf.ts b/sdk/typescript/lib/generated/models/ValidatorFieldStateSubstateAllOf.ts index 3c3ed7ffd6..b3508eff91 100644 --- a/sdk/typescript/lib/generated/models/ValidatorFieldStateSubstateAllOf.ts +++ b/sdk/typescript/lib/generated/models/ValidatorFieldStateSubstateAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/ValidatorFieldStateValue.ts b/sdk/typescript/lib/generated/models/ValidatorFieldStateValue.ts index 16c22de091..e067d88e10 100644 --- a/sdk/typescript/lib/generated/models/ValidatorFieldStateValue.ts +++ b/sdk/typescript/lib/generated/models/ValidatorFieldStateValue.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/VaultBalance.ts b/sdk/typescript/lib/generated/models/VaultBalance.ts index dd71a6ab96..912bd73921 100644 --- a/sdk/typescript/lib/generated/models/VaultBalance.ts +++ b/sdk/typescript/lib/generated/models/VaultBalance.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/VersionLedgerStateSelector.ts b/sdk/typescript/lib/generated/models/VersionLedgerStateSelector.ts index 081a055bdd..9ffd373e66 100644 --- a/sdk/typescript/lib/generated/models/VersionLedgerStateSelector.ts +++ b/sdk/typescript/lib/generated/models/VersionLedgerStateSelector.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/VersionLedgerStateSelectorAllOf.ts b/sdk/typescript/lib/generated/models/VersionLedgerStateSelectorAllOf.ts index 29443f27bd..c4ef1fb8cd 100644 --- a/sdk/typescript/lib/generated/models/VersionLedgerStateSelectorAllOf.ts +++ b/sdk/typescript/lib/generated/models/VersionLedgerStateSelectorAllOf.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/VirtualLazyLoadSchema.ts b/sdk/typescript/lib/generated/models/VirtualLazyLoadSchema.ts index d5edd6a16a..a6b7138953 100644 --- a/sdk/typescript/lib/generated/models/VirtualLazyLoadSchema.ts +++ b/sdk/typescript/lib/generated/models/VirtualLazyLoadSchema.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/VmType.ts b/sdk/typescript/lib/generated/models/VmType.ts index 4fe15449ab..1ce384d363 100644 --- a/sdk/typescript/lib/generated/models/VmType.ts +++ b/sdk/typescript/lib/generated/models/VmType.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/sdk/typescript/lib/generated/models/index.ts b/sdk/typescript/lib/generated/models/index.ts index 08e111f9bb..7d8d1d9c31 100644 --- a/sdk/typescript/lib/generated/models/index.ts +++ b/sdk/typescript/lib/generated/models/index.ts @@ -628,6 +628,7 @@ export * from './TransactionPreviewRequest'; export * from './TransactionPreviewRequestFlags'; export * from './TransactionPreviewResponse'; export * from './TransactionPreviewResponseLogsInner'; +export * from './TransactionPreviewResponseOptions'; export * from './TransactionReceipt'; export * from './TransactionReceiptRequest'; export * from './TransactionReceiptResponse'; diff --git a/sdk/typescript/lib/generated/runtime.ts b/sdk/typescript/lib/generated/runtime.ts index 25380740f4..20228184f0 100644 --- a/sdk/typescript/lib/generated/runtime.ts +++ b/sdk/typescript/lib/generated/runtime.ts @@ -1,10 +1,10 @@ /* tslint:disable */ /* eslint-disable */ /** - * Radix Core API - Babylon (Bottlenose) + * 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.1 + * The version of the OpenAPI document: v1.2.3 * * * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech). diff --git a/testnet-node/docker-compose.yml b/testnet-node/docker-compose.yml index 6fe529c2a7..c31017b893 100644 --- a/testnet-node/docker-compose.yml +++ b/testnet-node/docker-compose.yml @@ -4,7 +4,7 @@ services: core: container_name: radixdlt-stokenet-node #### Chose to either uncomment "image" or "build" to either pull the image from dockerhub or build locally from source - image: radixdlt/babylon-node:v1.3.0 + image: radixdlt/babylon-node:v1.2.3 # build: # context: .. # dockerfile: Dockerfile