Move Security Encyclopedia Sections (#1580)

briwylde08 · ElliotFriend · web-flow · commit aa02c2ffdc7f · 2025-06-18T15:36:35.000-06:00
* move securing web-based projects

* routes

* move signatures section

* links

* another link

* routes

* more routes

* redirects

* Update nginx/includes/redirects.conf

Co-authored-by: Elliot Voris &lt;elliot@stellar.org&gt;

* fix more redirects

---------

Co-authored-by: Elliot Voris &lt;elliot@stellar.org&gt;
diff --git a/docs/build/apps/application-design-considerations.mdx b/docs/build/apps/application-design-considerations.mdx
@@ -11,7 +11,7 @@ There are four custody options to consider:
 
 - Non-custodial service - the user of the application stores their own secret key
 - Custodial service - the service provider (application) stores the users’ secret keys
-- Mixture of both - with the use of [multisig](../../learn/encyclopedia/security/signatures-multisig.mdx), this option is useful for maintaining non-custodial status while still allowing for account recovery
+- Mixture of both - with the use of [multisig](../../learn/fundamentals/transactions/signatures-multisig.mdx), this option is useful for maintaining non-custodial status while still allowing for account recovery
 - Third-party key management services - integrate a third-party custodial service into your application that can store your users’ secret keys
 
 ### Non-custodial service
@@ -28,7 +28,7 @@ Many custodial services choose to use a single pooled Stellar account (called sh
 
 ### A mixture of non-custodial and custodial
 
-Building an application with [multi-signature](../../learn/encyclopedia/security/signatures-multisig.mdx) capabilities allows you to have a non-custodial service with account recovery. If the user loses their secret key, they can still sign transactions with other authorized signatures, granted the signature threshold is high enough.
+Building an application with [multi-signature](../../learn/fundamentals/transactions/signatures-multisig.mdx) capabilities allows you to have a non-custodial service with account recovery. If the user loses their secret key, they can still sign transactions with other authorized signatures, granted the signature threshold is high enough.
 
 ### Third-party key management services​
 
diff --git a/docs/build/apps/wallet/sep30.mdx b/docs/build/apps/wallet/sep30.mdx
@@ -233,7 +233,7 @@ let recoverableWallet = try await recovery.createRecoverableWallet(config: confi
 With the given parameters, this function will create a transaction that will:
 
 1. Set `deviceKp` as the primary account key. Please note that the master key belonging to `accountKp` will be locked. `deviceKp` should be used as a primary signer instead.
-2. Set all operation thresholds to 10. You can read more about threshold in the [documentation](../../../learn/encyclopedia/security/signatures-multisig.mdx#thresholds)
+2. Set all operation thresholds to 10. You can read more about threshold in the [documentation](../../../learn/fundamentals/transactions/signatures-multisig.mdx#thresholds)
 3. Use identities that were defined earlier on both servers. (That means, both server will accept SEP-10 authentication via `recoveryKp` as an auth method)
 4. Set device key weight to 10, and recovery server weight to 5. Given these account thresholds, both servers must be used to recover the account, as transaction signed by one will only have weight of 5, which is not sufficient to change account key.
 
diff --git a/docs/build/guides/tokens/custom-sac-admin.mdx b/docs/build/guides/tokens/custom-sac-admin.mdx
@@ -39,7 +39,7 @@ The following example will create a new Stellar asset, `STAR:GCS5NEHKJALCSVJAKIO
 
 :::note
 
-We will not demonstrate setting a new `G...` account as a SAC admin in this guide. Any use-case that needs asset administration delegated to another `G...` account will likely be better served by taking advantage of the existing [multisig capabilities](../../../learn/encyclopedia/security/signatures-multisig.mdx) of Stellar accounts.
+We will not demonstrate setting a new `G...` account as a SAC admin in this guide. Any use-case that needs asset administration delegated to another `G...` account will likely be better served by taking advantage of the existing [multisig capabilities](../../../learn/fundamentals/transactions/signatures-multisig.mdx) of Stellar accounts.
 
 :::
 
diff --git a/docs/build/security-docs/securing-web-based-projects.mdx b/docs/build/security-docs/securing-web-based-projects.mdx
diff --git a/docs/learn/encyclopedia/security/README.mdx b/docs/learn/encyclopedia/security/README.mdx
diff --git a/docs/learn/fundamentals/contract-development/authorization.mdx b/docs/learn/fundamentals/contract-development/authorization.mdx
@@ -87,7 +87,7 @@ This is a special, built-in 'account contract' that handles all the Stellar acco
 
 This supports the Stellar multisig with medium threshold. See Stellar [documentation] for more details on multisig and thresholds.
 
-[documentation]: ../../encyclopedia/security/signatures-multisig.mdx
+[documentation]: ../transactions/signatures-multisig.mdx
 
 ##### Transaction Invoker
 
diff --git a/docs/learn/fundamentals/stellar-data-structures/accounts.mdx b/docs/learn/fundamentals/stellar-data-structures/accounts.mdx
@@ -28,8 +28,8 @@ There are two types of accounts on Stellar: Stellar accounts (`G...` addresses)
 - [Number of sponsored reserves](../../encyclopedia/transactions-specialized/sponsored-reserves.mdx)
 - [Number of subentries](./accounts.mdx#subentries)
 - [Sequence number](../../glossary.mdx#sequence-number)
-- [Signers](../../encyclopedia/security/signatures-multisig.mdx)
-- [Thresholds](../../encyclopedia/security/signatures-multisig.mdx#thresholds)
+- [Signers](../../fundamentals/transactions/signatures-multisig.mdx)
+- [Thresholds](../../fundamentals/transactions/signatures-multisig.mdx#thresholds)
 
 ## Base reserves and subentries
 
diff --git a/docs/learn/fundamentals/transactions/list-of-operations.mdx b/docs/learn/fundamentals/transactions/list-of-operations.mdx
@@ -249,7 +249,7 @@ Set options for an account such as flags, inflation destination, signers, home d
 
 Learn more about flags: [Flags Encyclopedia Entry](../../glossary.mdx#flags)  
 Learn more about the home domain: [Stellar Ecosystem Proposals SEP-0001](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md)  
-Learn more about signers operations and key weight: [Signature and Multisignature Encyclopedia Entry](../../encyclopedia/security/signatures-multisig.mdx)
+Learn more about signers operations and key weight: [Signature and Multisignature Encyclopedia Entry](../../fundamentals/transactions/signatures-multisig.mdx)
 
 **SDKs**: [JavaScript](http://stellar.github.io/js-stellar-sdk/Operation.html#.setOptions) | [Java](https://github.com/lightsail-network/java-stellar-sdk/blob/master/src/main/java/org/stellar/sdk/operations/SetOptionsOperation.java) | [Go](https://godoc.org/github.com/stellar/go/txnbuild#SetOptions)  
 **Threshold**: High (when updating signers or other thresholds) or Medium (when updating everything else)  
@@ -262,9 +262,9 @@ Learn more about signers operations and key weight: [Signature and Multisignatur
 | Clear flags | integer | Indicates which [account](../stellar-data-structures/accounts.mdx) flags to clear. These account-level flags are primarily used by asset issuers. For details about the flags, please refer to the [Asset Design Considerations page](../../../tokens/control-asset-access.mdx). The bit mask integer subtracts from the existing flags of the account. This allows for setting specific bits without knowledge of existing flags. |
 | Set flags | integer | Indicates which [account](../stellar-data-structures/accounts.mdx) flags to set. These account-level flags are primarily used by asset issuers. For details about the flags, please refer to the [Asset Design Considerations page](../../../tokens/control-asset-access.mdx#controlling-access-to-an-asset-with-flags) The bit mask integer adds onto the existing flags of the account. This allows for setting specific bits without knowledge of existing flags. |
 | Master weight | integer | A number from 0-255 (inclusive) representing the weight of the master key. If the weight of the master key is updated to 0, it is effectively disabled. |
-| Low threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a low threshold](../../encyclopedia/security/signatures-multisig.mdx). |
-| Medium threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a medium threshold](../../encyclopedia/security/signatures-multisig.mdx). |
-| High threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a high threshold](../../encyclopedia/security/signatures-multisig.mdx). |
+| Low threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a low threshold](../../fundamentals/transactions/signatures-multisig.mdx). |
+| Medium threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a medium threshold](../../fundamentals/transactions/signatures-multisig.mdx). |
+| High threshold | integer | A number from 0-255 (inclusive) representing the threshold this account sets on all operations it performs that have [a high threshold](../../fundamentals/transactions/signatures-multisig.mdx). |
 | Home domain | string | Sets the home domain of an account. See [Federation](../../glossary.mdx#federation). |
 | Signer | \{Public Key, weight} | Add, update, or remove a signer from an account. Signer weight is a number from 0-255 (inclusive). The signer is deleted if the weight is 0. |
 
diff --git a/docs/learn/fundamentals/transactions/operations-and-transactions.mdx b/docs/learn/fundamentals/transactions/operations-and-transactions.mdx
@@ -17,7 +17,7 @@ Operations are individual commands that modify the ledger. Operations are used t
 
 All operations fall into one of three threshold categories: low, medium, or high, and each threshold category has a weight between 0 and 255 (which can be determined using set_options). Thresholds determine what signature weight is required for the operation to be accepted. For example, let’s say an account sets the medium threshold weight to 5. If the account wants to successfully establish a trustline with the `changeTrust` operation, the weight of the signature(s) must be greater than or equal to 5.
 
-To learn more about signature weight, see the [Signature and Multisignature Encyclopedia Entry](../../encyclopedia/security/signatures-multisig.mdx).
+To learn more about signature weight, see the [Signature and Multisignature Encyclopedia Entry](../../fundamentals/transactions/signatures-multisig.mdx).
 
 View a comprehensive list of Stellar operations and their threshold levels in the [List of Operations section](./list-of-operations.mdx).
 
@@ -29,7 +29,7 @@ Accounts can only perform one transaction at a time.
 
 Transactions comprise a bundle of between 1-100 operations (except smart contract transactions, which can only have one operation per transaction) and are signed and submitted to the ledger by accounts. Transactions always need to be authorized by the source account’s public key to be valid, which involves signing the transaction object with the public key’s associated secret key. A transaction plus its signature(s) is called a transaction envelope.
 
-A transaction may need more than one signature- this happens if it has operations that affect more than one account or if it has a high threshold weight. Check out the [Signature and Multisignature Encyclopedia Entry](../../encyclopedia/security/signatures-multisig.mdx) for more information.
+A transaction may need more than one signature- this happens if it has operations that affect more than one account or if it has a high threshold weight. Check out the [Signature and Multisignature Encyclopedia Entry](../../fundamentals/transactions/signatures-multisig.mdx) for more information.
 
 Transactions are atomic. Meaning if one operation in a transaction fails, all operations fail, and the entire transaction is not applied to the ledger.
 
@@ -41,7 +41,7 @@ Smart contract transactions also go through a simulation process where developer
 
 - [Fee](../fees-resource-limits-metering.mdx)
 - [List of operations](./list-of-operations.mdx)
-- [List of signatures](../../encyclopedia/security/signatures-multisig.mdx)
+- [List of signatures](../../fundamentals/transactions/signatures-multisig.mdx)
 - [Memo or muxed account](../../encyclopedia/transactions-specialized/pooled-accounts-muxed-accounts-memos.mdx)
 - [Sequence number](../../glossary.mdx#sequence-number)
 - [Source account](../../glossary.mdx#source-account)
diff --git a/docs/learn/fundamentals/transactions/signatures-multisig.mdx b/docs/learn/fundamentals/transactions/signatures-multisig.mdx
diff --git a/docs/learn/fundamentals/transactions/transaction-lifecycle.mdx b/docs/learn/fundamentals/transactions/transaction-lifecycle.mdx
@@ -15,7 +15,7 @@ A user creates a transaction by setting the source account, sequence number, lis
 
 ### 2. Signing (Transaction Signers)
 
-Once the transaction is complete, it becomes a transaction envelope containing the transaction itself and a list of signers. All the required signatures must be collected and added to the transaction envelope’s list of signers. Commonly, it’s just the signature of the account doing the transaction, but more complicated setups can require collecting signatures from multiple parties.
+Once the transaction is complete, it becomes a transaction envelope containing the transaction itself and a list of signers. All the required signatures must be collected and added to the transaction envelope’s list of signers. Commonly, it’s just the signature of the account doing the transaction, but more complicated setups can require collecting signatures from multiple parties. Read more about signatures in the [Signatures and Multisig section](./signatures-multisig.mdx).
 
 ### 3. Submitting (Transaction Submitter)
 
diff --git a/docs/learn/glossary.mdx b/docs/learn/glossary.mdx
@@ -285,7 +285,7 @@ Learn more in our [SEPs section](./fundamentals/stellar-ecosystem-proposals.mdx)
 
 Refers to the master key or to any other signing keys added later. A signer is defined as the pair: public key + weight. Signers can be set with the Set Options operation.
 
-See our [Signature and Multisignature Encyclopedia Entry](./encyclopedia/security/signatures-multisig.mdx) for more information.
+See our [Signature and Multisignature Encyclopedia Entry](./fundamentals/transactions/signatures-multisig.mdx) for more information.
 
 ### Smart contract
 
diff --git a/docs/tokens/control-asset-access.mdx b/docs/tokens/control-asset-access.mdx
@@ -224,6 +224,6 @@ This section details how to lock your account with the purpose of limiting the s
 
 With that warning in mind, it is possible to lock down the issuing account of an asset so that the asset’s supply cannot increase. To do this, first set the issuing account’s master weight to 0 using the Set Options operation. This prevents the issuing account from being able to sign transactions and therefore, making the issuer unable to issue any more assets. Be sure to do this only after you’ve issued all desired assets to the distribution account. If the asset has a Stellar Asset Contract, also make sure the admin for the contract was not updated from the default (which is the issuer) using the `set_admin` contract call. If the admin was not the issuer, then the admin would be able to mint the asset even with the issuing account locked.
 
-Learn more about signature weights in the [Signature and Multisig Encyclopedia Entry](../learn/encyclopedia/security/signatures-multisig.mdx).
+Learn more about signature weights in the [Signature and Multisig Encyclopedia Entry](../learn/fundamentals/transactions/signatures-multisig.mdx).
 
 See how to do this in the optional steps of the [Issuing an Asset Tutorial](./how-to-issue-an-asset.mdx#configure-maximum-supply).
diff --git a/docs/tokens/how-to-issue-an-asset.mdx b/docs/tokens/how-to-issue-an-asset.mdx
@@ -75,7 +75,7 @@ fmt.Println("Issuer Secret Key:", issuerKeypair.Seed())
 
 :::info
 
-Your account address will not change once you issue your asset, even if you modify its [signers](../learn/encyclopedia/security/signatures-multisig.mdx). Many issuers employ [vanity public keys](https://github.com/JFWooten4/py-stellar-vanity-toolkit) related to their asset. For instance, you might configure a custom signer in [base32](../learn/glossary.mdx#account-id) like `GASTRO...USD`.
+Your account address will not change once you issue your asset, even if you modify its [signers](../learn/fundamentals/transactions/signatures-multisig.mdx). Many issuers employ [vanity public keys](https://github.com/JFWooten4/py-stellar-vanity-toolkit) related to their asset. For instance, you might configure a custom signer in [base32](../learn/glossary.mdx#account-id) like `GASTRO...USD`.
 
 :::
 
@@ -135,7 +135,7 @@ distributorKeypair := keypair.MustParseFull("SCZANGBA5YHTNYVVV4C3U252E2B6P6F5T3U
 
 </CodeExample>
 
-##### Employ [multiple signatures](../learn/encyclopedia/security/signatures-multisig.mdx)
+##### Employ [multiple signatures](../learn/fundamentals/transactions/signatures-multisig.mdx)
 
 :::danger
 
diff --git a/nginx/includes/redirects.conf b/nginx/includes/redirects.conf
@@ -15,7 +15,7 @@ rewrite ^/docs/(learn/)?glossary/liquidity-pools$ "/docs/learn/encyclopedia/sdex
 rewrite ^/docs/(learn/)?encyclopedia/liquidity-on-stellar-sdex-and-liquidity-pools(.*)$ "/docs/learn/encyclopedia/sdex/liquidity-on-stellar-sdex-liquidity-pools$1" permanent;
 rewrite ^/docs/(learn/)?glossary/lumen-supply$ "/docs/learn/fundamentals/lumens#lumen-supply-metrics" permanent;
 rewrite ^/docs/(learn/)?glossary/minimum-balance$ "/docs/learn/fundamentals/lumens#minimum-balance" permanent;
-rewrite ^/docs/(learn/)?glossary/multisig$ "/docs/learn/encyclopedia/security/signatures-and-multisig" permanent;
+rewrite ^/docs/(learn/)?glossary/multisig$ "/docs/learn/fundamentals/transactions/signatures-multisig" permanent;
 rewrite ^/docs/(learn/)?glossary/muxed-accounts$ "/docs/learn/encyclopedia/transactions-specialized/pooled-accounts-muxed-accounts-memos" permanent;
 rewrite ^/docs/(learn/)?glossary/network-passphrase$ "/docs/learn/encyclopedia/network-configuration/network-passphrases" permanent;
 rewrite ^/docs/(learn/)?glossary/operations$ "/docs/learn/fundamentals/stellar-data-structures/operations-and-transactions#operations" permanent;
@@ -33,7 +33,7 @@ rewrite ^/docs/start/introduction$ "/docs" permanent;
 rewrite ^/docs/start/list-of-operations$ "/docs/learn/fundamentals/list-of-operations" permanent;
 rewrite ^/docs/start/stellar-stack$ "/docs/learn/fundamentals/stellar-stack" permanent;
 rewrite ^/docs/tutorials/handling-errors$ "/docs/learn/fundamentals/contract-development/errors-and-debugging/debugging-errors" permanent;
-rewrite ^/docs/tutorials/securing-projects$ "/docs/learn/encyclopedia/security/securing-web-based-projects" permanent;
+rewrite ^/docs/tutorials/securing-projects$ "/docs/build/security-docs/securing-web-based-projects" permanent;
 rewrite ^/docs/tutorials/moneygram-access-integration-guide$ "/docs/build/apps/moneygram-access-integration-guide" permanent;
 rewrite ^/docs/fundamentals-and-concepts/testnet-and-pubnet$ "/docs/learn/fundamentals/networks" permanent;
 rewrite ^/api$ "/docs/data/apis/horizon" permanent;
@@ -140,8 +140,8 @@ rewrite ^/docs/learn/encyclopedia/memos$ "/docs/learn/encyclopedia/transactions-
 rewrite ^/docs/learn/encyclopedia/network-passphrases$ "/docs/learn/encyclopedia/network-configuration/network-passphrases" permanent;
 rewrite ^/docs/learn/encyclopedia/path-payments$ "/docs/learn/encyclopedia/transactions-specialized/path-payments" permanent;
 rewrite ^/docs/learn/encyclopedia/pooled-accounts-muxed-accounts-memos$ "/docs/learn/encyclopedia/transactions-specialized/pooled-accounts-muxed-accounts-memos" permanent;
-rewrite ^/docs/learn/encyclopedia/securing-web-based-projects$ "/docs/learn/encyclopedia/security/securing-web-based-projects" permanent;
-rewrite ^/docs/learn/encyclopedia/signatures-multisig$ "/docs/learn/encyclopedia/security/signatures-multisig" permanent;
+rewrite ^/docs/learn/encyclopedia/securing-web-based-projects$ "/docs/build/security-docs/securing-web-based-projects" permanent;
+rewrite ^/docs/learn/encyclopedia/signatures-multisig$ "/docs/learn/fundamentals/transactions/signatures-multisig" permanent;
 rewrite ^/docs/learn/encyclopedia/sponsored-reserves$ "/docs/learn/encyclopedia/transactions-specialized/sponsored-reserves" permanent;
 rewrite ^/docs/learn/encyclopedia/xdr$ "/docs/learn/encyclopedia/data-format/xdr" permanent;
 rewrite ^/network/core-node(.*)$ "/docs/validators$1" permanent;
@@ -209,3 +209,8 @@ rewrite ^/docs/learn/encyclopedia/errors-and-debugging(.*)$ "/docs/learn/fundame
 rewrite ^/docs/learn/encyclopedia/security/authorization(.*)$ "/docs/learn/fundamentals/contract-development/authorization$1" permanent;
 rewrite ^/docs/learn/encyclopedia/storage(.*)$ "/docs/learn/fundamentals/contract-development/storage$1" permanent;
 rewrite ^/docs/learn/encyclopedia/contract-development(.*)$ "/docs/learn/fundamentals/contract-development$1" permanent;
+
+# Moving the security section (https://github.com/stellar/stellar-docs/pull/1580)
+rewrite ^/docs/learn/encyclopedia/security/signatures-multisig$ "/docs/learn/fundamentals/transactions/signatures-multisig" permanent;
+rewrite ^/docs/learn/encyclopedia/security/securing-web-based-projects$ "/docs/build/security-docs/securing-web-based-projects" permanent;
+rewrite ^/docs/learn/encyclopedia/security "/docs/learn/fundamentals/transactions/signatures-multisig" permanent;
diff --git a/routes.txt b/routes.txt
diff --git a/src/pages/index.mdx b/src/pages/index.mdx
