From 0257b486e226eefe6d2e8631be5eb03394122d90 Mon Sep 17 00:00:00 2001 From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com> Date: Thu, 23 Apr 2026 15:39:49 -0400 Subject: [PATCH 1/5] docs: expand horizon streaming guide --- .../api-reference/structure/streaming.mdx | 64 ++++++++++++++----- 1 file changed, 48 insertions(+), 16 deletions(-) diff --git a/docs/data/apis/horizon/api-reference/structure/streaming.mdx b/docs/data/apis/horizon/api-reference/structure/streaming.mdx index ad13f8ca33..00b71930f5 100644 --- a/docs/data/apis/horizon/api-reference/structure/streaming.mdx +++ b/docs/data/apis/horizon/api-reference/structure/streaming.mdx @@ -1,27 +1,59 @@ --- +id: streaming title: Streaming +description: Use Horizon streaming mode to receive new ledger data in near real time. Streaming requests use the same endpoint parameters as normal requests and can begin from the earliest known record or from a supplied cursor. +sidebar_label: Streaming sidebar_position: 30 --- -import { MethodTable } from "@site/src/components/MethodTable"; +Horizon supports streaming for endpoints that expose newly ingested ledger data over time. -Horizon provides a streaming mechanism for receiving events in near real time. Instead of repeatedly sending requests to Horizon for batch updates, a connection is established between a client and Horizon with updates to an endpoint response streaming as new ledgers close and updates occur. +Instead of repeatedly polling an endpoint for new results, you can keep a connection open and receive updates as new ledgers close and matching records become available. This is useful when you want to react to ledger activity without repeatedly issuing requests that return no new data. -This reduces requests that return no data and allows near instantaneous updates client-side. +## How Streaming Works -All attributes for the endpoints that allow streaming are the same as regular responses. A caller can initiate streaming by setting ‘Accept: text/event-stream’ in the HTTP header when making the request. +Streaming mode uses the same endpoint and query parameters as the standard request for that resource. - +To open a stream, send the request with the `Accept: text/event-stream` header. -| | -| ----------------------------------------------------- | -| [Ledgers](../resources/ledgers/README.mdx) | -| [Transactions](../resources/transactions/README.mdx) | -| [Operations](../resources/operations/README.mdx) | -| [Payments](../resources/payments/README.mdx) | -| [Effects](../resources/effects/README.mdx) | -| [Accounts](../resources/accounts/README.mdx) | -| [Trades](../resources/trades/README.mdx) | -| [Order Books](../aggregations/order-books/README.mdx) | +For example: - +```bash +curl -N \ + -H "Accept: text/event-stream" \ + "/operations?cursor=now" +``` + +## Cursor Behavior + +Cursor behavior is the main difference between a standard request and a streaming request. + +- If no `cursor` is provided, Horizon starts at the earliest known matching record and streams forward from there. +- If a `cursor` is provided, Horizon starts from that cursor. +- If `cursor=now` is provided, Horizon starts from your request time and streams only newly created matching records. + +Use `cursor=now` when you want to watch for new activity only. Use a specific cursor when you want to resume from a known point. + +## When To Use Streaming + +Streaming is a good fit when you want to: + +- watch for new transactions, operations, payments, or effects +- follow new ledger closures +- track changing order book data +- keep an application UI updated as new matching records arrive + +## Supported Endpoints + +Many Horizon resource endpoints support streaming. Check the individual endpoint reference to confirm whether a specific endpoint can be called in streaming mode. + +Common examples include endpoints for: + +- [Ledgers](../resources/ledgers/README.mdx) +- [Transactions](../resources/transactions/README.mdx) +- [Operations](../resources/operations/README.mdx) +- [Payments](../resources/payments/README.mdx) +- [Effects](../resources/effects/README.mdx) +- [Accounts](../resources/accounts/README.mdx) +- [Trades](../resources/trades/README.mdx) +- [Order Books](../aggregations/order-books/README.mdx) From 5926222d0b2861f392b838011c3b079b652976dd Mon Sep 17 00:00:00 2001 From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com> Date: Sun, 26 Apr 2026 07:36:46 -0400 Subject: [PATCH 2/5] init --- config/theme/footer.ts | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/config/theme/footer.ts b/config/theme/footer.ts index e90605c4ab..a56d6cb386 100644 --- a/config/theme/footer.ts +++ b/config/theme/footer.ts @@ -5,7 +5,7 @@ const resources = { items: [ { label: "Developer Blog", - href: "https://www.stellar.org/developers-blog", + href: "https://stellar.org/developers-blog", }, { label: "Stellar Quest", From be12501d6df8a6a82f83b604a90f18aeacacde2b Mon Sep 17 00:00:00 2001 From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com> Date: Sun, 26 Apr 2026 07:37:23 -0400 Subject: [PATCH 3/5] Remove www from stellar.org links --- README.md | 2 +- docs/build/apps/application-design-considerations.mdx | 2 +- .../anchor-integration/sep24.mdx | 2 +- docs/data/apis/horizon/README.mdx | 2 +- docs/data/apis/horizon/admin-guide/overview.mdx | 2 +- .../horizon-specific/transaction-failed.mdx | 2 +- .../apis/horizon/api-reference/errors/response.mdx | 2 +- .../api-reference/errors/result-codes/operations.mdx | 2 +- .../api-reference/errors/result-codes/transactions.mdx | 2 +- docs/data/apis/rpc/providers.mdx | 2 +- docs/learn/fundamentals/lumens.mdx | 10 +++++----- docs/networks/software-versions.mdx | 6 +++--- .../sep-guide/sep24/setting-up-production-server.mdx | 2 +- docs/validators/admin-guide/configuring.mdx | 2 +- i18n/en/docusaurus-theme-classic/footer.json | 2 +- .../admin-guide/sep24/setting-up-production-server.mdx | 2 +- .../sep-guide/sep24/setting-up-production-server.mdx | 2 +- .../build/apps/application-design-considerations.mdx | 2 +- .../anchor-integration/sep24.mdx | 2 +- .../build/guides/basics/send-and-receive-payments.mdx | 2 +- .../current/data/apis/api-providers.mdx | 2 +- .../current/data/apis/horizon/README.mdx | 2 +- .../current/data/apis/horizon/admin-guide/overview.mdx | 2 +- .../horizon-specific/transaction-failed.mdx | 2 +- .../apis/horizon/api-reference/errors/response.mdx | 2 +- .../api-reference/errors/result-codes/operations.mdx | 2 +- .../api-reference/errors/result-codes/transactions.mdx | 2 +- .../current/data/apis/rpc/providers.mdx | 2 +- .../encyclopedia/network-configuration/inflation.mdx | 2 +- .../current/learn/fundamentals/lumens.mdx | 10 +++++----- .../current/networks/software-versions.mdx | 6 +++--- .../sep-guide/sep24/setting-up-production-server.mdx | 2 +- .../current/validators/admin-guide/configuring.mdx | 2 +- i18n/es/docusaurus-theme-classic/footer.json | 2 +- openapi/horizon/bundled.yml | 2 +- openapi/horizon/main.yml | 2 +- static/llms.txt | 2 +- 37 files changed, 49 insertions(+), 49 deletions(-) diff --git a/README.md b/README.md index feac42185b..d01eee6351 100644 --- a/README.md +++ b/README.md @@ -247,7 +247,7 @@ export const CODE_LANGS = { }; ``` -**Remember that this is a community; we build together! 🫱🏻‍🫲🏽 Our code of conduct is [here](https://www.stellar.org/community/code-of-conduct) and our Privacy Policy is [here](https://www.stellar.org/privacy-policy).** +**Remember that this is a community; we build together! 🫱🏻‍🫲🏽 Our code of conduct is [here](https://stellar.org/community/code-of-conduct) and our Privacy Policy is [here](https://stellar.org/privacy-policy).** [docs]: https://developers.stellar.org/docs [stellar]: https://stellar.org diff --git a/docs/build/apps/application-design-considerations.mdx b/docs/build/apps/application-design-considerations.mdx index 8ee0355321..d13bdb423b 100644 --- a/docs/build/apps/application-design-considerations.mdx +++ b/docs/build/apps/application-design-considerations.mdx @@ -43,7 +43,7 @@ There are several apps and services that specialize in adding additional securit Even though wallets can operate client-side, they deal with a user’s secret keys, which give direct access to their account, and to any value they hold. That’s why it’s essential to require all web traffic to flow over strong TLS methods. Even when developing locally, use a non-signed localhost certificate to develop secure habits from the very beginning. Stellar is a powerful money-moving software — don’t skimp on security. -For more information, check out our guide to [securing web-based products](https://www.stellar.org/developers/guides/walkthroughs/securing-web-projects.html). +For more information, check out our guide to [securing web-based products](https://stellar.org/developers/guides/walkthroughs/securing-web-projects.html). ## Wallet services diff --git a/docs/build/apps/example-application-tutorial/anchor-integration/sep24.mdx b/docs/build/apps/example-application-tutorial/anchor-integration/sep24.mdx index cfc84aff3f..63327d9c11 100644 --- a/docs/build/apps/example-application-tutorial/anchor-integration/sep24.mdx +++ b/docs/build/apps/example-application-tutorial/anchor-integration/sep24.mdx @@ -276,4 +276,4 @@ In a withdrawal transaction, BasicPay will also build and present to the user a [sep-10 authentication]: ./sep10.mdx [sep-6 section]: ./sep6.mdx -[this section of the sep-24 specification]: https://www.stellar.org/protocol/sep-24#adding-parameters-to-the-url +[this section of the sep-24 specification]: https://stellar.org/protocol/sep-24#adding-parameters-to-the-url diff --git a/docs/data/apis/horizon/README.mdx b/docs/data/apis/horizon/README.mdx index 4675889855..a69d1e5fd8 100644 --- a/docs/data/apis/horizon/README.mdx +++ b/docs/data/apis/horizon/README.mdx @@ -17,7 +17,7 @@ Horizon provides an HTTP API to data in the Stellar network. It ingests and re-s Horizon can be accessed via cURL, a browser, or one of the [Stellar SDKs](../../../tools/sdks/README.mdx). To reduce the complexity of your project, we recommend you use an SDK instead of making direct API calls. -This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://www.stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). +This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). Before we begin, it's worth reiterating the sentiment echoed in the [Core Node](../../../validators/README.mdx) documentation: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance). diff --git a/docs/data/apis/horizon/admin-guide/overview.mdx b/docs/data/apis/horizon/admin-guide/overview.mdx index afe932c9a0..4841d20ad1 100644 --- a/docs/data/apis/horizon/admin-guide/overview.mdx +++ b/docs/data/apis/horizon/admin-guide/overview.mdx @@ -5,7 +5,7 @@ sidebar_position: 0 Horizon is a central component of the Stellar platform: it provides an HTTP API to data in the Stellar network. It ingests and re-serves the data produced by the Stellar network in a form that is easier to consume by the average application relative to the performance-oriented data representations used by Stellar Core. -This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://www.stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/internal/docs/DEVELOPING.md). +This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/internal/docs/DEVELOPING.md). Before we begin, it's worth reiterating the sentiment echoed in the [Run a Core Node](../../../../validators/README.mdx) guide: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance). diff --git a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx index f31621b5b2..0064c131a9 100644 --- a/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx +++ b/docs/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx @@ -20,7 +20,7 @@ In almost every case, this error indicates that the transaction submitted in the "type": "https://stellar.org/horizon-errors/transaction_failed", "title": "Transaction Failed", "status": 400, - "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://www.stellar.org/developers/guides/concepts/list-of-operations.html", + "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://stellar.org/developers/guides/concepts/list-of-operations.html", "extras": { "envelope_xdr": "AAAAAgAAAADdfhHDs4Vaug6p8Oxb1QRjNRdJt3pYKKBVhFHrEgd9QAAAAAoAEi4YAAAAAwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACwAAAAAAAAAAAAAAAAAAAAESB31AAAAAQFhc/liVXbLk3NtB2BtweFJ064JdDIfrTSrqKMhb1oIRK+0PSyvjzZTkRCJmQY3bHNXYNuepa2TF7aBdibrb1gI=", "result_codes": { diff --git a/docs/data/apis/horizon/api-reference/errors/response.mdx b/docs/data/apis/horizon/api-reference/errors/response.mdx index 6d1668b09e..3dc655813c 100644 --- a/docs/data/apis/horizon/api-reference/errors/response.mdx +++ b/docs/data/apis/horizon/api-reference/errors/response.mdx @@ -47,7 +47,7 @@ When any error occurs, Horizon responds with a JSON document with the below attr "type": "https://stellar.org/horizon-errors/transaction_failed", "title": "Transaction Failed", "status": 400, - "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html", + "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://stellar.org/developers/learn/concepts/list-of-operations.html", "extras": { "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAADAAAAAAAAAAAAAAABAAAAAQAAAACuSL9OciKkFztj4d3zuadl20HHObu+7qJenBxHPrMayQAAAAUAAAABAAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAtJBKRwAAABA1N0iqDAgqS6+3RIZGoNB9OXrY3wd/nLruXYi+eiTt4jn94fLVLwAw6jJCaK+qxStwO7c4kP6u5k0RPbuYC55CT6zGskAAABAiUGCNCS4pGlfcRmi82kbralzcFlTQAFzLyfUrYGn3RtQ4p/7TUwAqIanVoWGfEqzIJo64ZT+mYtJ72BfI+FiDg==", "result_codes": { diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/operations.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/operations.mdx index 6caab52f9e..2c94bddf28 100644 --- a/docs/data/apis/horizon/api-reference/errors/result-codes/operations.mdx +++ b/docs/data/apis/horizon/api-reference/errors/result-codes/operations.mdx @@ -38,7 +38,7 @@ These are Result Codes that communicate success (200) or failure (400) at the op "type": "https://stellar.org/horizon-errors/transaction_failed", "title": "Transaction Failed", "status": 400, - "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html", + "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://stellar.org/developers/learn/concepts/list-of-operations.html", "extras": { "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAADAAAAAAAAAAAAAAABAAAAAQAAAACuSL9OciKkFztj4d3zuadl20HHObu+7qJenBxHPrMayQAAAAUAAAABAAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAtJBKRwAAABA1N0iqDAgqS6+3RIZGoNB9OXrY3wd/nLruXYi+eiTt4jn94fLVLwAw6jJCaK+qxStwO7c4kP6u5k0RPbuYC55CT6zGskAAABAiUGCNCS4pGlfcRmi82kbralzcFlTQAFzLyfUrYGn3RtQ4p/7TUwAqIanVoWGfEqzIJo64ZT+mYtJ72BfI+FiDg==", "result_codes": { diff --git a/docs/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx b/docs/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx index 7adb63d757..04cd189bfd 100644 --- a/docs/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx +++ b/docs/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx @@ -56,7 +56,7 @@ These are Result Codes that communicate success (200) or failure (400) at the tr "type": "https://stellar.org/horizon-errors/transaction_failed", "title": "Transaction Failed", "status": 400, - "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html", + "detail": "The transaction failed when submitted to the Stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://stellar.org/developers/learn/concepts/list-of-operations.html", "extras": { "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAArki/TnIipBc7Y+Hd87mnZdtBxzm7vu6iXpwcRz6zGskAAAAAAAAAAAAHoSAAAAAAAAAAAdJBKRwAAABANWeKuRYFmBm1lrMQqMvhbSouwL270SnxcTtv1XI4Y+uVe4yw4Jq7/43EoxwLbRh/pC3V4WfOZRzDqwsTyEztAA==", "result_codes": { diff --git a/docs/data/apis/rpc/providers.mdx b/docs/data/apis/rpc/providers.mdx index c98ce99fa0..78443e151c 100644 --- a/docs/data/apis/rpc/providers.mdx +++ b/docs/data/apis/rpc/providers.mdx @@ -40,7 +40,7 @@ _The "Dedicated Nodes" column represents providers who host full nodes as a serv | [sorobanrpc.com](https://sorobanrpc.com/) | Mainnet | RPC: `https://mainnet.sorobanrpc.com` | | [Nodies](https://nodies.org) | Testnet | RPC: `https://stellar-soroban-testnet-public.nodies.app` | | | Mainnet | RPC: `https://stellar-soroban-public.nodies.app` | -| [SDF](http://www.stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org` | +| [SDF](http://stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org` | | | Testnet | RPC: `https://soroban-testnet.stellar.org` | | [OnFinality](https://onfinality.io/networks/stellar) | Mainnet | RPC: `https://stellar.api.onfinality.io/public` | | [Lightsail Network - Quasar](https://quasar.lightsail.network/) | Mainnet | RPC `https://rpc.lightsail.network/` | diff --git a/docs/learn/fundamentals/lumens.mdx b/docs/learn/fundamentals/lumens.mdx index 669ba49b08..922038716e 100644 --- a/docs/learn/fundamentals/lumens.mdx +++ b/docs/learn/fundamentals/lumens.mdx @@ -9,7 +9,7 @@ sidebar_position: 30 Lumens (XLM) are the native currency of the Stellar network. The lumen is the only token that doesn’t require an issuer or trustline. They are used to pay all transaction [fees](#transaction-fees), fund [rent](./fees-resource-limits-metering.mdx#resource-fee), and to cover [minimum balance requirements](stellar-data-structures/accounts.mdx#base-reserves-and-subentries) on the network. -To read up on the basics of lumens, head over to our Stellar Learn site: [Stellar Learn: Lumens](https://www.stellar.org/lumens) +To read up on the basics of lumens, head over to our Stellar Learn site: [Stellar Learn: Lumens](https://stellar.org/lumens) ## Transaction fees @@ -66,7 +66,7 @@ As of May 28th, 2024, the Dashboard API shows: "feePool": "4690537.8610771", "sdfMandate": "20761482987.7713113", "circulatingSupply": "28976033204.7768698", - "_details": "https://www.stellar.org/developers/guides/lumen-supply-metrics.html" + "_details": "https://stellar.org/developers/guides/lumen-supply-metrics.html" } ``` @@ -82,15 +82,15 @@ Adding this number to the Original Supply, you get the total lumens that have ev **burnedLumens** These are all the lumens sent to accounts with no signers, meaning the funds are inaccessible and have been removed forever from Stellar’s lumen supply. -While any address with no signers is counted here, the vast majority of the lumens in this sum are in a single locked address. On November 4, 2019, SDF [reduced](https://www.stellar.org/blog/sdfs-next-steps/) its lumen holdings to better reflect its mission and the growth of the Stellar ecosystem. To do so, the Foundation sent 55,442,095,285.7418 lumens to [GALA…LUTO](https://stellar.expert/explorer/public/account/GALAXYVOIDAOPZTDLHILAJQKCVVFMD4IKLXLSZV5YHO7VY74IWZILUTO). +While any address with no signers is counted here, the vast majority of the lumens in this sum are in a single locked address. On November 4, 2019, SDF [reduced](https://stellar.org/blog/sdfs-next-steps/) its lumen holdings to better reflect its mission and the growth of the Stellar ecosystem. To do so, the Foundation sent 55,442,095,285.7418 lumens to [GALA…LUTO](https://stellar.expert/explorer/public/account/GALAXYVOIDAOPZTDLHILAJQKCVVFMD4IKLXLSZV5YHO7VY74IWZILUTO). **totalSupply** The Total Supply is the number of lumens now in existence: 50,001,803,905.97172. The Total Supply includes four major categories of lumens, which the API treats in detail. -**upgradeReserve** The Upgrade Reserve is a special address that’s neither circulating nor a part of SDF’s mandate. When Stellar [changed its consensus algorithm](https://www.stellar.org/blog/upgraded-network-is-here/) in 2015 and relaunched the network these lumens were set aside, to be claimed, one-for-one, by holders of the old network tokens. The [Upgrade Reserve account](https://stellar.expert/explorer/public/account/GBEZOC5U4TVH7ZY5N3FLYHTCZSI6VFGTULG7PBITLF5ZEBPJXFT46YZM) is essentially an escrow, and we don’t expect many claimants to come and pull those lumens into the circulating supply at this point. +**upgradeReserve** The Upgrade Reserve is a special address that’s neither circulating nor a part of SDF’s mandate. When Stellar [changed its consensus algorithm](https://stellar.org/blog/upgraded-network-is-here/) in 2015 and relaunched the network these lumens were set aside, to be claimed, one-for-one, by holders of the old network tokens. The [Upgrade Reserve account](https://stellar.expert/explorer/public/account/GBEZOC5U4TVH7ZY5N3FLYHTCZSI6VFGTULG7PBITLF5ZEBPJXFT46YZM) is essentially an escrow, and we don’t expect many claimants to come and pull those lumens into the circulating supply at this point. **feePool** The Fee Pool is where network fees collect. The lumens do not belong to any particular account. No one has access to the fee pool, so these lumens are non-circulating. Network validators could theoretically vote for a protocol change that would affect the fee pool, so we include it in the total supply. Stellar’s transaction fees are extremely low so the fee pool grows very slowly. The Fee Pool is tracked by the protocol itself, and the current number is visible on the [List All Ledgers](../../data/apis/horizon/api-reference/list-all-ledgers.api.mdx) Horizon API endpoint as `_embedded.records.fee_pool`. See all Stellar Mainnet Horizon data providers [here](../../data/apis/horizon/providers.mdx). -**sdfMandate** The SDF Mandate is described in detail [here](https://www.stellar.org/foundation/mandate). The Foundation was funded by lumens generated at Stellar’s inception; all of those lumens will eventually be spent or distributed to enhance and promote Stellar. Here is a complete list of the addresses currently associated with the SDF Mandate: +**sdfMandate** The SDF Mandate is described in detail [here](https://stellar.org/foundation/mandate). The Foundation was funded by lumens generated at Stellar’s inception; all of those lumens will eventually be spent or distributed to enhance and promote Stellar. Here is a complete list of the addresses currently associated with the SDF Mandate: - [Direct Development, Available Funds](https://stellar.expert/explorer/public/account/GB6NVEN5HSUBKMYCE5ZOWSK5K23TBWRUQLZY3KNMXUZ3AQ2ESC4MY4AQ) - [Jan 1 2021 Escrow](https://stellar.expert/explorer/public/account/GBA6XT7YBQOERXT656T74LYUVJ6MEIOC5EUETGAQNHQHEPUFPKCW5GYM) diff --git a/docs/networks/software-versions.mdx b/docs/networks/software-versions.mdx index c4576342f2..c3759bdfe1 100644 --- a/docs/networks/software-versions.mdx +++ b/docs/networks/software-versions.mdx @@ -1992,15 +1992,15 @@ See https://github.com/stellar/soroban-cli/releases v0.2.0, v0.2.1 for more deta ### Changelog -See https://www.stellar.org/blog/soroban-a-new-smart-contract-standard. +See https://stellar.org/blog/soroban-a-new-smart-contract-standard. ## Preview 2 (September 13th, 2022) -See https://www.stellar.org/developers-blog/soroban-preview-release-2. +See https://stellar.org/developers-blog/soroban-preview-release-2. ## Preview 1 (August 1st, 2022) -See https://www.stellar.org/blog/project-jump-cannon-soroban-preview-release. +See https://stellar.org/blog/project-jump-cannon-soroban-preview-release. [@waldmatias]: https://github.com/waldmatias [@willemneal]: https://github.com/willemneal diff --git a/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx b/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx index 149e81566c..9b632ee592 100644 --- a/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx +++ b/docs/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx @@ -119,4 +119,4 @@ Having a group of beta testers is a great way to check if there are any edge cas All Anchor user interactions are done through a Wallet, so it's vital for Anchors to be connected to Wallets that have a good market penetration in the region where the business is most focused. Connecting to Wallets is a simple process, since both ends of that integration are already compliant with SEPs. -Stellar.org maintains a [list of wallets](https://www.stellar.org/ecosystem/projects), many of which currently support SEP-24 Sending them a message with more information on an asset and an issuer account is a great way to start getting some real users to the Anchor. +Stellar.org maintains a [list of wallets](https://stellar.org/ecosystem/projects), many of which currently support SEP-24 Sending them a message with more information on an asset and an issuer account is a great way to start getting some real users to the Anchor. diff --git a/docs/validators/admin-guide/configuring.mdx b/docs/validators/admin-guide/configuring.mdx index d85008fe43..ca3cfa640f 100644 --- a/docs/validators/admin-guide/configuring.mdx +++ b/docs/validators/admin-guide/configuring.mdx @@ -291,5 +291,5 @@ Let there be 3 `HIGH` quality organizations, 2 `MEDIUM` quality organizations, a [`HOME_DOMAINS` array]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L671 [`VALIDATORS` array]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L688 [SEP-20]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md -[how Stellar approaches quorums]: https://www.stellar.org/developers-blog/why-quorums-matter-and-how-stellar-approaches-them +[how Stellar approaches quorums]: https://stellar.org/developers-blog/why-quorums-matter-and-how-stellar-approaches-them [public network config for a Full Validator]: https://github.com/stellar/packages/blob/master/docs/examples/pubnet-validator-full/stellar-core.cfg diff --git a/i18n/en/docusaurus-theme-classic/footer.json b/i18n/en/docusaurus-theme-classic/footer.json index b7831aa765..e1c1cfa0a5 100644 --- a/i18n/en/docusaurus-theme-classic/footer.json +++ b/i18n/en/docusaurus-theme-classic/footer.json @@ -17,7 +17,7 @@ }, "link.item.label.Developer Blog": { "message": "Developer Blog", - "description": "The label of footer link with label=Developer Blog linking to https://www.stellar.org/developers-blog" + "description": "The label of footer link with label=Developer Blog linking to https://stellar.org/developers-blog" }, "link.item.label.Stellar Quest": { "message": "Stellar Quest", diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/setting-up-production-server.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/setting-up-production-server.mdx index 1a3757b649..5d4b08a4fd 100644 --- a/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/setting-up-production-server.mdx +++ b/i18n/es/docusaurus-plugin-content-docs-ap/current/admin-guide/sep24/setting-up-production-server.mdx @@ -121,4 +121,4 @@ Tener un grupo de beta testers es una excelente manera de verificar si hay algú Todas las interacciones de los usuarios de Anchor se realizan a través de una billetera, así que es vital que los Anchors estén conectados a billeteras que tengan una buena penetración de mercado en la región donde el negocio esté más enfocado. Conectar a billeteras es un proceso simple, ya que ambos extremos de esa integración ya son compatibles con SEPs. -Stellar.org mantiene una [lista de billeteras](https://www.stellar.org/ecosystem/projects), muchas de las cuales actualmente soportan SEP-24. Enviarles un mensaje con más información sobre un activo y una cuenta emisor es una excelente manera de comenzar a obtener algunos usuarios reales para el Anchor. +Stellar.org mantiene una [lista de billeteras](https://stellar.org/ecosystem/projects), muchas de las cuales actualmente soportan SEP-24. Enviarles un mensaje con más información sobre un activo y una cuenta emisor es una excelente manera de comenzar a obtener algunos usuarios reales para el Anchor. diff --git a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/setting-up-production-server.mdx b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/setting-up-production-server.mdx index 07ff30c3ca..cb586db9c4 100644 --- a/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/setting-up-production-server.mdx +++ b/i18n/es/docusaurus-plugin-content-docs-ap/current/sep-guide/sep24/setting-up-production-server.mdx @@ -121,4 +121,4 @@ Tener un grupo de testers beta es una excelente manera de detectar casos extremo Todas las interacciones de usuarios con Anchor se realizan a través de una Wallet, por lo que es vital que los Anchors estén conectados a Wallets con buena penetración de mercado en la región donde el negocio se concentra. Conectarse a Wallets es un proceso simple, ya que ambos extremos de esa integración ya cumplen con los SEPs. -Stellar.org mantiene una [lista de wallets](https://www.stellar.org/ecosystem/projects), muchas de las cuales actualmente soportan SEP-24. Enviarles información sobre un activo y una cuenta emisor es una excelente forma de empezar a conseguir usuarios reales para el Anchor. +Stellar.org mantiene una [lista de wallets](https://stellar.org/ecosystem/projects), muchas de las cuales actualmente soportan SEP-24. Enviarles información sobre un activo y una cuenta emisor es una excelente forma de empezar a conseguir usuarios reales para el Anchor. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/application-design-considerations.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/application-design-considerations.mdx index 11ee8d63d8..effeb29351 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/application-design-considerations.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/application-design-considerations.mdx @@ -43,7 +43,7 @@ Hay varias aplicaciones y servicios que se especializan en agregar capas de segu A pesar de que las billeteras pueden operar del lado del cliente, manejan las claves secretas de un usuario, que dan acceso directo a su cuenta y a cualquier valor que posean. Por eso, es esencial requerir que todo el tráfico web fluya a través de métodos TLS sólidos. Incluso cuando desarrollas localmente, utiliza un certificado de localhost no firmado para desarrollar hábitos seguros desde el principio. Stellar es un potente software para mover dinero; no escatimes en seguridad. -Para más información, consulta nuestra guía sobre [asegurar productos basados en la web](https://www.stellar.org/developers/guides/walkthroughs/securing-web-projects.html). +Para más información, consulta nuestra guía sobre [asegurar productos basados en la web](https://stellar.org/developers/guides/walkthroughs/securing-web-projects.html). ## Servicios de billetera diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep24.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep24.mdx index 8f45bb6a92..3fd76abf8b 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep24.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/build/apps/example-application-tutorial/anchor-integration/sep24.mdx @@ -276,4 +276,4 @@ En una transacción de retirada de fondos, BasicPay también desarrollará y pre [autenticación sep-10]: ./sep10.mdx [sección sep-6]: ./sep6.mdx -[esta sección de la especificación sep-24]: https://www.stellar.org/protocol/sep-24#adding-parameters-to-the-url +[esta sección de la especificación sep-24]: https://stellar.org/protocol/sep-24#adding-parameters-to-the-url diff --git a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/send-and-receive-payments.mdx b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/send-and-receive-payments.mdx index 61f36d383a..20123dc5bc 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/send-and-receive-payments.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/build/guides/basics/send-and-receive-payments.mdx @@ -537,7 +537,7 @@ transaction = TransactionBuilder( -4. Agrega la operación de pago a la cuenta. Ten en cuenta que necesitas especificar el tipo de activo que estás enviando: la moneda de la red Stellar es el [lumen](https://www.stellar.org/lumens), pero puedes enviar cualquier activo emitido en la red. Cubriré el envío de activos no lumen [abajo](#transacting-in-other-currencies). Por ahora, sin embargo, nos mantendremos en lumens, que se llaman activos “nativos” en el SDK: +4. Agrega la operación de pago a la cuenta. Ten en cuenta que necesitas especificar el tipo de activo que estás enviando: la moneda de la red Stellar es el [lumen](https://stellar.org/lumens), pero puedes enviar cualquier activo emitido en la red. Cubriré el envío de activos no lumen [abajo](#transacting-in-other-currencies). Por ahora, sin embargo, nos mantendremos en lumens, que se llaman activos “nativos” en el SDK: diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/api-providers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/api-providers.mdx index 9a800b8226..c3923d1c4a 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/api-providers.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/api-providers.mdx @@ -50,7 +50,7 @@ Estos proveedores permiten acceder a la red Futurenet, Testnet y Mainnet. | [sorobanrpc.com](https://sorobanrpc.com/) | Mainnet | RPC: `https://mainnet.sorobanrpc.com` | | [Nodies](https://nodies.org) | Testnet | RPC: `https://stellar-soroban-testnet-public.nodies.app` | | | Mainnet | RPC: `https://stellar-soroban-public.nodies.app` | -| [SDF](http://www.stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org`
Horizon: `https://horizon-futurenet.stellar.org` | +| [SDF](http://stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org`
Horizon: `https://horizon-futurenet.stellar.org` | | | Testnet | RPC: `https://soroban-testnet.stellar.org`
Horizon: `https://horizon-testnet.stellar.org` | | [LOBSTR](https://lobstr.co) | Mainnet | Horizon: `https://horizon.stellar.lobstr.co` | | [OnFinality](https://onfinality.io/networks/stellar) | Mainnet | RPC: `https://stellar.api.onfinality.io/public` | diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/README.mdx index 2de4d2300a..9f8ed8ad9b 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/README.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/README.mdx @@ -17,7 +17,7 @@ Horizon proporciona una API HTTP para datos en la red Stellar. Recoge y vuelve a Horizon se puede acceder a través de cURL, un navegador o uno de los [Stellar SDKs](../../../tools/sdks/README.mdx). Para reducir la complejidad de tu proyecto, te recomendamos usar un SDK en vez de hacer llamadas directas a la API. -Esta guía describe cómo administrar una instancia de producción de Horizon (consulta el [Blog de los desarrolladores](https://www.stellar.org/developers-blog/a-new-sun-on-the-horizon) para algunos antecedentes sobre las mejoras de rendimiento y arquitectónicas de esta importante actualización de versión). Para obtener información sobre el desarrollo en el código base de Horizon, consulta la [Guía de Desarrollo](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). +Esta guía describe cómo administrar una instancia de producción de Horizon (consulta el [Blog de los desarrolladores](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) para algunos antecedentes sobre las mejoras de rendimiento y arquitectónicas de esta importante actualización de versión). Para obtener información sobre el desarrollo en el código base de Horizon, consulta la [Guía de Desarrollo](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). Antes de comenzar, vale la pena reiterar el sentimiento expresado en la documentación de [Core Node](../../../validators/README.mdx): **no respaldamos correr Horizon respaldado por una instancia de Stellar Core independiente**, y especialmente no por un Stellar Core _validante_. Estas son dos preocupaciones separadas, y desacoplarlas es importante tanto para la confiabilidad como para el rendimiento. Horizon en cambio gestiona su propia versión reducida de Stellar Core optimizada para su propio subconjunto de necesidades (nos referiremos a esto como una instancia de "Core cautivo"). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/overview.mdx index ab5befc0a2..9fa7db2029 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/overview.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/overview.mdx @@ -5,7 +5,7 @@ sidebar_position: 0 Horizon es un componente central de la plataforma Stellar: proporciona una API HTTP para los datos en la red Stellar. Ingiere y vuelve a servir los datos producidos por la red Stellar en una forma que es más fácil de consumir por la aplicación promedio en comparación con las representaciones de datos orientadas al rendimiento utilizadas por Stellar Core. -Esta guía describe cómo administrar una instancia de Horizon en producción (consulta el [Blog de Desarrolladores](https://www.stellar.org/developers-blog/a-new-sun-on-the-horizon) para obtener información de fondo sobre las mejoras de rendimiento y arquitectónicas de este importante aumento de versión). Para obtener información sobre cómo desarrollar en la base de código de Horizon, consulta la [Guía de Desarrollo](https://github.com/stellar/stellar-horizon/blob/main/internal/docs/DEVELOPING.md). +Esta guía describe cómo administrar una instancia de Horizon en producción (consulta el [Blog de Desarrolladores](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) para obtener información de fondo sobre las mejoras de rendimiento y arquitectónicas de este importante aumento de versión). Para obtener información sobre cómo desarrollar en la base de código de Horizon, consulta la [Guía de Desarrollo](https://github.com/stellar/stellar-horizon/blob/main/internal/docs/DEVELOPING.md). Antes de comenzar, vale la pena reiterar el sentimiento expuesto en la guía [Ejecutar un Nodo Core](../../../../validators/README.mdx): **no recomendamos ejecutar Horizon respaldado por una instancia independiente de Stellar Core**, y especialmente no por un Stellar Core _validador_. Estas son dos preocupaciones separadas, y desacoplarlas es importante tanto para la confiabilidad como para el rendimiento. Horizon, en cambio, gestiona su propia versión reducida de Stellar Core optimizada para su propio subconjunto de necesidades (nos referiremos a esto como una instancia de "Captive Core"). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx index 60b788f28d..2f92179af8 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx @@ -20,7 +20,7 @@ En casi todos los casos, este error indica que la transacción enviada en la sol "type": "https://stellar.org/horizon-errors/transaction_failed", "title": "Transaction Failed", "status": 400, - "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://www.stellar.org/developers/guides/concepts/list-of-operations.html", + "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://stellar.org/developers/guides/concepts/list-of-operations.html", "extras": { "envelope_xdr": "AAAAAgAAAADdfhHDs4Vaug6p8Oxb1QRjNRdJt3pYKKBVhFHrEgd9QAAAAAoAEi4YAAAAAwAAAAEAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAEAAAAAAAAACwAAAAAAAAAAAAAAAAAAAAESB31AAAAAQFhc/liVXbLk3NtB2BtweFJ064JdDIfrTSrqKMhb1oIRK+0PSyvjzZTkRCJmQY3bHNXYNuepa2TF7aBdibrb1gI=", "result_codes": { diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/response.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/response.mdx index e03543eea9..69ad081fe5 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/response.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/response.mdx @@ -47,7 +47,7 @@ Cuando ocurre un error, Horizon responde con un documento JSON que contiene los "type": "https://stellar.org/horizon-errors/transaction_failed", "title": "Transaction Failed", "status": 400, - "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html", + "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://stellar.org/developers/learn/concepts/list-of-operations.html", "extras": { "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAADAAAAAAAAAAAAAAABAAAAAQAAAACuSL9OciKkFztj4d3zuadl20HHObu+7qJenBxHPrMayQAAAAUAAAABAAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAtJBKRwAAABA1N0iqDAgqS6+3RIZGoNB9OXrY3wd/nLruXYi+eiTt4jn94fLVLwAw6jJCaK+qxStwO7c4kP6u5k0RPbuYC55CT6zGskAAABAiUGCNCS4pGlfcRmi82kbralzcFlTQAFzLyfUrYGn3RtQ4p/7TUwAqIanVoWGfEqzIJo64ZT+mYtJ72BfI+FiDg==", "result_codes": { diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operations.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operations.mdx index 0856c4a6d3..3d80ac1ecc 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operations.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/operations.mdx @@ -38,7 +38,7 @@ Estos son los Códigos de Resultado que comunican éxito (200) o fracaso (400) a "type": "https://stellar.org/horizon-errors/transaction_failed", "title": "Transaction Failed", "status": 400, - "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html", + "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://stellar.org/developers/learn/concepts/list-of-operations.html", "extras": { "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAADAAAAAAAAAAAAAAABAAAAAQAAAACuSL9OciKkFztj4d3zuadl20HHObu+7qJenBxHPrMayQAAAAUAAAABAAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAtJBKRwAAABA1N0iqDAgqS6+3RIZGoNB9OXrY3wd/nLruXYi+eiTt4jn94fLVLwAw6jJCaK+qxStwO7c4kP6u5k0RPbuYC55CT6zGskAAABAiUGCNCS4pGlfcRmi82kbralzcFlTQAFzLyfUrYGn3RtQ4p/7TUwAqIanVoWGfEqzIJo64ZT+mYtJ72BfI+FiDg==", "result_codes": { diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx index 468966e6f0..37da87e8cf 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/api-reference/errors/result-codes/transactions.mdx @@ -56,7 +56,7 @@ Estos son los Códigos de Resultado que comunican éxito (200) o fracaso (400) a "type": "https://stellar.org/horizon-errors/transaction_failed", "title": "Transaction Failed", "status": 400, - "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://www.stellar.org/developers/learn/concepts/list-of-operations.html", + "detail": "The transaction failed when submitted to the stellar network. The `extras.result_codes` field on this response contains further details. Descriptions of each code can be found at: https://stellar.org/developers/learn/concepts/list-of-operations.html", "extras": { "envelope_xdr": "AAAAANPRjCD1iCti3hovsrrz6aSAjmp263grVr6+mI3SQSkcAAAAZAAPRLgAAAAAAAAAAAAAAAAAAAABAAAAAAAAAAEAAAAArki/TnIipBc7Y+Hd87mnZdtBxzm7vu6iXpwcRz6zGskAAAAAAAAAAAAHoSAAAAAAAAAAAdJBKRwAAABANWeKuRYFmBm1lrMQqMvhbSouwL270SnxcTtv1XI4Y+uVe4yw4Jq7/43EoxwLbRh/pC3V4WfOZRzDqwsTyEztAA==", "result_codes": { diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/providers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/providers.mdx index ef277693db..c06e0b39f6 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/providers.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/providers.mdx @@ -39,7 +39,7 @@ _La columna "Dedicated Nodes" representa proveedores que alojan nodos completos | [sorobanrpc.com](https://sorobanrpc.com/) | Mainnet | RPC: `https://mainnet.sorobanrpc.com` | | [Nodies](https://nodies.org) | Testnet | RPC: `https://stellar-soroban-testnet-public.nodies.app` | | | Mainnet | RPC: `https://stellar-soroban-public.nodies.app` | -| [SDF](http://www.stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org` | +| [SDF](http://stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org` | | [OnFinality](https://onfinality.io/networks/stellar) | Mainnet | RPC: `https://stellar.api.onfinality.io/public` | | [Lightsail Network - Quasar](https://quasar.lightsail.network/) | Mainnet | RPC `https://rpc.lightsail.network/` | | | Mainnet | RPC de archivo completo: `https://archive-rpc.lightsail.network/` | diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/inflation.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/inflation.mdx index 7f4c3eefea..3080258209 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/inflation.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/learn/encyclopedia/network-configuration/inflation.mdx @@ -10,4 +10,4 @@ Antes del Protocolo 12, Stellar tenía un mecanismo de inflación integrado dise A medida que la red evolucionó y creció, se hizo evidente que la inflación no estaba funcionando como se pretendía: los titulares de cuentas no establecieron su destino de inflación o se unieron a grupos de inflación para reclamar la inflación ellos mismos. Los costos operativos asociados con los pagos de inflación continuaron aumentando, por lo que se propuso CAP-26, un cambio de protocolo para deshabilitar la inflación, que fue [implementado](https://github.com/stellar/stellar-core/releases/tag/v12.0.0), votado por los validadores y finalmente adoptado como parte de una actualización de la red. -Para obtener más información, puedes leer nuestro blog aquí: [Nuestra Propuesta para Deshabilitar la Inflación](https://www.stellar.org/blog/our-proposal-to-disable-inflation) +Para obtener más información, puedes leer nuestro blog aquí: [Nuestra Propuesta para Deshabilitar la Inflación](https://stellar.org/blog/our-proposal-to-disable-inflation) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/lumens.mdx b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/lumens.mdx index f0674d1b80..d1871df819 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/lumens.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/learn/fundamentals/lumens.mdx @@ -9,7 +9,7 @@ sidebar_position: 30 Lumens (XLM) son la moneda nativa de la red Stellar. El lumen es el único token que no requiere un emisor o línea de fideicomiso. Se utilizan para pagar todas las [tarifas](#transaction-fees) de transacción, financiar [alquiler](./fees-resource-limits-metering.mdx#resource-fee), y para cumplir con los [requisitos de saldo mínimo](stellar-data-structures/accounts.mdx#base-reserves-and-subentries) en la red. -Para informarte sobre lo básico de los lumens, visita nuestro sitio Stellar Learn: [Stellar Learn: Lumens](https://www.stellar.org/lumens) +Para informarte sobre lo básico de los lumens, visita nuestro sitio Stellar Learn: [Stellar Learn: Lumens](https://stellar.org/lumens) ## Tarifas de transacción @@ -66,7 +66,7 @@ A partir del 28 de mayo de 2024, la API del Dashboard muestra: "feePool": "4690537.8610771", "sdfMandate": "20761482987.7713113", "circulatingSupply": "28976033204.7768698", - "_details": "https://www.stellar.org/developers/guides/lumen-supply-metrics.html" + "_details": "https://stellar.org/developers/guides/lumen-supply-metrics.html" } ``` @@ -82,15 +82,15 @@ Sumando este número al Suministro Original, obtienes el total de lumens que han **burnedLumens** Estos son todos los lumens enviados a cuentas sin firmantes, lo que significa que los fondos son inaccesibles y han sido eliminados para siempre del suministro de lumens de Stellar. -Mientras que cualquier dirección sin firmantes se cuenta aquí, la gran mayoría de los lumens en esta suma están en una única dirección bloqueada. El 4 de noviembre de 2019, el SDF [redujo](https://www.stellar.org/blog/sdfs-next-steps/) sus tenencias de lumens para reflejar mejor su misión y el crecimiento del ecosistema Stellar. Para hacerlo, la Fundación envió 55.442.095.285,7418 lumens a [GALA…LUTO](https://stellar.expert/explorer/public/account/GALAXYVOIDAOPZTDLHILAJQKCVVFMD4IKLXLSZV5YHO7VY74IWZILUTO). +Mientras que cualquier dirección sin firmantes se cuenta aquí, la gran mayoría de los lumens en esta suma están en una única dirección bloqueada. El 4 de noviembre de 2019, el SDF [redujo](https://stellar.org/blog/sdfs-next-steps/) sus tenencias de lumens para reflejar mejor su misión y el crecimiento del ecosistema Stellar. Para hacerlo, la Fundación envió 55.442.095.285,7418 lumens a [GALA…LUTO](https://stellar.expert/explorer/public/account/GALAXYVOIDAOPZTDLHILAJQKCVVFMD4IKLXLSZV5YHO7VY74IWZILUTO). **totalSupply** El Suministro Total es el número de lumens que ahora existen: 50.001.803.905,97172. El Suministro Total incluye cuatro categorías principales de lumens, que la API trata en detalle. -**upgradeReserve** La Reserva de Mejora es una dirección especial que no está en circulación ni forma parte del mandato del SDF. Cuando Stellar [cambió su algoritmo de consenso](https://www.stellar.org/blog/upgraded-network-is-here/) en 2015 y relanzó la red, estos lumens se reservaron, para ser reclamados, uno a uno, por los titulares de los tokens de la red anterior. La [cuenta de Reserva de Mejora](https://stellar.expert/explorer/public/account/GBEZOC5U4TVH7ZY5N3FLYHTCZSI6VFGTULG7PBITLF5ZEBPJXFT46YZM) es esencialmente un depósito en garantía, y no esperamos que muchos reclamantes vengan a retirar esos lumens para que entren en circulación en este momento. +**upgradeReserve** La Reserva de Mejora es una dirección especial que no está en circulación ni forma parte del mandato del SDF. Cuando Stellar [cambió su algoritmo de consenso](https://stellar.org/blog/upgraded-network-is-here/) en 2015 y relanzó la red, estos lumens se reservaron, para ser reclamados, uno a uno, por los titulares de los tokens de la red anterior. La [cuenta de Reserva de Mejora](https://stellar.expert/explorer/public/account/GBEZOC5U4TVH7ZY5N3FLYHTCZSI6VFGTULG7PBITLF5ZEBPJXFT46YZM) es esencialmente un depósito en garantía, y no esperamos que muchos reclamantes vengan a retirar esos lumens para que entren en circulación en este momento. **feePool** El Fondo de Tarifas es donde se acumulan las tarifas de la red. Los lumens no pertenecen a ninguna cuenta particular. Nadie tiene acceso al fondo de tarifas, por lo que estos lumens no están en circulación. Teóricamente, los validadores de la red podrían votar por un cambio de protocolo que afectara el fondo de tarifas, por lo que lo incluimos en el suministro total. Las tarifas de transacción de Stellar son extremadamente bajas, por lo que el fondo de tarifas crece muy lentamente. El Pool de Tarifas es rastreado por el protocolo mismo, y el número actual es visible en el [Listar Todos los Ledgers](../../data/apis/horizon/api-reference/list-all-ledgers.api.mdx) en el punto final de la API Horizon como `_embedded.records.fee_pool`. Consulta todos los proveedores de datos de Horizon de Stellar Mainnet [aquí](../../data/apis/horizon/providers.mdx). -**sdfMandate** El Mandato del SDF se describe en detalle [aquí](https://www.stellar.org/foundation/mandate). La Fundación fue financiada por lumens generados en el inicio de Stellar; todos esos lumens serán eventualmente gastados o distribuidos para mejorar y promover Stellar. Aquí tienes una lista completa de las direcciones actualmente asociadas con el Mandato del SDF: +**sdfMandate** El Mandato del SDF se describe en detalle [aquí](https://stellar.org/foundation/mandate). La Fundación fue financiada por lumens generados en el inicio de Stellar; todos esos lumens serán eventualmente gastados o distribuidos para mejorar y promover Stellar. Aquí tienes una lista completa de las direcciones actualmente asociadas con el Mandato del SDF: - [Desarrollo Directo, Fondos Disponibles](https://stellar.expert/explorer/public/account/GB6NVEN5HSUBKMYCE5ZOWSK5K23TBWRUQLZY3KNMXUZ3AQ2ESC4MY4AQ) - [Escrow del 1 de enero de 2021](https://stellar.expert/explorer/public/account/GBA6XT7YBQOERXT656T74LYUVJ6MEIOC5EUETGAQNHQHEPUFPKCW5GYM) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/networks/software-versions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/networks/software-versions.mdx index 0b946e6a88..738358656c 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/networks/software-versions.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/networks/software-versions.mdx @@ -1922,15 +1922,15 @@ Ver https://github.com/stellar/soroban-cli/releases v0.2.0, v0.2.1 para más det ### Registro de cambios -Ver https://www.stellar.org/blog/soroban-a-new-smart-contract-standard. +Ver https://stellar.org/blog/soroban-a-new-smart-contract-standard. ## Vista previa 2 (13 de septiembre de 2022) -Ver https://www.stellar.org/developers-blog/soroban-preview-release-2. +Ver https://stellar.org/developers-blog/soroban-preview-release-2. ## Vista previa 1 (1 de agosto de 2022) -Ver https://www.stellar.org/blog/project-jump-cannon-soroban-preview-release. +Ver https://stellar.org/blog/project-jump-cannon-soroban-preview-release. [@waldmatias]: https://github.com/waldmatias [@willemneal]: https://github.com/willemneal diff --git a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx index b088a875d5..f75e40edc6 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/platforms/anchor-platform/sep-guide/sep24/setting-up-production-server.mdx @@ -119,4 +119,4 @@ Tener un grupo de testers beta es una excelente forma de verificar si hay casos Todas las interacciones de usuarios de Anchor se realizan a través de una wallet, por lo que es vital para las anchors estar conectadas a wallets que tengan buena penetración en el mercado de la región donde se enfoque el negocio. Conectarse a wallets es un proceso sencillo, ya que ambos extremos de esa integración ya cumplen con los SEPs. -Stellar.org mantiene una [lista de wallets](https://www.stellar.org/ecosystem/projects), muchas de las cuales actualmente soportan SEP-24. Enviarles un mensaje con más información sobre un activo y una cuenta emisora es una excelente forma de comenzar a atraer usuarios reales a la Anchor. +Stellar.org mantiene una [lista de wallets](https://stellar.org/ecosystem/projects), muchas de las cuales actualmente soportan SEP-24. Enviarles un mensaje con más información sobre un activo y una cuenta emisora es una excelente forma de comenzar a atraer usuarios reales a la Anchor. diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/configuring.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/configuring.mdx index 254e273b4e..fa7671679a 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/configuring.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/configuring.mdx @@ -291,5 +291,5 @@ Supongamos que hay 3 organizaciones de calidad `HIGH`, 2 organizaciones de calid [array `HOME_DOMAINS`]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L671 [array `VALIDATORS`]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L688 [SEP-20]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md -[cómo Stellar aborda los quorums]: https://www.stellar.org/developers-blog/why-quorums-matter-and-how-stellar-approaches-them +[cómo Stellar aborda los quorums]: https://stellar.org/developers-blog/why-quorums-matter-and-how-stellar-approaches-them [configuración de red pública para un Validador Completo]: https://github.com/stellar/packages/blob/master/docs/examples/pubnet-validator-full/stellar-core.cfg diff --git a/i18n/es/docusaurus-theme-classic/footer.json b/i18n/es/docusaurus-theme-classic/footer.json index f29920d203..ba5e8ab695 100644 --- a/i18n/es/docusaurus-theme-classic/footer.json +++ b/i18n/es/docusaurus-theme-classic/footer.json @@ -17,7 +17,7 @@ }, "link.item.label.Developer Blog": { "message": "Blog de Desarrolladores", - "description": "The label of footer link with label=Developer Blog linking to https://www.stellar.org/developers-blog" + "description": "The label of footer link with label=Developer Blog linking to https://stellar.org/developers-blog" }, "link.item.label.Stellar Quest": { "message": "Búsqueda Stellar", diff --git a/openapi/horizon/bundled.yml b/openapi/horizon/bundled.yml index 09fdd524ef..99e2a66321 100644 --- a/openapi/horizon/bundled.yml +++ b/openapi/horizon/bundled.yml @@ -8,7 +8,7 @@ info: Horizon can be accessed via cURL, a browser, or one of the [Stellar SDKs](https://developers.stellar.org/docs/tools/sdks). To reduce the complexity of your project, we recommend you use an SDK instead of making direct API calls. - This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://www.stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). + This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). Before we begin, it's worth reiterating the sentiment echoed in the [Core Node](https://developers.stellar.org/network/core-node) documentation: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance). termsOfService: https://stellar.org/terms-of-service diff --git a/openapi/horizon/main.yml b/openapi/horizon/main.yml index 47f74dda81..07871e4562 100644 --- a/openapi/horizon/main.yml +++ b/openapi/horizon/main.yml @@ -8,7 +8,7 @@ info: Horizon can be accessed via cURL, a browser, or one of the [Stellar SDKs](https://developers.stellar.org/docs/tools/sdks). To reduce the complexity of your project, we recommend you use an SDK instead of making direct API calls. - This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://www.stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). + This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). Before we begin, it's worth reiterating the sentiment echoed in the [Core Node](https://developers.stellar.org/network/core-node) documentation: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance). termsOfService: https://stellar.org/terms-of-service diff --git a/static/llms.txt b/static/llms.txt index 5aa11bd52d..d2851d9ec8 100644 --- a/static/llms.txt +++ b/static/llms.txt @@ -260,7 +260,7 @@ Discuss Core Advancement Proposals (CAPs) and Stellar Ecosystem Proposals (SEPs) Resources -- [Developer Blog](https://www.stellar.org/developers-blog) +- [Developer Blog](https://stellar.org/developers-blog) - [Stellar Quest](https://quest.stellar.org/) - [Soroban Quest](https://fastcheapandoutofcontrol.com/tutorial) - [YouTube](https://www.youtube.com/@StellarDevelopmentFoundation) From 9a5afd9a77b0fd9a6fad3a6faecbbf670e5a8cc6 Mon Sep 17 00:00:00 2001 From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com> Date: Sun, 26 Apr 2026 07:42:13 -0400 Subject: [PATCH 4/5] Revert "docs: expand horizon streaming guide" This reverts commit 0257b486e226eefe6d2e8631be5eb03394122d90. --- .../api-reference/structure/streaming.mdx | 64 +++++-------------- 1 file changed, 16 insertions(+), 48 deletions(-) diff --git a/docs/data/apis/horizon/api-reference/structure/streaming.mdx b/docs/data/apis/horizon/api-reference/structure/streaming.mdx index 00b71930f5..ad13f8ca33 100644 --- a/docs/data/apis/horizon/api-reference/structure/streaming.mdx +++ b/docs/data/apis/horizon/api-reference/structure/streaming.mdx @@ -1,59 +1,27 @@ --- -id: streaming title: Streaming -description: Use Horizon streaming mode to receive new ledger data in near real time. Streaming requests use the same endpoint parameters as normal requests and can begin from the earliest known record or from a supplied cursor. -sidebar_label: Streaming sidebar_position: 30 --- -Horizon supports streaming for endpoints that expose newly ingested ledger data over time. +import { MethodTable } from "@site/src/components/MethodTable"; -Instead of repeatedly polling an endpoint for new results, you can keep a connection open and receive updates as new ledgers close and matching records become available. This is useful when you want to react to ledger activity without repeatedly issuing requests that return no new data. +Horizon provides a streaming mechanism for receiving events in near real time. Instead of repeatedly sending requests to Horizon for batch updates, a connection is established between a client and Horizon with updates to an endpoint response streaming as new ledgers close and updates occur. -## How Streaming Works +This reduces requests that return no data and allows near instantaneous updates client-side. -Streaming mode uses the same endpoint and query parameters as the standard request for that resource. +All attributes for the endpoints that allow streaming are the same as regular responses. A caller can initiate streaming by setting ‘Accept: text/event-stream’ in the HTTP header when making the request. -To open a stream, send the request with the `Accept: text/event-stream` header. + -For example: +| | +| ----------------------------------------------------- | +| [Ledgers](../resources/ledgers/README.mdx) | +| [Transactions](../resources/transactions/README.mdx) | +| [Operations](../resources/operations/README.mdx) | +| [Payments](../resources/payments/README.mdx) | +| [Effects](../resources/effects/README.mdx) | +| [Accounts](../resources/accounts/README.mdx) | +| [Trades](../resources/trades/README.mdx) | +| [Order Books](../aggregations/order-books/README.mdx) | -```bash -curl -N \ - -H "Accept: text/event-stream" \ - "/operations?cursor=now" -``` - -## Cursor Behavior - -Cursor behavior is the main difference between a standard request and a streaming request. - -- If no `cursor` is provided, Horizon starts at the earliest known matching record and streams forward from there. -- If a `cursor` is provided, Horizon starts from that cursor. -- If `cursor=now` is provided, Horizon starts from your request time and streams only newly created matching records. - -Use `cursor=now` when you want to watch for new activity only. Use a specific cursor when you want to resume from a known point. - -## When To Use Streaming - -Streaming is a good fit when you want to: - -- watch for new transactions, operations, payments, or effects -- follow new ledger closures -- track changing order book data -- keep an application UI updated as new matching records arrive - -## Supported Endpoints - -Many Horizon resource endpoints support streaming. Check the individual endpoint reference to confirm whether a specific endpoint can be called in streaming mode. - -Common examples include endpoints for: - -- [Ledgers](../resources/ledgers/README.mdx) -- [Transactions](../resources/transactions/README.mdx) -- [Operations](../resources/operations/README.mdx) -- [Payments](../resources/payments/README.mdx) -- [Effects](../resources/effects/README.mdx) -- [Accounts](../resources/accounts/README.mdx) -- [Trades](../resources/trades/README.mdx) -- [Order Books](../aggregations/order-books/README.mdx) + From 7aeca3ff995fd73f1c80e0ea78307cce529e6dd5 Mon Sep 17 00:00:00 2001 From: "john.xlm" <60260750+JFWooten4@users.noreply.github.com> Date: Sun, 26 Apr 2026 08:00:27 -0400 Subject: [PATCH 5/5] copilot no.1 + new blog article format --- docs/data/apis/horizon/README.mdx | 2 +- docs/data/apis/horizon/admin-guide/overview.mdx | 2 +- docs/data/apis/rpc/providers.mdx | 2 +- docs/networks/software-versions.mdx | 2 +- docs/validators/admin-guide/configuring.mdx | 2 +- .../current/data/apis/api-providers.mdx | 2 +- .../current/data/apis/horizon/README.mdx | 2 +- .../current/data/apis/horizon/admin-guide/overview.mdx | 2 +- .../current/data/apis/rpc/providers.mdx | 2 +- .../current/networks/software-versions.mdx | 2 +- .../current/validators/admin-guide/configuring.mdx | 2 +- openapi/horizon/bundled.yml | 2 +- openapi/horizon/main.yml | 2 +- 13 files changed, 13 insertions(+), 13 deletions(-) diff --git a/docs/data/apis/horizon/README.mdx b/docs/data/apis/horizon/README.mdx index a69d1e5fd8..0200cd2611 100644 --- a/docs/data/apis/horizon/README.mdx +++ b/docs/data/apis/horizon/README.mdx @@ -17,7 +17,7 @@ Horizon provides an HTTP API to data in the Stellar network. It ingests and re-s Horizon can be accessed via cURL, a browser, or one of the [Stellar SDKs](../../../tools/sdks/README.mdx). To reduce the complexity of your project, we recommend you use an SDK instead of making direct API calls. -This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). +This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/blog/developers/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). Before we begin, it's worth reiterating the sentiment echoed in the [Core Node](../../../validators/README.mdx) documentation: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance). diff --git a/docs/data/apis/horizon/admin-guide/overview.mdx b/docs/data/apis/horizon/admin-guide/overview.mdx index 4841d20ad1..6f334b7659 100644 --- a/docs/data/apis/horizon/admin-guide/overview.mdx +++ b/docs/data/apis/horizon/admin-guide/overview.mdx @@ -5,7 +5,7 @@ sidebar_position: 0 Horizon is a central component of the Stellar platform: it provides an HTTP API to data in the Stellar network. It ingests and re-serves the data produced by the Stellar network in a form that is easier to consume by the average application relative to the performance-oriented data representations used by Stellar Core. -This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/internal/docs/DEVELOPING.md). +This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/blog/developers/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/internal/docs/DEVELOPING.md). Before we begin, it's worth reiterating the sentiment echoed in the [Run a Core Node](../../../../validators/README.mdx) guide: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance). diff --git a/docs/data/apis/rpc/providers.mdx b/docs/data/apis/rpc/providers.mdx index 78443e151c..71b8fd9587 100644 --- a/docs/data/apis/rpc/providers.mdx +++ b/docs/data/apis/rpc/providers.mdx @@ -40,7 +40,7 @@ _The "Dedicated Nodes" column represents providers who host full nodes as a serv | [sorobanrpc.com](https://sorobanrpc.com/) | Mainnet | RPC: `https://mainnet.sorobanrpc.com` | | [Nodies](https://nodies.org) | Testnet | RPC: `https://stellar-soroban-testnet-public.nodies.app` | | | Mainnet | RPC: `https://stellar-soroban-public.nodies.app` | -| [SDF](http://stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org` | +| [SDF](https://stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org` | | | Testnet | RPC: `https://soroban-testnet.stellar.org` | | [OnFinality](https://onfinality.io/networks/stellar) | Mainnet | RPC: `https://stellar.api.onfinality.io/public` | | [Lightsail Network - Quasar](https://quasar.lightsail.network/) | Mainnet | RPC `https://rpc.lightsail.network/` | diff --git a/docs/networks/software-versions.mdx b/docs/networks/software-versions.mdx index c3759bdfe1..f50e1f3797 100644 --- a/docs/networks/software-versions.mdx +++ b/docs/networks/software-versions.mdx @@ -1996,7 +1996,7 @@ See https://stellar.org/blog/soroban-a-new-smart-contract-standard. ## Preview 2 (September 13th, 2022) -See https://stellar.org/developers-blog/soroban-preview-release-2. +See https://stellar.org/blog/developers/soroban-preview-release-2. ## Preview 1 (August 1st, 2022) diff --git a/docs/validators/admin-guide/configuring.mdx b/docs/validators/admin-guide/configuring.mdx index ca3cfa640f..a2a736c2ad 100644 --- a/docs/validators/admin-guide/configuring.mdx +++ b/docs/validators/admin-guide/configuring.mdx @@ -291,5 +291,5 @@ Let there be 3 `HIGH` quality organizations, 2 `MEDIUM` quality organizations, a [`HOME_DOMAINS` array]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L671 [`VALIDATORS` array]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L688 [SEP-20]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md -[how Stellar approaches quorums]: https://stellar.org/developers-blog/why-quorums-matter-and-how-stellar-approaches-them +[how Stellar approaches quorums]: https://stellar.org/blog/developers/why-quorums-matter-and-how-stellar-approaches-them [public network config for a Full Validator]: https://github.com/stellar/packages/blob/master/docs/examples/pubnet-validator-full/stellar-core.cfg diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/api-providers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/api-providers.mdx index c3923d1c4a..82bc7307bb 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/api-providers.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/api-providers.mdx @@ -50,7 +50,7 @@ Estos proveedores permiten acceder a la red Futurenet, Testnet y Mainnet. | [sorobanrpc.com](https://sorobanrpc.com/) | Mainnet | RPC: `https://mainnet.sorobanrpc.com` | | [Nodies](https://nodies.org) | Testnet | RPC: `https://stellar-soroban-testnet-public.nodies.app` | | | Mainnet | RPC: `https://stellar-soroban-public.nodies.app` | -| [SDF](http://stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org`
Horizon: `https://horizon-futurenet.stellar.org` | +| [SDF](https://stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org`
Horizon: `https://horizon-futurenet.stellar.org` | | | Testnet | RPC: `https://soroban-testnet.stellar.org`
Horizon: `https://horizon-testnet.stellar.org` | | [LOBSTR](https://lobstr.co) | Mainnet | Horizon: `https://horizon.stellar.lobstr.co` | | [OnFinality](https://onfinality.io/networks/stellar) | Mainnet | RPC: `https://stellar.api.onfinality.io/public` | diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/README.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/README.mdx index 9f8ed8ad9b..4126f1cb9f 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/README.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/README.mdx @@ -17,7 +17,7 @@ Horizon proporciona una API HTTP para datos en la red Stellar. Recoge y vuelve a Horizon se puede acceder a través de cURL, un navegador o uno de los [Stellar SDKs](../../../tools/sdks/README.mdx). Para reducir la complejidad de tu proyecto, te recomendamos usar un SDK en vez de hacer llamadas directas a la API. -Esta guía describe cómo administrar una instancia de producción de Horizon (consulta el [Blog de los desarrolladores](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) para algunos antecedentes sobre las mejoras de rendimiento y arquitectónicas de esta importante actualización de versión). Para obtener información sobre el desarrollo en el código base de Horizon, consulta la [Guía de Desarrollo](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). +Esta guía describe cómo administrar una instancia de producción de Horizon (consulta el [Blog de los desarrolladores](https://stellar.org/blog/developers/a-new-sun-on-the-horizon) para algunos antecedentes sobre las mejoras de rendimiento y arquitectónicas de esta importante actualización de versión). Para obtener información sobre el desarrollo en el código base de Horizon, consulta la [Guía de Desarrollo](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). Antes de comenzar, vale la pena reiterar el sentimiento expresado en la documentación de [Core Node](../../../validators/README.mdx): **no respaldamos correr Horizon respaldado por una instancia de Stellar Core independiente**, y especialmente no por un Stellar Core _validante_. Estas son dos preocupaciones separadas, y desacoplarlas es importante tanto para la confiabilidad como para el rendimiento. Horizon en cambio gestiona su propia versión reducida de Stellar Core optimizada para su propio subconjunto de necesidades (nos referiremos a esto como una instancia de "Core cautivo"). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/overview.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/overview.mdx index 9fa7db2029..f47a8f2830 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/overview.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/horizon/admin-guide/overview.mdx @@ -5,7 +5,7 @@ sidebar_position: 0 Horizon es un componente central de la plataforma Stellar: proporciona una API HTTP para los datos en la red Stellar. Ingiere y vuelve a servir los datos producidos por la red Stellar en una forma que es más fácil de consumir por la aplicación promedio en comparación con las representaciones de datos orientadas al rendimiento utilizadas por Stellar Core. -Esta guía describe cómo administrar una instancia de Horizon en producción (consulta el [Blog de Desarrolladores](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) para obtener información de fondo sobre las mejoras de rendimiento y arquitectónicas de este importante aumento de versión). Para obtener información sobre cómo desarrollar en la base de código de Horizon, consulta la [Guía de Desarrollo](https://github.com/stellar/stellar-horizon/blob/main/internal/docs/DEVELOPING.md). +Esta guía describe cómo administrar una instancia de Horizon en producción (consulta el [Blog de Desarrolladores](https://stellar.org/blog/developers/a-new-sun-on-the-horizon) para obtener información de fondo sobre las mejoras de rendimiento y arquitectónicas de este importante aumento de versión). Para obtener información sobre cómo desarrollar en la base de código de Horizon, consulta la [Guía de Desarrollo](https://github.com/stellar/stellar-horizon/blob/main/internal/docs/DEVELOPING.md). Antes de comenzar, vale la pena reiterar el sentimiento expuesto en la guía [Ejecutar un Nodo Core](../../../../validators/README.mdx): **no recomendamos ejecutar Horizon respaldado por una instancia independiente de Stellar Core**, y especialmente no por un Stellar Core _validador_. Estas son dos preocupaciones separadas, y desacoplarlas es importante tanto para la confiabilidad como para el rendimiento. Horizon, en cambio, gestiona su propia versión reducida de Stellar Core optimizada para su propio subconjunto de necesidades (nos referiremos a esto como una instancia de "Captive Core"). diff --git a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/providers.mdx b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/providers.mdx index c06e0b39f6..3ff6d6227d 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/providers.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/data/apis/rpc/providers.mdx @@ -39,7 +39,7 @@ _La columna "Dedicated Nodes" representa proveedores que alojan nodos completos | [sorobanrpc.com](https://sorobanrpc.com/) | Mainnet | RPC: `https://mainnet.sorobanrpc.com` | | [Nodies](https://nodies.org) | Testnet | RPC: `https://stellar-soroban-testnet-public.nodies.app` | | | Mainnet | RPC: `https://stellar-soroban-public.nodies.app` | -| [SDF](http://stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org` | +| [SDF](https://stellar.org) | Futurenet | RPC: `https://rpc-futurenet.stellar.org` | | [OnFinality](https://onfinality.io/networks/stellar) | Mainnet | RPC: `https://stellar.api.onfinality.io/public` | | [Lightsail Network - Quasar](https://quasar.lightsail.network/) | Mainnet | RPC `https://rpc.lightsail.network/` | | | Mainnet | RPC de archivo completo: `https://archive-rpc.lightsail.network/` | diff --git a/i18n/es/docusaurus-plugin-content-docs/current/networks/software-versions.mdx b/i18n/es/docusaurus-plugin-content-docs/current/networks/software-versions.mdx index 738358656c..85d8e0e946 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/networks/software-versions.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/networks/software-versions.mdx @@ -1926,7 +1926,7 @@ Ver https://stellar.org/blog/soroban-a-new-smart-contract-standard. ## Vista previa 2 (13 de septiembre de 2022) -Ver https://stellar.org/developers-blog/soroban-preview-release-2. +Ver https://stellar.org/blog/developers/soroban-preview-release-2. ## Vista previa 1 (1 de agosto de 2022) diff --git a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/configuring.mdx b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/configuring.mdx index fa7671679a..36a3e2d885 100644 --- a/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/configuring.mdx +++ b/i18n/es/docusaurus-plugin-content-docs/current/validators/admin-guide/configuring.mdx @@ -291,5 +291,5 @@ Supongamos que hay 3 organizaciones de calidad `HIGH`, 2 organizaciones de calid [array `HOME_DOMAINS`]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L671 [array `VALIDATORS`]: https://github.com/stellar/stellar-core/blob/master/docs/stellar-core_example.cfg#L688 [SEP-20]: https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md -[cómo Stellar aborda los quorums]: https://stellar.org/developers-blog/why-quorums-matter-and-how-stellar-approaches-them +[cómo Stellar aborda los quorums]: https://stellar.org/blog/developers/why-quorums-matter-and-how-stellar-approaches-them [configuración de red pública para un Validador Completo]: https://github.com/stellar/packages/blob/master/docs/examples/pubnet-validator-full/stellar-core.cfg diff --git a/openapi/horizon/bundled.yml b/openapi/horizon/bundled.yml index 99e2a66321..647446baa2 100644 --- a/openapi/horizon/bundled.yml +++ b/openapi/horizon/bundled.yml @@ -8,7 +8,7 @@ info: Horizon can be accessed via cURL, a browser, or one of the [Stellar SDKs](https://developers.stellar.org/docs/tools/sdks). To reduce the complexity of your project, we recommend you use an SDK instead of making direct API calls. - This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). + This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/blog/developers/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). Before we begin, it's worth reiterating the sentiment echoed in the [Core Node](https://developers.stellar.org/network/core-node) documentation: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance). termsOfService: https://stellar.org/terms-of-service diff --git a/openapi/horizon/main.yml b/openapi/horizon/main.yml index 07871e4562..2590034646 100644 --- a/openapi/horizon/main.yml +++ b/openapi/horizon/main.yml @@ -8,7 +8,7 @@ info: Horizon can be accessed via cURL, a browser, or one of the [Stellar SDKs](https://developers.stellar.org/docs/tools/sdks). To reduce the complexity of your project, we recommend you use an SDK instead of making direct API calls. - This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/developers-blog/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). + This guide describes how to administer a production Horizon instance (refer to the [Developers' Blog](https://stellar.org/blog/developers/a-new-sun-on-the-horizon) for some background on the performance and architectural improvements of this major version bump). For information about developing on the Horizon codebase, check out the [Development Guide](https://github.com/stellar/stellar-horizon/blob/main/DEVELOPING.md). Before we begin, it's worth reiterating the sentiment echoed in the [Core Node](https://developers.stellar.org/network/core-node) documentation: **we do not endorse running Horizon backed by a standalone Stellar Core instance**, and especially not by a _validating_ Stellar Core. These are two separate concerns, and decoupling them is important for both reliability and performance. Horizon instead manages its own, pared-down version of Stellar Core optimized for its own subset of needs (we'll refer to this as a "Captive Core" instance). termsOfService: https://stellar.org/terms-of-service