diff --git a/docs/build/guides/basics/classic-transition.mdx b/docs/build/guides/basics/classic-transition.mdx
index 2d99f7ea57..b591417608 100644
--- a/docs/build/guides/basics/classic-transition.mdx
+++ b/docs/build/guides/basics/classic-transition.mdx
@@ -24,7 +24,7 @@ Horizon offers an effects endpoint that describes state changes executed by clas
 
 ### Simulating Transaction
 
-While events should be used to monitor changes to a contract’s state, clients may also need to determine the current state of a contract. [Simulation](../../../build/guides/transactions/simulateTransaction-Deep-Dive.mdx) allows clients to execute contract invocations with incurring fees or finalizing changes, making it an ideal approach for fetching contracts’ current state. For example, clients can call the balance function on a [SEP-0041](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md)-compliant token contract to fetch a user’s current balance.
+While events should be used to monitor changes to a contract’s state, clients may also need to determine the current state of a contract. [Simulation](../../../build/guides/transactions/simulateTransaction-Deep-Dive.mdx) allows clients to execute contract invocations with incurring fees or finalizing changes, making it an ideal approach for fetching contracts’ current state. For example, clients can call the balance function on a [SEP-41](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0041.md)-compliant token contract to fetch a user’s current balance.
 
 ## 3. Transaction Workflow Changes
 
diff --git a/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx b/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx
index 7c282cc957..cfd4bffbcd 100644
--- a/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx
+++ b/docs/build/guides/transactions/pooled-accounts-muxed-accounts-memos.mdx
@@ -26,7 +26,7 @@ Muxed accounts are embedded into the protocol for convenience and standardizatio
 
 Muxed accounts do not exist on the ledger, but their shared underlying `GABC…` account does.
 
-Muxed accounts are defined in [CAP-0027](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0027.md), introduced in Protocol 13, and their string representation is described in [SEP-0023](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md).
+Muxed accounts are defined in [CAP-0027](https://github.com/stellar/stellar-protocol/blob/master/core/cap-0027.md), introduced in Protocol 13, and their string representation is described in [SEP-23](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md).
 
 It is safe for all wallets to implement sending to muxed accounts.
 
diff --git a/docs/learn/fundamentals/stellar-ecosystem-proposals.mdx b/docs/learn/fundamentals/stellar-ecosystem-proposals.mdx
index 5084be5d6d..a0b911b0ee 100644
--- a/docs/learn/fundamentals/stellar-ecosystem-proposals.mdx
+++ b/docs/learn/fundamentals/stellar-ecosystem-proposals.mdx
@@ -27,7 +27,7 @@ There are many SEPs, and they cover a wide variety of standards for interoperati
 
 This section will cover a few notable SEPs that define the standards for some common Stellar use cases.
 
-### SEP-0001 - Stellar Info File
+### SEP-1 - Stellar Info File
 
 Defines how to create and host a stellar.toml file: a common place where the Internet can find information about your Stellar integration. You can store a lot of information in your stellar.toml file including organization information, currency information, and contact information. TOML is a simple and commonly used configuration file format designed to be readable by both humans and machines.
 
@@ -37,7 +37,7 @@ Using the `set_options` operation, you can link your Stellar account to the doma
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md)
 
-### SEP-0005 - Key Derivation Methods for Stellar Accounts
+### SEP-5 - Key Derivation Methods for Stellar Accounts
 
 Describes methods for key derivation for Stellar, improving key storage and moving keys between wallets and applications. Guidance in this SEP improves the Stellar ecosystem by:
 
@@ -50,7 +50,7 @@ Describes methods for key derivation for Stellar, improving key storage and movi
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0005.md)
 
-### SEP-0006 - Deposit and Withdrawal API
+### SEP-6 - Deposit and Withdrawal API
 
 Defines the standard way for anchors and wallets to interact on behalf of users. With this SEP’s guidance, wallets and other clients can interact with anchors directly without the user needing to leave the wallet to go to the anchor’s site.
 
@@ -64,13 +64,13 @@ This SEP defines a standard protocol enabling the following features within a wa
 - Check the status of ongoing deposits or withdrawals involving the user
 - View history of deposits and withdrawals involving the user
 
-SEP-0024 is the alternative to SEP-0006 which supports hosted deposits and withdrawals.
+SEP-24 is the alternative to SEP-6 which supports hosted deposits and withdrawals.
 
 **Used by anchors, wallets, and other applications.**
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md)
 
-### SEP-0007 - URI Scheme to Facilitate Delegated Signing
+### SEP-7 - URI Scheme to Facilitate Delegated Signing
 
 Defines the standard URI scheme that can be used to generate a URI that will serve as a request to sign a transaction. With this SEP’s guidance, non-wallet applications can have their their users sign a transaction without seeing the wallet user's secret key in any form since the URI (request) will typically be signed by the user’s trusted wallet where the secret keys are stored.
 
@@ -85,7 +85,7 @@ This SEP defines a standard protocol enabling the following features within a wa
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md)
 
-### SEP-0010 - Stellar Authentication
+### SEP-10 - Stellar Authentication
 
 Defines a standard way for clients (such as wallets or exchanges) to create authenticated web sessions for users holding a Stellar account. This SEP also supports authenticating users of shared or pooled Stellar accounts. Clients can use muxed accounts to distinguish users or sub-accounts of shared accounts.
 
@@ -95,7 +95,7 @@ Proves that the user has a Stellar account and that they control the account wit
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md)
 
-### SEP-0012 - KYC API
+### SEP-12 - KYC API
 
 Allows for sharing of KYC data and defines a standard way for Stellar clients to upload KYC and other information to anchors and other services. This SEP was made with these goals in mind:
 
@@ -110,7 +110,7 @@ Allows for sharing of KYC data and defines a standard way for Stellar clients to
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md)
 
-### SEP-0020 - Self-Verification of Validator Nodes
+### SEP-20 - Self-Verification of Validator Nodes
 
 Defines how validators self-verify by setting the home domain of their Stellar account to their website, where they publish information on-chain about their node and organization in a stellar.toml file. This allows other participants to discover other nodes and add them to their quorum sets without needing a centralized database.
 
@@ -118,19 +118,19 @@ Defines how validators self-verify by setting the home domain of their Stellar a
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md)
 
-### SEP-0024 - Hosted Deposit and Withdrawal
+### SEP-24 - Hosted Deposit and Withdrawal
 
 Defines the standard way for anchors and wallets to interact on behalf of users interactively. This means that the user’s application must open a webview hosted by a third-party anchor for the user to provide the information necessary to complete the transaction.
 
-Users use applications that implement SEP-0024 to connect to businesses that will accept off-chain value (such as USD) in exchange for on-chain value (such as USDC) and vice-versa.
+Users use applications that implement SEP-24 to connect to businesses that will accept off-chain value (such as USD) in exchange for on-chain value (such as USDC) and vice-versa.
 
-SEP-0006 is the alternative to SEP-0024 that supports an API-style solution for the same use case.
+SEP-6 is the alternative to SEP-24 that supports an API-style solution for the same use case.
 
 **Used by anchors, wallets, and other applications.**
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md)
 
-### SEP-0030 - Account Recovery: Multi-Party Recovery of Stellar Accounts
+### SEP-30 - Account Recovery: Multi-Party Recovery of Stellar Accounts
 
 Defines the standard API that enables an individual (e.g., a user or wallet) to regain access to a Stellar account that it owns after the individual has lost its private key without providing any third-party control of the account. Using this protocol, the user or wallet will preregister the account and a phone number, email, or other form of authentication with one or more servers implementing the protocol and add those servers as signers of the account. If two or more servers are used with appropriate signer configuration no individual server will have control of the account, but collectively, they may help the individual recover access to the account.
 
@@ -145,7 +145,7 @@ This SEP enables the following use cases for a user:
 
 [Link to GitHub](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0030.md)
 
-### SEP-0031 - Cross-Border Payment API
+### SEP-31 - Cross-Border Payment API
 
 Defines the protocol for two financial accounts that exist outside the Stellar network (anchors) to interact with each other.
 
@@ -157,26 +157,26 @@ Defines the protocol for two financial accounts that exist outside the Stellar n
 
 | Number | Title | Track |
 | --- | --- | --- |
-| [SEP-0001](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) | Stellar Info File | Standard |
-| [SEP-0002](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0002.md) | Federation Protocol | Standard |
-| [SEP-0004](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0004.md) | Tx Status Endpoint | Standard |
-| [SEP-0005](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0005.md) | Key Derivation Methods for Stellar Accounts | Standard |
-| [SEP-0006](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) | Deposit and Withdrawal API | Standard |
-| [SEP-0007](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md) | URI Scheme to facilitate delegated signing | Standard |
-| [SEP-0008](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md) | Regulated Assets | Standard |
-| [SEP-0009](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md) | Standard KYC Fields | Standard |
-| [SEP-0010](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) | Stellar Authentication | Standard |
-| [SEP-0011](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md) | Txrep: Human-Readable Low-Level Representation of Stellar Transactions | Standard |
-| [SEP-0012](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md) | KYC API | Standard |
-| [SEP-0014](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0014.md) | Dynamic Asset Metadata | Standard |
-| [SEP-0018](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0018.md) | Data Entry Namespaces | Standard |
-| [SEP-0020](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md) | Self-verification of validator nodes | Standard |
-| [SEP-0023](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md) | Muxed Account Strkeys | Standard |
-| [SEP-0024](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md) | Hosted Deposit and Withdrawal | Standard |
-| [SEP-0028](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0028.md) | XDR Base64 Encoding | Standard |
-| [SEP-0029](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0029.md) | Account Memo Requirements | Standard |
-| [SEP-0031](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md) | Cross-Border Payments API | Standard |
-| [SEP-0033](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0033.md) | Identicons for Stellar Accounts | Standard |
-| [SEP-0046](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0046.md) | Contract Meta | Standard |
-| [SEP-0048](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0048.md) | Contract Interface Specification | Standard |
-| [SEP-0050](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0050.md) | Non-Fungible Tokens | Standard |
+| [SEP-1](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) | Stellar Info File | Standard |
+| [SEP-2](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0002.md) | Federation Protocol | Standard |
+| [SEP-4](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0004.md) | Tx Status Endpoint | Standard |
+| [SEP-5](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0005.md) | Key Derivation Methods for Stellar Accounts | Standard |
+| [SEP-6](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md) | Deposit and Withdrawal API | Standard |
+| [SEP-7](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0007.md) | URI Scheme to facilitate delegated signing | Standard |
+| [SEP-8](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md) | Regulated Assets | Standard |
+| [SEP-9](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0009.md) | Standard KYC Fields | Standard |
+| [SEP-10](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md) | Stellar Authentication | Standard |
+| [SEP-11](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0011.md) | Txrep: Human-Readable Low-Level Representation of Stellar Transactions | Standard |
+| [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md) | KYC API | Standard |
+| [SEP-14](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0014.md) | Dynamic Asset Metadata | Standard |
+| [SEP-18](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0018.md) | Data Entry Namespaces | Standard |
+| [SEP-20](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0020.md) | Self-verification of validator nodes | Standard |
+| [SEP-23](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0023.md) | Muxed Account Strkeys | Standard |
+| [SEP-24](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md) | Hosted Deposit and Withdrawal | Standard |
+| [SEP-28](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0028.md) | XDR Base64 Encoding | Standard |
+| [SEP-29](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0029.md) | Account Memo Requirements | Standard |
+| [SEP-31](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md) | Cross-Border Payments API | Standard |
+| [SEP-33](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0033.md) | Identicons for Stellar Accounts | Standard |
+| [SEP-46](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0046.md) | Contract Meta | Standard |
+| [SEP-48](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0048.md) | Contract Interface Specification | Standard |
+| [SEP-50](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0050.md) | Non-Fungible Tokens | Standard |
diff --git a/docs/learn/fundamentals/transactions/list-of-operations.mdx b/docs/learn/fundamentals/transactions/list-of-operations.mdx
index d69f6e6ab2..d5dab533f9 100644
--- a/docs/learn/fundamentals/transactions/list-of-operations.mdx
+++ b/docs/learn/fundamentals/transactions/list-of-operations.mdx
@@ -248,7 +248,7 @@ Learn more about passive sell offers: [Liquidity on Stellar: SDEX and Liquidity
 Set options for an account such as flags, inflation destination, signers, home domain, and master key weight
 
 Learn more about flags: [Flags Section](../../../tokens/control-asset-access.mdx#controlling-access-to-an-asset-with-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 the home domain: [Stellar Ecosystem Proposals SEP-1](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md)  
 Learn more about signers operations and key weight: [Signature and Multisignature Section](../../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-stellar-sdk/txnbuild#SetOptions)  
diff --git a/docs/learn/glossary.mdx b/docs/learn/glossary.mdx
index ce486a0946..c0e521a8c7 100644
--- a/docs/learn/glossary.mdx
+++ b/docs/learn/glossary.mdx
@@ -337,7 +337,7 @@ A node that provides an interface for submitting transactions and reading data f
 
 ### Stellar.toml {/* #stellar-toml */}
 
-A formatted configuration file containing published information about a node and an organization. For more, see the [Stellar Info File spec (SEP-0001)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md).
+A formatted configuration file containing published information about a node and an organization. For more, see the [Stellar Info File spec (SEP-1)](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md).
 
 ### Stroop
 
diff --git a/docs/platforms/anchor-platform/admin-guide/events/integration.mdx b/docs/platforms/anchor-platform/admin-guide/events/integration.mdx
index 8b9f7527f4..3eef754cbb 100644
--- a/docs/platforms/anchor-platform/admin-guide/events/integration.mdx
+++ b/docs/platforms/anchor-platform/admin-guide/events/integration.mdx
@@ -77,10 +77,10 @@ Anchor Platform will only send events to clients listed in the client configurat
 
 Anchor Platform signs the callback requests it sends to client applications. The signature is included in the `Signature` header of the request. The callback URL signature specification can be found in the corresponding SEP protocol specifications.
 
-- [SEP-0006](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md#url-callback-signature)
-- [SEP-0012](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#callback-post-request)
-- [SEP-0024](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#url-callback-signature)
-- [SEP-0031](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md#url-callback-signature)
+- [SEP-6](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md#url-callback-signature)
+- [SEP-12](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md#callback-post-request)
+- [SEP-24](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md#url-callback-signature)
+- [SEP-31](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md#url-callback-signature)
 
 ### As a Business Server
 
diff --git a/docs/platforms/anchor-platform/sep-guide/sep10/README.mdx b/docs/platforms/anchor-platform/sep-guide/sep10/README.mdx
index 55981438fe..2f1af7cd20 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep10/README.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep10/README.mdx
@@ -7,7 +7,7 @@ sidebar_position: 60
 
 SEP-10 (Stellar Web Authentication) enables wallet applications to create authenticated sessions with Stellar anchors by proving control over a Stellar account. Once authenticated, wallets receive a JSON Web Token (JWT) that they use in subsequent requests to the anchor's standardized services.
 
-For the complete specification, see [SEP-0010: Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md).
+For the complete specification, see [SEP-10: Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md).
 
 The Anchor Platform implements SEP-10 with support for:
 
diff --git a/docs/platforms/anchor-platform/sep-guide/sep45/README.mdx b/docs/platforms/anchor-platform/sep-guide/sep45/README.mdx
index 4800dc9fff..c25e72742a 100644
--- a/docs/platforms/anchor-platform/sep-guide/sep45/README.mdx
+++ b/docs/platforms/anchor-platform/sep-guide/sep45/README.mdx
@@ -7,7 +7,7 @@ sidebar_position: 70
 
 SEP-45 (Stellar Web Authentication for Contract Accounts) enables smart wallet applications to create authenticated sessions with Stellar anchors by proving control over a contract account (`C...`). Once authenticated, wallets receive a JSON Web Token (JWT) that they use in subsequent requests to the anchor's standardized services.
 
-For the complete specification, see [SEP-0045: Stellar Web Authentication for Contract Accounts][sep-45].
+For the complete specification, see [SEP-45: Stellar Web Authentication for Contract Accounts][sep-45].
 
 The Anchor Platform implements SEP-45 with support for:
 
diff --git a/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx b/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx
index 259239e195..45ba17f518 100644
--- a/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx
+++ b/docs/platforms/stellar-disbursement-platform/admin-guide/embedded-wallets.mdx
@@ -205,7 +205,7 @@ The verification step ensures that the receiver is who they claim to be. Dependi
 
 The verification process uses the SDP's native SEP-24 implementation. The receiver authenticates with a SEP-24 JWT token that's generated during the passkey authentication flow.
 
-For background on SEP-45 (contract-account web authentication), see [SEP-0045](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md).
+For background on SEP-45 (contract-account web authentication), see [SEP-45](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0045.md).
 
 :::
 
diff --git a/docs/tokens/anatomy-of-an-asset.mdx b/docs/tokens/anatomy-of-an-asset.mdx
index 39a45e3b8f..eb4a33d520 100644
--- a/docs/tokens/anatomy-of-an-asset.mdx
+++ b/docs/tokens/anatomy-of-an-asset.mdx
@@ -32,7 +32,7 @@ to help issuers select the most appropriate model for their use case.
 | **Ledger Storage Fees/Expiry** | 0.5 XLM per trustline, no expiry\* | [Rent](../learn/fundamentals/lumens#rent) and [Archives](../learn/fundamentals/contract-development/storage/state-archival) | [Rent](../learn/fundamentals/lumens#rent) and [Archives](../learn/fundamentals/contract-development/storage/state-archival) |
 | **Ideal For** | Payments, simple assets (fiat based stablecoins), Stellar smart contracts integration | DeFi and custom tokenomics | Institutional RWAs with compliance |
 | **Source Code** | [Built-in Stellar Asset Contract](https://github.com/stellar/rs-soroban-env/tree/main/soroban-env-host/src/builtin_contracts) | [OpenZeppelin Fungible Token reference](https://github.com/OpenZeppelin/stellar-contracts/tree/main/packages/tokens/src/fungible) | [OpenZeppelin T-REX (RWA token) reference](https://github.com/OpenZeppelin/stellar-contracts/tree/main/packages/tokens/src/rwa) |
-| **Relevant SEPs** | [SEP-0001 (Stellar Info File)][sep-1] <br /><br /> [SEP-0014 (Dynamic Asset Metadata)][sep-14] <br /><br />[SEP-41 (Soroban Token Interface)][sep-41] | [SEP-41 (Soroban Token Interface)][sep-41] | [SEP-41 (Soroban Token Interface)][sep-41] <br /><br /> [SEP-0057 (T-REX / Token for Regulated EXchanges)][sep-57] |
+| **Relevant SEPs** | [SEP-1 (Stellar Info File)][sep-1] <br /><br /> [SEP-14 (Dynamic Asset Metadata)][sep-14] <br /><br />[SEP-41 (Soroban Token Interface)][sep-41] | [SEP-41 (Soroban Token Interface)][sep-41] | [SEP-41 (Soroban Token Interface)][sep-41] <br /><br /> [SEP-57 (T-REX / Token for Regulated EXchanges)][sep-57] |
 
 _\* Starting with Yardstick, Protocol 26, by assigning a smart contract (`C...` address) as the owner of a Stellar Asset Contract, balances and transfer rules can be fully managed within the contract. Additionally, smart contracts can create trustlines programmatically using the SAC's [`trust` function](./stellar-asset-contract.mdx#creating-trustlines-from-a-contract), so a missing trustline no longer needs to be set up in a separate, prior transaction._
 
@@ -263,7 +263,7 @@ When issuing a reserve-backed stablecoin, you must set up its off-chain reserve,
 As an asset issuer, you may need to comply with regulatory requirements that vary based on jurisdiction. Stellar has built-in features that can help meet these requirements, such as:
 
 - [Controlling access to an asset with flags](./control-asset-access.mdx#controlling-access-to-an-asset-with-flags)
-- [SEP-0008: Regulated Assets](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md) - regulated assets are assets that require an issuer’s approval (or a delegated third party’s approval) on a per-transaction basis. Check out this Stellar Ecosystem Proposal to learn how to implement regulated assets into your use case.
+- [SEP-8: Regulated Assets](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0008.md) - regulated assets are assets that require an issuer’s approval (or a delegated third party’s approval) on a per-transaction basis. Check out this Stellar Ecosystem Proposal to learn how to implement regulated assets into your use case.
 
 [sac]: ./stellar-asset-contract.mdx
 [ti]: ./token-interface.mdx
diff --git a/docs/tokens/publishing-asset-info.mdx b/docs/tokens/publishing-asset-info.mdx
index 2bbde89119..7aee329fcd 100644
--- a/docs/tokens/publishing-asset-info.mdx
+++ b/docs/tokens/publishing-asset-info.mdx
@@ -19,7 +19,7 @@ Using a `set_options` operation, you can link your Stellar account to the domain
 
 ## Completing your `stellar.toml`
 
-The first Stellar Ecosystem Proposal (SEP) is [SEP-0001: Stellar Info File](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) and specifies everything you would ever need to include in your Stellar info file. This section will walk through the sections of SEP-0001 that relate to asset issuers. Use this section in conjunction with the SEP to ensure you complete your `stellar.toml` correctly.
+The first Stellar Ecosystem Proposal (SEP) is [SEP-1: Stellar Info File](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md) and specifies everything you would ever need to include in your Stellar info file. This section will walk through the sections of SEP-1 that relate to asset issuers. Use this section in conjunction with the SEP to ensure you complete your `stellar.toml` correctly.
 
 The four sections we’ll cover are:
 
@@ -30,7 +30,7 @@ The four sections we’ll cover are:
 
 For each of those sections, we’ll let you know which fields are required, meaning all asset issuers must include them to be listed by exchanges and wallets, and which fields are suggested. Completing suggested fields is a good way to make your asset stand out.
 
-**Note:** it's a good idea to keep the sections in the order presented in SEP-0001: Stellar Info File, which is also the order they're presented here. TOML requires arrays to be at the end, so if you scramble the order, you may cause errors for TOML parsers.
+**Note:** it's a good idea to keep the sections in the order presented in SEP-1: Stellar Info File, which is also the order they're presented here. TOML requires arrays to be at the end, so if you scramble the order, you may cause errors for TOML parsers.
 
 ### 1. General Information
 
@@ -44,11 +44,11 @@ There are several fields where you list information about your Stellar integrati
 
 #### Suggested fields for asset issuers:
 
-- `TRANSFER_SERVER` if you support [SEP-0006: Deposit and Withdrawal API](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md)
-- `TRANSFER_SERVER_SEP0024` if you support [SEP-0024: Interactive Deposit and Withdrawal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md)
-- `KYC_SERVER` if you support [SEP-0012: KYC API](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md)
-- `WEB_AUTH_ENDPOINT` if you support [SEP-0010: Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md)
-- `DIRECT_PAYMENT_SERVER` if you support [SEP-0031: Cross-Border Payments API](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md)
+- `TRANSFER_SERVER` if you support [SEP-6: Deposit and Withdrawal API](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0006.md)
+- `TRANSFER_SERVER_SEP0024` if you support [SEP-24: Interactive Deposit and Withdrawal](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0024.md)
+- `KYC_SERVER` if you support [SEP-12: KYC API](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0012.md)
+- `WEB_AUTH_ENDPOINT` if you support [SEP-10: Stellar Web Authentication](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0010.md)
+- `DIRECT_PAYMENT_SERVER` if you support [SEP-31: Cross-Border Payments API](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0031.md)
 
 If you support other Stellar Ecosystem Proposals — such as federation or delegated signing — or host a public Horizon instance that other people can use to query the ledger, you should also add the location of those resources to [General Information](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0001.md#general-information) so they're discoverable.
 
diff --git a/meetings/2024-02-08.mdx b/meetings/2024-02-08.mdx
index 7347b5031f..3a530ba352 100644
--- a/meetings/2024-02-08.mdx
+++ b/meetings/2024-02-08.mdx
@@ -10,7 +10,7 @@ import DriveVideo from "@site/src/components/DriveVideo";
 
 [Discord agenda thread](https://discord.com/channels/897514728459468821/1204462856037470248)
 
-1. Stellar Asset List (SEP-0042) draft presentation by [OrbitLens](https://github.com/orbitlens)
+1. Stellar Asset List (SEP-42) draft presentation by [OrbitLens](https://github.com/orbitlens)
    1. [SEP draft](https://github.com/orbitlens/stellar-protocol/blob/sep-0042-token-lists/ecosystem/sep-0042.md)
    2. [Discord discussion](https://discord.com/channels/897514728459468821/1162558946867953704)
 2. Stellar + Soroban documentation survey