stellar · JFWooten4 · Apr 23, 2026 · Apr 26, 2026 · Apr 26, 2026 · Apr 26, 2026
diff --git 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/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",

diff --git 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
@@ -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
@@ -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/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
@@ -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/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/.../api-reference/errors/http-status-codes/horizon-specific/transaction-failed.mdx b/.../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
@@ -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
@@ -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
@@ -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
@@ -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](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/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
@@ -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/blog/developers/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
@@ -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
@@ -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/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/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",
Original file line number	Diff line number	Diff line change
Expand Up		@@ -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.
Copy link Copy Markdown Contributor Author JFWooten4 Apr 26, 2026 Choose a reason for hiding this comment The reason will be displayed to describe this comment to others. Learn more. moved into JFWooten4@`bc80f63`